SBL-GEN-00143 Process 8408 exited with error



Applies to:


Siebel Public Sector Service - Version: 8.1.1.3[21219] and later   [Release: V8 and later ]
Information in this document applies to any platform.



Symptoms



Statement of issue:

------------------------

intermittent failures and timeouts when sending out JMS messages.



Error:

--------

JMSReceiver 8408 SBL-GEN-00143 Process 8408 exited with error



Expected behaivor:

-----------------------

the messages should be processed in a consistence way with no timeouts



Actual behaivor:

-------------------

the EAI Object Manager doesnt release the running task until 25 minutes.
This causes a stack of running tasks stating 'Waiting for command'
which seems to make the component unstable





Siebel / OS version:

--------------------------

8.1.1.3, Windows 2003


Cause



Wrong "SessionType" being used in the HTTP Header as 'Stateless'
while the external system was not using the session tokens provided in
the the Siebel HTTP Response. Changing the SessionType to 'None' ensures
the EAI Tasks are completing successfully and



The customer has used "SessionType" Stateless according to his confirmation


Solution



In this particular case where the external application did not use
the token from soap header, ensure the SOAP header of the message
contains a section with sessiontype = None like following:


Example:


 <soap:Header>

<UsernameToken xmlns="http://siebel.com/webservices">user</UsernameToken>

<PasswordText xmlns="http://siebel.com/webservices">hello123</PasswordText>

<SessionType xmlns="http://siebel.com/webservices">None</SessionType>

</soap:Header>

תגובות

פוסטים פופולריים מהבלוג הזה

Profile Attributes and Open UI

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

SBL-SVC-00150