Application Crashes When Using Script Debugger with UseThreadPool=True
(Doc ID 2969347.1)
Last updated on JUNE 11, 2024
Applies to:
Siebel CRM - Version 23.7 to 24.5 [Release V17]Information in this document applies to any platform.
Symptoms
Application crashes in Development environment while running Script Debugger.
MSVCR110 +0x30203 = memccpy() +0xbc
SSCFDBGU +0x981f = CSSScriptDebuggerClientUIService::End() +0xe9f
SSCFDBGU +0x63df = CSSScriptDebuggerClientUIService::GetTheClient() +0x146f
SSCFDBGU +0x8970 = CSSScriptDebuggerClientUIService::ProcessMessage() +0x80
sscfom +0x1d1cd = CSSService::InvokeMethod() +0x2cd
sstcsiom +0x27d1 = CSSSIOMSession::ProcessDebugMessage() +0x91
sssasos +0x2898 = CompHandleMsg() +0xbf8
siebmtshmw +0x1a84c = SmiBeginTrace() +0x60bc
siebmtshmw +0x19f8f = SmiBeginTrace() +0x57ff
siebmtshmw +0xe823 = SmiCleanupDetTask() +0x3483
sslcosd +0x2443 = OSDThreadPrivIsInit() +0x273
sslcosd +0x24db = OSDThreadPrivIsInit() +0x30b
MSVCR110 +0x2db10 = _get_tlsindex() +0x61
MSVCR110 +0x2daf4 = _get_tlsindex() +0x45
KERNEL32 +0x205c9 = BaseThreadInitThunk() +0x19
ntdll +0x677ad = RtlGetAppContainerNamedObjectPath() +0xed
ntdll +0x6777d = RtlGetAppContainerNamedObjectPath() +0xbd
The issue can be reproduced at will with the following steps:
1- Login to Webtools (db authentication)
2- Create your DEV Workspace
3- Navigate to the Webtools Objects
4- From the top right hand corner, click on the Script Debugger (Insect Icon)
5- From debugger Frame, from drop down select Business Service and search for BS name "Eliza"
6- For the "Service_PreInvokeMethod", put a Toggle Breakpoint on "var msg = Inputs.GetProperty("InputMessage");"
7- Click on Settings (Gear shape) in the right hand corner and make sure Application being used is defined
8- Now click the "Start" Button to start Script Debugging
9- This will launch the Application Object Manager
10- Enter your DB credentials
11- Now, navigate to the Administration - Business Service from the Site Map
12- Select the "Simulator" View Tab
13- Create a new record with BS Name "Eliza" and Method "Analyze"
14- In the middle "Input Arguments" Applet, create a new record and enter "InputMessage" for Property Name and "TEST" for Property Value, then save the record
15- Finally, click the Button "Run"
16- If the above works, the system should navigate you back to Webtools and place cursor on Toggle Breakpoint, in order to Step through the code
17. Repeat the business service call, it may break at 4th and sometimes 10th call.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |