[jboss-jira] [JBoss JIRA] (WFLY-115) JMSService error during :reload operation

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Tue Apr 30 20:50:54 EDT 2013


    [ https://issues.jboss.org/browse/WFLY-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771259#comment-12771259 ] 

RH Bugzilla Integration commented on WFLY-115:
----------------------------------------------

Paul Gier <pgier at redhat.com> changed the Status of [bug 951649|https://bugzilla.redhat.com/show_bug.cgi?id=951649] from MODIFIED to ON_QA
                
> JMSService error during :reload operation
> -----------------------------------------
>
>                 Key: WFLY-115
>                 URL: https://issues.jboss.org/browse/WFLY-115
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>             Fix For: 8.0.0.Alpha1
>
>
> 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:
> {noformat}
> 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]
> {noformat}
> When the HornetQ server is reloaded, it fails to lock its lock files that were not properly released during stop.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list