Bug 1029396 - Sometimes JMS client does not failover when journal is disconnected
Summary: Sometimes JMS client does not failover when journal is disconnected
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-12 10:47 UTC by Miroslav Novak
Modified: 2014-10-25 12:01 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-07 08:55:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Miroslav Novak 2013-11-12 10:47:50 UTC 
Description of problem:
JMS producer does not failover when server is shutdowned due to journal disconnection. This was seen in with AIO journal-type on NFSv4. 

How reproducible:

1. Start 2 servers in collocated HA topology with shared journal on NFSv4 (with AIO journal type). There is queue "testQueue" deployed on both of the servers.
2. Start producer and consumer connected to 1st server sending/reading messages to/from queue "testQueue" (with transacted session)
3. Disconnect 1st server from NFS
4. Wait for HQ component on 1st server to shutdown and clients to failover

Results:
Sometimes happens that producer does not failover.

Issue is under investigation.
Comment 1 Miroslav Novak 2014-07-07 08:55:52 UTC 
I was not able to reproduce the issue with EAP 6.3.0.ER9. Closing.
Note You need to log in before you can comment on or make changes to this bug.