[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=12811431#comment-12811431 ] 

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]

(In reply to Miroslav Novak from comment #5)
> Problem is "[WFLY-101] JMSService.start to perform blocking I/O
> asynchronously" I guess only way to verify is to read the code, right?

That's correct, there is no observable way to verify this.
Reading the code, it appears that the JMSService.start/stop methods performs HornetQ-related operations asynchronously in a separate executor: https://github.com/jmesnil/jboss-eap/commit/161295de1ae35a10c53dcc8f4fce933b4baadeb2#diff-60f2c56b6f01bb06387cbe9054ddc549R89
                
> 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