SWSE Plugin Crashes with stcaswpi - CSSSWSESessionUtils
(Doc ID 1914486.1)
Last updated on SEPTEMBER 22, 2017
Applies to:Siebel CRM - Version 188.8.131.52  to 184.108.40.206.9 [IP2013] [Release V8]
On : 220.127.116.11 and 18.104.22.168, Windows platform and IIS Web Server
When uploading a Siebel attachment, the SWSE plugin may crash with below call stack:
stcaswpi +0x8194 = CSSSWSESessionUtils::ValidateXMLDoc() +0x254
stcaswpi +0x83d1 = CSSSWSESessionUtils::GetHttpRequestSoapHeaders() +0xf1
stcaswpi +0x915f = CSSSWSESessionUtils::GetHttpRequestReqProperties() +0x26f
stcaswpi +0x118ff = CSSSWSEHttpRequest::InitReqProperty() +0xbf
stcaswpi +0x11987 = CSSSWSEHttpRequest::GetReqProperty() +0x47
stcaswpi +0x22427 = CSSSWSEReqHandlerFactory::CreateHandler() +0x32c7
stcaswpi +0x1e6c9 = CSSSWSEAbstractRequestHandler::GetHandlerName() +0x6a9
sweiis +0x2c17 = GetExtensionVersion() +0x207
sslcosd +0x2152 = OSDThreadPrivIsInit() +0x1d2
sslcosd +0x21dc = OSDThreadPrivIsInit() +0x25c
MSVCR71 +0x9565 = endthreadex() +0xa0
kernel32 +0x24829 = GetModuleHandleA() +0xdf
The crash.txt is generated under <SWSE_ROOT>\BIN. For example: crash_5476.txt, where 5476 corresponds to the PID of w3wp.exe.
In swse log (i.e.: ss140703_5476.log), messages such as the below are found:
When SWSE plugin crashes with this call stack, the IIS worker (aka w3wp.exe, aka IIS Application Pool) recycles: some Siebel requests fail, but the user sessions on the OM stay intact and can be revitalized.
When IIS worker is recycled:
- Some Microsoft Application/System Events warnings/events are registered in Microsoft Event Viewer.
- A new swse log is generated; for example: ss140703_2904.log, where 2904 corresponds to the TID of new w3wp.exe process.
When uploading the attachment through an OpenUI OM, this SWSE crash may try to recycle the IIS worker several times in a row for a few seconds. This may result in IIS stopping the Application Pool; thus all Siebel sessions are lost and new Siebel sessions cannot be started. The "Service Unavailable" is displayed in browser.
When IIS Application Pool has been stopped, an IISRESET or restart of 'World Wide Web Publishing Service' (aka W3SVC) may not be enough. Some times it's necessary to start the AppPool manually.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|