[arquillian-issues] [JBoss JIRA] (ARQ-626) Arquillian test with asynchronous components (Asynchonous EJB or JMS) in glassfish -embedded

[Hugo de Paix de Coeur (Commented) (JIRA)]

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

Hugo de Paix de Coeur commented on ARQ-626:
-------------------------------------------

Yes .. I had written such a workaround (thanks for CountDownLatch I didn't know).

I agree we must sync ourself by our own means a "user" thread, but I was hoping "managed" threads (JMS, or Async EJB) could have been tracked by the glassfish containers for us and the glassfish-embedded to handle it.
It seems it's more an enhancement than a bug.
                
> Arquillian test with asynchronous components (Asynchonous EJB or JMS) in glassfish -embedded
> --------------------------------------------------------------------------------------------
>
>                 Key: ARQ-626
>                 URL: https://issues.jboss.org/browse/ARQ-626
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: GlassFish Containers
>    Affects Versions: 1.0.0.Alpha5
>         Environment: arquillian-glassfish-embedded-3.1, arquillian-junit-1.0.0.Alpha5
>            Reporter: Hugo de Paix de Coeur
>
> When we use Asynchronous EJB or MDB with JMS in our tests, the test leave and it seems the container is undeployed or something ...
> It results in async always running code complaining about undeployed or stopped container for subsequents EJB calls and so on ...
> Am I wrong ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira