Bug 779521 (SOA-1903) - [JBPAPP-3593] [JBMESSAGING-1786] Message stuck caused by rolling back the transaction
Summary: [JBPAPP-3593] [JBMESSAGING-1786] Message stuck caused by rolling back the tra...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1903
Deadline: 2010-03-08
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBoss Messaging
Version: 4.3 CP02
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP04 CR1
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-29 12:43 UTC by Darran Lofthouse
Modified: 2010-05-13 06:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-12 08:32:26 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1903 0 Major Closed [JBPAPP-3593] [JBMESSAGING-1786] Message stuck caused by rolling back the transaction 2014-06-24 19:17:26 UTC

Description Darran Lofthouse 2010-01-29 12:43:55 UTC 
Date of First Response: 2010-02-01 04:48:09
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/267393
project_key: SOA
Comment 1 Darran Lofthouse 2010-01-29 12:44:16 UTC 
Link: Added: This issue depends JBPAPP-3593
Comment 2 Toshiya Kobayashi 2010-02-01 09:48:09 UTC 
Modified title because it's not backport issue, but incorporating a new fix.
Comment 3 Anne-Louise Tangring 2010-02-25 16:38:24 UTC 
Approved for SOA 4.3 CP03, but depends on inclusion into EAP 4.3 CP08 and the ability for SOA 4.3 CP03 to consume EAP 4.3 CP08 in time for release.
Comment 4 David Le Sage 2010-04-09 00:24:12 UTC 
Documented as Known Issue in draft Release Notes.  Will be moved to "Resolved Issues" section if fixed before release:



SOA-1903 https://jira.jboss.org/jira/browse/JBPAPP-3593

   If a site is running both a Java Message Service server and an application server, if the latter is
   killed, the transaction database will be rolled back by the recovery process but the the in-memory
   state of the queue is neither restored nor canceled. As a result, the message will be stuck in the
   queue.

   To work around this problem, restart the JMS Server. This will make the message "alive" once
   more so that it can be processed correctly.
Comment 5 Zuzana Zoubkova 2010-04-12 11:14:19 UTC 
CR1 will be based on EAP 4.3 CP08 CR1
Comment 6 Jiri Pechanec 2010-05-12 08:32:26 UTC 
Verified in CR2 - SOA-P is based on EAP 4.3 CP08 GA
Note You need to log in before you can comment on or make changes to this bug.