Bug 780197 (SOA-2578)
Summary: | Exception "javax.jms.IllegalStateException: Cannot find session with id ..." | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Pavel Macik <pmacik> |
Component: | JBossESB | Assignee: | Julian Coleman <jcoleman> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 5.1.0.ER4 | ||
Target Milestone: | --- | ||
Target Release: | 5.1.0 GA, 5.1.0.ER5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://jira.jboss.org/jira/browse/SOA-2578 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
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 |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pavel Macik
2010-11-12 15:52:27 UTC
Link: Added: This issue Cloned from SOA-1064 Link: Added: This issue depends JBPAPP-5415 Is this a defect we are tracking for EAP next? Or is it something we need for SOA 5.1.0? We need it for SOA 5.1 as it is part of the clustered messaging changes that are coming in Link: Added: This issue depends JBPAPP-5505 Link: Removed: This issue depends JBPAPP-5415 Link: Added: This issue is related to SOA-2455 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. Release Notes Docs Status: Added: Not Yet Documented Writer: Added: dlesage Verified - not seeing the exception any more - with ER7 Temporarily reopening to update release notes. 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. Reopening this JIRA to edit the release notes text field; will set back to Closed -> Done in a moment. 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. Setting to Closed -> Done again after editing the release notes field. |