Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-11455

(7.1.z) Legacy EJB client: Failed to open channel for context

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 7.1.0.DR19
    • EJB, Remoting
    • None

    Description

      We saw this error on client during failover scenarios where the legacy EJB client was used. Ejbservlet and ejbremote shutdown async scenarios are affected.

      Client log stacktrace:

      07:58:14,499 ERROR [org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver] (Remoting "config-based-ejb-client-endpoint" task-8) Failed to open channel for context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@758223be, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@518aab02,channel=jboss.ejb,nodename=perf18]}
      org.jboss.remoting3.NotOpenException: Cannot open new channel because close was initiated
      	at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:200)
      	at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:337)
      	at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:112)
      	at org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection.openChannel(ConnectionPool.java:292)
      	at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.associate(RemotingConnectionEJBReceiver.java:180)
      	at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:399)
      	at org.jboss.ejb.client.ClusterContext.registerEJBReceiver(ClusterContext.java:394)
      	at org.jboss.ejb.client.remoting.ClusterContextConnectionReconnectHandler.reconnect(ClusterContextConnectionReconnectHandler.java:70)
      	at org.jboss.ejb.client.EJBClientContext$ReconnectAttempt.run(EJBClientContext.java:1474)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:745)
      

      Error was logged on client during node (perf18) shutdown after deployment was stopped:

      07:58:14,467 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 484ms
      [JBossINF] [0m[0m07:58:14,517 INFO  [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: JBoss EAP 7.1.0.Beta1 (WildFly Core 3.0.0.Beta23-redhat-1) stopped in 532ms
      [JBossINF] [0m
      2017/06/08 07:58:14:986 EDT [DEBUG][RMI TCP Connection(53)-10.16.90.52] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Server is down.
      

      Link to client log:
      http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-legacy-ejb-ejbremote-shutdown-dist-async/3/console-perf17/

      Attachments

        Issue Links

          Activity

            People

              tadamski@redhat.com Tomasz Adamski
              dcihak@redhat.com Daniel Cihak
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: