[
https://issues.jboss.org/browse/ARQ-626?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-626:
-----------------------------------
When using async components you are moving the execution over to another thread, which is
outside of Arquillians reach. In these cases the TestClass has to 'wait' one way
or the other for the async execution to finish before moving on. This can be done by using
e.g java.util.concurrent.Latches. See the cdi-ejb async example in the showcase:
https://github.com/arquillian/arquillian-showcase/blob/master/cdi-ejb/src...
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