PK99026: JMS CLIENT CONNECTION TO WEBSPHERE APPLICATION SERVER FAILS WITH A CWSIC8007E OBJECTSTOREFULLEXCEPTION

Fixes are available

APAR status

Closed as program error.

Error description

A JMS client connecting with WebSphere Application Server
can fail with the following exception returned to the client:
Exception in thread "main" com.ibm.websphere.sib.exception.
SIErrorException:com.ibm.websphere.sib.exception.
SIErrorException:
CWSIC8002E: An internal error occurred. An unknown or unexpected
exception was thrown by the core API:
exception CWSIC8007E: An exception was caught from the remote
server with Probe Id 3-006-0012. Exception:
com.ibm.ws.sib.comms.server.ObjectStoreFullException..
at com.ibm.ws.sib.comms.common.JFAPCommunicator.defaultChecker
(JFAPCommunicator.java:1631)
at com.ibm.ws.sib.comms.client.OrderingContextProxy.create
(OrderingContextProxy.java:245)
at com.ibm.ws.sib.comms.client.OrderingContextProxy.<init>
(OrderingContextProxy.java:120)

at com.ibm.ws.sib.comms.client.ConnectionProxy.createOrdering
Context(ConnectionProxy.java:3454)
at com.ibm.ws.sib.api.jms.impl.JmsSessionImpl.<init>
(JmsSessionImpl.java:448)
at com.ibm.ws.sib.api.jms.impl.JmsConnectionImpl.Instantiate
Session(JmsConnectionImpl.java:1221)

at com.ibm.ws.sib.api.jms.impl.JmsConnectionImpl.createSession
(JmsConnectionImpl.java:343)
at CreateLotsOfSessions.main(CreateLotsOfSessions.java:20)
FFDC files on the server side show:
Exception = com.ibm.ws.sib.comms.server.
ObjectStoreFull Exception
Source = com.ibm.ws.sib.comms.server.clientsupport.
StaticCATConsumer.rcvCreateConsumerSess
probeid = 3-010-0002
Stack Dump = com.ibm.ws.sib.comms.server.ObjectStore
FullException
at com.ibm.ws.sib.comms.server.ConversationState.
extendObjectTable(ConversationState.java:431)
at com.ibm.ws.sib.comms.server.ConversationState.
addObject(ConversationState.java:360)
at com.ibm.ws.sib.comms.server.clientsupport.
StaticCATConsumer.rcvCreateConsumerSess
(StaticCATConsumer.java:401)
at com.ibm.ws.sib.comms.server.clientsupport.
ServerTransportReceiveListener.dataReceived
(ServerTransportReceiveListener.java:505)
at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.
ConversationReceiveListenerDataReceivedInvocation.
invoke
(ConversationReceiveListenerDataReceivedInvocation.
java:188)
at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.
ReceiveListenerDispatchQueue.run(ReceiveListener
DispatchQueue.java:411)
at com.ibm.ws.util.ThreadPool$Worker.run
(ThreadPool.java:1497)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server            *
*                  Version 6.0.2, 6.1, or Version 7.0          *
****************************************************************
* PROBLEM DESCRIPTION: ObjectStoreFullException after          *
*                      creating or closing a large number      *
*                      of JMS sessions, without creating       *
*                      message producers/consumers             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
An occurrence of a
com.ibm.ws.sib.comms.server.ObjectStoreFullException
indicates that a an internal table of shared state between a
client connected to a messaging engine over a network, and the
messaging engine itself, has become full.
The table has a limited size of 32,767 items, and each
physical network connection between client and server has its
own table.

The most common cause of these exceptions, is application
logic that creates JMS objects (such as sessions, or message
producers/consumers) and does not close them.
These cases must be corrected in the application code that is
not closing the objects.

However, this APAR addresses a specific problem in the
default messaging provider client code when an application
creates a JMS session, and closes it without creating any
message producers, or message consumers.
In this specific case, an object allocated in the table when
the JMS session is created, is not freed or reused when the
JMS session is closed.

The FFDC dumped with probeid 3-006-0012 from a messaging
engine experiencing this issue, will show many thousands
objects of the following class in the state tables:
com.ibm.ws.sib.processor.impl.OrderingContextImpl

Problem conclusion

The fix for this APAR prevents the leak of objects, when JMS
sessions are created and closed without creating any message
producers or consumers from them.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.0.2.43, 6.1.0.31, and 7.0.0.9.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK99026
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-20
Closed date
2009-12-21
Last modified date
2015-03-05

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
PLAT MSG COM
Fixed component ID
620600101

Applicable component levels

R200 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK99026: JMS CLIENT CONNECTION TO WEBSPHERE APPLICATION SERVER FAILS WITH A CWSIC8007E OBJECTSTOREFULLEXCEPTION

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R200 PSY

Document Information

Share your feedback

Need support?