Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1143818

Summary: [QE] (6.4.0) Shutting down server with deployed JMS bridge aborts XA transactions
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Miroslav Novak <mnovak>
Component: HornetQAssignee: Clebert Suconic <csuconic>
Status: CLOSED NOTABUG QA Contact: Miroslav Novak <mnovak>
Severity: medium Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.4.0CC: ataylor, cdewolf, istudens, jbertram, msvehla
Target Milestone: DR9   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-15 16:35:18 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:
Bug Depends On:    
Bug Blocks: 1158079    
Attachments:
Description Flags
server.log
none
standalone-full-ha-bridge.xml
none
standalone-full-ha-target.xml
none
standalone-full-ha-2.xml none

Description Miroslav Novak 2014-09-18 05:22:19 UTC 
Description of problem:
If server with deployed JMS bridge (ONCE_AND_ONLY_ONCE delivery mode) is processing messages and this server is cleanly shutdowned than there are lots of arjuna warnings (see server.log)

Steps to Reproduce:
1. Start two EAP 6.4.0.DR1 servers and deploy JMS bridge to first. Bridge sends messages from InQueue (from 1st server) to OutQueue (2nd server)
2. Start producer which sends messages to InQueue
3. Cleanly shutdown first server - see warnings

Expected results:
Before shutdown the bridge should stop to process new messages from InQueue and wait some time for current messages to be processed.
Comment 1 Miroslav Novak 2014-09-18 05:23:27 UTC 
Created attachment 938745 [details]
server.log
Comment 2 Miroslav Novak 2014-09-18 05:24:11 UTC 
Created attachment 938746 [details]
standalone-full-ha-bridge.xml
Comment 3 Miroslav Novak 2014-09-18 05:24:51 UTC 
Created attachment 938747 [details]
standalone-full-ha-target.xml
Comment 4 Miroslav Novak 2014-09-18 08:02:57 UTC 
After some tries I've noticed that steps to reproduce the issue are different:
1. Start two EAP 6.4.0.DR1 servers and deploy JMS bridge to first. Bridge sends messages from InQueue (from 1st server) to OutQueue (2nd server)
2. Cleanly shutdown 2nd server and start again
3. Cleanly shutdown first server - see warnings
Comment 5 Miroslav Novak 2014-09-18 08:05:02 UTC 
@Andy
I'd like to ask you to take a look at this first before it's moved to another component.
Comment 6 Andy Taylor 2014-09-18 10:56:11 UTC 
yes, this is for us so leave it with me
Comment 7 Miroslav Novak 2014-09-22 08:04:06 UTC 
Created attachment 939911 [details]
standalone-full-ha-2.xml

New standalone-full-ha-2.xml for target server of the bridge attached.
Comment 8 Andy Taylor 2014-09-22 14:07:56 UTC 
PR created https://github.com/hornetq/hornetq/pull/1858.

Just to note that if the target server is down then an exception will still be shown. This is only in XA mode as we batch messages and need to rollback the transaction. We should make sure that this is documented and that in this scenario the target server should be stopped after the source server (or other way around if the source server is remote).
Comment 10 JBoss JIRA Server 2014-10-30 16:07:16 UTC 
Clebert Suconic <clebert.suconic> updated the status of jira HORNETQ-1440 to Closed
Comment 11 Ivo Studensky 2014-12-11 11:44:42 UTC 
This has been fixed in 2.3.22.Final, see comment 9.
Comment 13 Miroslav Novak 2014-12-15 08:39:49 UTC 
I can see exceptions in EAP 6.4.0.DR13 (HQ 2.3.24.Final). Returning to assigned.

Based on comment #8 this should be closed as won't fix, right?
Comment 14 Andy Taylor 2014-12-15 16:18:52 UTC 
if in xa mode yes
Comment 15 Miroslav Novak 2014-12-15 16:35:18 UTC 
Ok, closing as won't fix and creating new bz for doc team bz#1174338.