[arquillian-issues] [JBoss JIRA] (ARQ-1388) @EJB not working in embedded glassfish for @Remote Stateless beans if called more than twice

[Aslak Knutsen (JIRA)]

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

Aslak Knutsen commented on ARQ-1388:
------------------------------------

Do you get the same even if you don't cache the ear and the jar between tests? 
                
> @EJB not working in embedded glassfish for @Remote Stateless beans if called more than twice
> --------------------------------------------------------------------------------------------
>
>                 Key: ARQ-1388
>                 URL: https://issues.jboss.org/browse/ARQ-1388
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Base Implementation
>    Affects Versions: 1.0.3.Final, glassfish_1.0.0.CR4
>            Reporter: Dominik Kuhn
>         Attachments: arqtest.zip
>
>
> We have 20 testclasses. the ejb's are injected by the @EJB annotation.
> If each testclass is run standalone (using eclipse), everything works and the tests are successful.
> If all testclasses are run together (using eclipse or maven surefire plugin) the test fails after the first two testclasses with one of the two following error messages:
> java.lang.NullPointerException
> 	at arqtest.test.GreeterTest5.test(GreeterTest5.java:23)
> ... 
> or 
> java.lang.IllegalArgumentException: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata, please contact DeployableContainer developer.
> ...
> If I change the @Remote annotation of the stateless beans to @Local the tests are successful, even if run together.
> To test this i created a very simple test project, which i attached to this issue.

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