Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 7.7.2 SIA  and later
Information in this document applies to any platform.
Many open TCP connections to JMS Provider in ESTABLISHED state was detected,
after performing of series of calls the "EAI JMS Transport" BS (methods: "SendReceive" and "Send"), in parallel user sessions (up to 100) of Siebel Thin Client Application Object Manager (AOM).
After the number of opened connections was reached around 300, the JMS Provider (the IBM Websphere MQ Server) started encountering the resource problem to accept new connection from a new request (JMS Send) coming from new Siebel Thin Client task. As result Siebel user could not put any new message (invoice) in JMS Queue.
This can also be observed when sending requests to TIBCO where it leaves zero sessions opened in TIBCO JMS.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms