[jboss-jira] [JBoss JIRA] (AS7-3830) Remote JNDI call does not bind stateful beans

[jaikiran pai (JIRA)]

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

jaikiran pai commented on AS7-3830:
-----------------------------------

Ondra, I've included your testcase changes in that pull request. So you won't have to send a separate pull request for this. Thank you for that testcase.

                
> Remote JNDI call does not bind stateful beans
> ---------------------------------------------
>
>                 Key: AS7-3830
>                 URL: https://issues.jboss.org/browse/AS7-3830
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB, Naming
>    Affects Versions: 7.1.0.Final
>            Reporter: Ondřej Chaloupka
>            Assignee: jaikiran pai
>              Labels: eap6_LA
>             Fix For: 7.1.1.Final
>
>
> It seems that current ejb remote client is not able to find stateful bean. Exception is thrown instead:
> {code}
> javax.naming.NamingException: java.lang.IllegalStateException: No EJB client context is available [Root exception is java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available]
> 	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135)
> 	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
> 	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
> 	at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:124)
> 	at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:70)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available
> 	at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:91)
> 	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:133)
> 	... 7 more
> Caused by: java.lang.IllegalStateException: No EJB client context is available
> 	at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:233)
> 	at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:160)
> 	at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:89)
> 	... 8 more
> {code}
> Please, check my test whether definition of remote context does not contain a mistake. But finding singleton and stateless beans works fine.
> https://github.com/ochaloup/jboss-as/blob/ejb-remote-call/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/naming/remote/ejb/RemoteNamingEjbTestCase.java

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