Bug 779941

Summary:	HornetQ logs warning and exception on shutdown
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Julian Coleman <jcoleman>
Component:	JBoss Messaging	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.ER1	CC:	butkovic
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2300
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	SOA-2300	Environment:	SOA 5.1.0 ER1 embedded and standalone
Last Closed:	2011-12-06 22:01:25 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:

Description Julian Coleman 2010-09-10 16:03:00 UTC

++ This bug is a clone of bug 779940 ++

project_key: SOA

The following entries are logged when shutting down the server:

17:09:08,345 WARN  [HornetQXAResourceWrapper] Notified of connection failure in recovery connectionFactory for provider org.hornetq.core.remoting.impl.invm.InVMConnectorFactory
HornetQException[errorCode=4 message=The connection was disconnected because of server shutdown]
        at org.hornetq.core.client.impl.FailoverManagerImpl$Channel0Handler$1.run(FailoverManagerImpl.java:1118)
        at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
17:09:08,797 INFO  [HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) stopped

Comment 1 Julian Coleman 2010-09-14 14:51:32 UTC

Link: Added: This issue depends JBPAPP-5080

Comment 2 Martin Vecera 2010-09-15 11:37:47 UTC

Link: Added: This issue is duplicated by SOA-2321

Comment 3 Julian Coleman 2011-09-18 08:30:09 UTC

From JBPAPP-5080:

From a HornetQ perspective there's nothing we can do to get rid of this exception. This is because the life-cycle of the HornetQXAResourceWrapper is under the control of the Transaction Manager and since there are no life cycle methods in the XAResourceWrapper interface (i.e. close or stop) we have no hook point as to when we can close the underlying connection.

As far as I'm aware this is addressed in AS7.

Comment 4 Peter Butkovic 2011-10-14 06:59:45 UTC

it seems to be resolved in JBPAPP-5080
is it not possible to provide (possibly backport) the solution for JBoss 6 series?
As migration to JBoss7 is not an option for us.