Bug 780197 (SOA-2578) - Exception "javax.jms.IllegalStateException: Cannot find session with id ..."
Summary: Exception "javax.jms.IllegalStateException: Cannot find session with id ..."
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2578
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.1.0.ER4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0 GA,5.1.0.ER5
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-12 15:52 UTC by Pavel Macik
Modified: 2011-02-12 12:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Linux 2.6.18-53.1.14.el5xen, x86_64, SOA-P 4.2.0 CP03 CR5, "production" based configuration, jdk1.5.0_12
Last Closed: 2011-02-12 12:49:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778591 0 high CLOSED Exception "javax.jms.IllegalStateException: Cannot find session with id ..." during clustered/failover testing. 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 780088 0 urgent CLOSED MessageSucker failures cause the delivery of the failed message to stall 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-2578 0 Blocker Closed Exception "javax.jms.IllegalStateException: Cannot find session with id ..." 2013-03-07 11:55:42 UTC

Internal Links: 778591 780088

Description Pavel Macik 2010-11-12 15:52:27 UTC 
project_key: SOA

There is a race in the JBoss Messaging code that may be triggered when the JCA layer attempts to close down a messaging inflow deployment.  This results in the IllegalStateException being raised at a later point, during commit on the transaction boundary.
Comment 1 Kevin Conner 2010-11-12 15:52:28 UTC 
Link: Added: This issue Cloned from SOA-1064
Comment 2 Kevin Conner 2010-11-16 10:18:43 UTC 
Link: Added: This issue depends JBPAPP-5415
Comment 3 Anne-Louise Tangring 2010-12-01 18:00:07 UTC 
Is this a defect we are tracking for EAP next? Or is it something we need for SOA 5.1.0?
Comment 4 Kevin Conner 2010-12-01 18:17:54 UTC 
We need it for SOA 5.1 as it is part of the clustered messaging changes that are coming in
Comment 5 Kevin Conner 2010-12-03 15:57:57 UTC 
Link: Added: This issue depends JBPAPP-5505
Comment 6 Kevin Conner 2010-12-03 15:59:19 UTC 
Link: Removed: This issue depends JBPAPP-5415
Comment 7 Kevin Conner 2010-12-03 15:59:55 UTC 
Link: Added: This issue is related to SOA-2455
Comment 8 Julian Coleman 2010-12-05 16:37:55 UTC 
Resolved with revision 7524 of:

  build-tools/builders/eap/post-patch/patch_db_persistance_conf.xml

Commit message:

  SOA-2455/SOA-2578
  Add the patches from JBPAPP-5505 to jboss-messaging-client.jar,
  jboss-messaging.jar and the &-persistence-service.xml files.
Comment 9 Laura Bailey 2010-12-17 01:10:55 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Comment 11 Dana Mison 2011-01-05 00:14:48 UTC 
Writer: Added: dlesage
Comment 12 Pavel Macik 2011-02-03 12:08:35 UTC 
Verified - not seeing the exception any more - with ER7
Comment 13 David Le Sage 2011-02-10 23:27:49 UTC 
Temporarily reopening to update release notes.
Comment 14 David Le Sage 2011-02-10 23:30:04 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2578

There was a race in the JBoss Messaging code that was triggered when the JCA layer attempted to close down a messaging inflow deployment. This caused a IllegalStateException to be raised during the commit on the transaction boundary. To fix this problem, a series of JBoss messaging patches have been back-ported. As a result, the problem no longer occurs.
Comment 15 Laura Bailey 2011-02-12 12:45:58 UTC 
Reopening this JIRA to edit the release notes text field; will set back to Closed -> Done in a moment.
Comment 16 Laura Bailey 2011-02-12 12:48:56 UTC 
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2578

There was a race in the JBoss Messaging code that was triggered when the JCA layer attempted to close down a messaging inflow deployment. This caused a IllegalStateException to be raised during the commit on the transaction boundary. To fix this problem, a series of JBoss messaging patches have been back-ported. As a result, the problem no longer occurs. Added: A race in the JBoss Messaging code was triggered when the JCA layer attempted to close down a messaging inflow deployment. This caused an exception of type IllegalStateException during the commit on the transaction boundary. Several JBoss Messaging patches were back-ported to fix this issue.
Comment 17 Laura Bailey 2011-02-12 12:49:44 UTC 
Setting to Closed -> Done again after editing the release notes field.
Note You need to log in before you can comment on or make changes to this bug.