Bug 1029396

Summary:	Sometimes JMS client does not failover when journal is disconnected
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Miroslav Novak <mnovak>
Component:	HornetQ	Assignee:	Clebert Suconic <csuconic>
Status:	CLOSED NOTABUG	QA Contact:	Miroslav Novak <mnovak>
Severity:	high	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.0	CC:	msvehla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-07 08:55:52 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 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.