[jboss-jira] [JBoss JIRA] (WFLY-101) JMSService.start is doing blocking I/O

[RH Bugzilla Integration (JIRA)]

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

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

Jeff Mesnil <jmesnil at redhat.com> made a comment on [bug 1003913|https://bugzilla.redhat.com/show_bug.cgi?id=1003913]

Breakpoint should be on org.hornetq.jms.server.impl.JMSServerManagerImpl#start

That the HornetQ class that is called by WildFly JMSService.

I'm nto sure what should happen exactly but since the JMS server start is asynchrounous now, other WildFly services will be able to start without being blocked.
This changes nothing for services *depending* on JMSService. They will not be started until the JMSService is started (asynchronously or not).
                
> JMSService.start is doing blocking I/O
> --------------------------------------
>
>                 Key: WFLY-101
>                 URL: https://issues.jboss.org/browse/WFLY-101
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>             Fix For: 8.0.0.Alpha1
>
>
> flag the start context as asynchronous

--
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