[jboss-jira] [JBoss JIRA] (WFLY-2671) Failed to open channel for context EJBReceiverContext

[Yuriy Tereshchuk (JIRA)]

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

Yuriy Tereshchuk commented on WFLY-2671:
----------------------------------------

I am sorry, can some one share link on AS 7.2 or WildFly nightly builds, because on http://www.jboss.org/jbossas/downloads
                
> Failed to open channel for context EJBReceiverContext
> -----------------------------------------------------
>
>                 Key: WFLY-2671
>                 URL: https://issues.jboss.org/browse/WFLY-2671
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB
>    Affects Versions: JBoss AS7 7.1.1.Final
>         Environment: RHEL 6.3
>            Reporter: Yuriy Tereshchuk
>            Assignee: David Lloyd
>
> 526605 [Remoting "config-based-naming-client-endpoint" task-1] ERROR org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver  - Failed to open channel for context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext at 3969369f, receiver=Remoting connection EJB receiver [connection=Remoting connection <1f6f6df3>,channel=jboss.ejb,nodename=localhost]}
> org.jboss.remoting3.NotOpenException: Cannot open new channel because close was initiated
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:181)
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:307)
> 	at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:75)
> 	at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.associate(RemotingConnectionEJBReceiver.java:126)
> 	at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:297)
> 	at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:252)
> 	at org.jboss.ejb.client.EJBClientContext.registerConnection(EJBClientContext.java:342)
> 	at org.jboss.naming.remote.client.ejb.RemoteNamingEjbClientContextSelector.setCurrent(RemoteNamingEjbClientContextSelector.java:25)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.naming.remote.client.InitialContextFactory.setupEjbContext(InitialContextFactory.java:425)
> 	at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:115)
> 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
> 	at javax.naming.InitialContext.init(InitialContext.java:242)
> 	at javax.naming.InitialContext.<init>(InitialContext.java:216)

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