PM11439: ILLEGALSTATEEXCEPTION SEEN WHEN USING JBOSS AS AN GENERIC MESSAGING PROVIDER WITH A NON XASESSION.

Fixes are available

APAR status

Closed as program error.

Error description

An IllegalStateException exception is thrown by
JBoss Messaging when it is used as a generic messaging
provider for WebSphere Application Server.
Theexception is thrown when the application is attempting to
use a non XASession. The exception is as follows:

source=com.ibm.ejs.jms.JMSQueueSenderHandle org=IBM
prod=WebSphere
component=Application Server thread=[WebContainer : 0]
Caught JMSException in JMSQueueSenderHandle
parm0=javax.jms.IllegalStateException: Isn't an XASession
at org.jboss.jms.client.JBossSession.getSession(
                                          JBossSession.java:381)
at org.jboss.jms.client.JBossSession.getQueueSession(
                                          JBossSession.java:413)
at com.ibm.ejs.jms.JMSQueueSessionHandle.
             getOpenQueueSession(JMSQueueSessionHandle.java:411)
at com.ibm.ejs.jms.JMSQueueSenderHandle.<init>
                                  (JMSQueueSenderHandle.java:95)
at com.ibm.ejs.jms.JMSQueueSessionHandle.createSender(
                                 JMSQueueSessionHandle.java:232)

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  using a third-party JMS messaging provider  *
****************************************************************
* PROBLEM DESCRIPTION: When a generic JMS Provider is used     *
*                      an exception might occur on the JMS     *
*                      provider indicating that the Session    *
*                      is not an XA Session.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A third-party JMS messaging provider configured in WebSphere
Application Server might throw an exception indicating that a
non-XA session created by the application server cannot be
used as an XA sesion.

For example, JBoss Messaging configured as a JMS Provider throws
the following exception when non-XA Sessions are used:
javax.jms.IllegalStateException: Isn't an XASession
at org.jboss.jms.client.JBossSession.getSession(
                                          JBossSession.java:381)
at org.jboss.jms.client.JBossSession.getQueueSession(
                                          JBossSession.java:413)
at com.ibm.ejs.jms.JMSQueueSessionHandle.
             getOpenQueueSession(JMSQueueSessionHandle.java:411)
at com.ibm.ejs.jms.JMSQueueSenderHandle.<init>
                                  (JMSQueueSenderHandle.java:95)
at com.ibm.ejs.jms.JMSQueueSessionHandle.createSender(
                                 JMSQueueSessionHandle.java:232)

The exception occurs due to the application server incorrectly
using an instanceof check to determine if the session it
created was an XA session or not. This check is invalid, as
when the application server requests a non-XA session, it is
valid for the messaging provider to return an object that
happens to be an instance of the javax.jms.XASession interface
(even though is is a non-XA session, as requested).

Problem conclusion

The fix for this APAR removes the invalid instanceof check
from the application server. Instead, the application server
uses the same state check that it used when it created the
session to determine if it requested an XA session or not.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.33 and 7.0.0.13.  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
PM11439
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-01
Closed date
2010-06-01
Last modified date
2010-06-01

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
25 October 2021

Tips

PM11439: ILLEGALSTATEEXCEPTION SEEN WHEN USING JBOSS AS AN GENERIC MESSAGING PROVIDER WITH A NON XASESSION.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?