Bug 951649 - JMSService error during :reload operation
Summary: JMSService error during :reload operation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMS
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER6
: EAP 6.1.0
Assignee: Jeff Mesnil
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-12 17:15 UTC by Jeff Mesnil
Modified: 2013-07-23 18:43 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-6881 0 Major Resolved JMSService error during :reload operation 2014-04-02 07:54:15 UTC

Description Jeff Mesnil 2013-04-12 17:15:18 UTC
Description of problem:

if the admin client performs a :reload operation, the JMSService throws an exception and HornetQ server is not stopped properly and do not release its resources:
20:01:54,480 ERROR [org.jboss.messaging] (MSC service thread 1-1) JBAS011602: Exception while stopping JMS server: java.lang.IllegalStateException: Service already removed
	at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:792) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
	at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:775) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
	at org.jboss.msc.service.ServiceControllerImpl.setMode(ServiceControllerImpl.java:754) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
	at org.jboss.as.messaging.jms.JMSService$1.deActivate(JMSService.java:103) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
	at org.hornetq.core.server.impl.HornetQServerImpl.callDeActiveCallbacks(HornetQServerImpl.java:1374) [hornetq-server-2.3.0.CR2.jar:]
	at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:598) [hornetq-server-2.3.0.CR2.jar:]
	at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:542) [hornetq-server-2.3.0.CR2.jar:]
	at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:509) [hornetq-server-2.3.0.CR2.jar:]
	at org.hornetq.jms.server.impl.JMSServerManagerImpl.stop(JMSServerManagerImpl.java:502) [hornetq-jms-server-2.3.0.CR2.jar:]
	at org.jboss.as.messaging.jms.JMSService.stop(JMSService.java:119) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
	at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2082) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
	at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2043) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_15]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_15]
	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]
When the HornetQ server is reloaded, it fails to lock its lock files that were not properly released during stop.

How reproducible:
Always

Steps to Reproduce:
1. start the standalone-full.xml config
2. connected from the CLI, issue a :reload
=> JMSService throws the exception when it is stopped
=> HornetQ server throws an exception when it is (re)started

Comment 1 Jeff Mesnil 2013-04-15 14:04:39 UTC
this bug prevents a server with HornetQ to reload successfully.

Comment 2 Miroslav Novak 2013-04-16 11:50:04 UTC
We did not hit this issue in EAP 6.1.0.ER4. Not a beta blocker.

Comment 4 JBoss JIRA Server 2013-04-16 15:22:16 UTC
Jeff Mesnil <jmesnil> made a comment on jira AS7-6881

PR merged in master branch

Comment 6 Nikoleta Hlavickova 2013-05-03 09:39:44 UTC
We could not hit this problem neither with EAP 6.1.0 (tried DR4,ER4), nor with EAP 6.0.1. Verified for EAP 6.1.0 ER6.


Note You need to log in before you can comment on or make changes to this bug.