PK80246: JMS SESSION CREATION CAN FAIL WITH CWSIK0022E

Fixes are available

APAR status

Closed as program error.

Error description

With the default messaging provider, using multiple JMS
Sessions derived from a single JMS Connection the following
exception might occur when creating a new JMS Session:

com.ibm.ws.sib.processor.exceptions.
SIMPConnectionUnavailableException: CWSIK0022E: The connection
is closed to messaging engine <messaging engine name> and
cannot be used.

The above exception occurs using a JMS Connection that has
already been used to create a JMS Session that was
subsequently closed.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  WebSphere Application Server Version 7.0    *
****************************************************************
* PROBLEM DESCRIPTION: The following exception can occur       *
*                      when creating a new JMS Session:        *
*                                                              *
*                      SIMPConnectionUnavailableException:     *
*                      CWSIK0022E: The connection is           *
*                      closed to messaging                     *
*                      engine <messaging engine name> and      *
*                      cannot be used.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The following sequence of events causes this problem to
occur:

- A JMS Session is created within the default messaging
  provider in order to return a JMS Session handle to an
  application. This session is the first one created on the
  JMS Connection, and contains a connection to the messaging
  engine that is cloned when additional JMS Sessions are
  created on the connection.
- The JMS Session is closed, for example because it becomes
  aged and is closed by the J2C session pool.
- A new JMS Session is requested from the JMS Connection, and
  the exception is thrown.
The exception occurs because creating the new JMS Session
requires the original connection to the messaging engine,
which was incorrectly destroyed when the first JMS Session was
closed.

Problem conclusion

The fix for this APAR prevents the exception from occurring,
by ensuring a connection to the messaging engine is retained
from which JMS Sessions can be created, even if the first JMS
Session created from the JMS Connection is closed.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  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
PK80246
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-02-09
Closed date
2009-04-20
Last modified date
2009-04-20

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
620800101

Applicable component levels

R300 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK80246: JMS SESSION CREATION CAN FAIL WITH CWSIK0022E

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

R300 PSY

Document Information

Share your feedback

Need support?