Uploaded image for project: 'JBoss Remoting (3+)'
  1. JBoss Remoting (3+)
  2. REM3-169

ChannelBusyException as a result of remoting server ignoring client capabilities on auth failure with one of the authentication mechanisms

    XMLWordPrintable

    Details

      Description

      When running the performance test found here:

      https://github.com/rhnordics/netent-remote-app

      Eventually every thread fails with the following exception:

      java.lang.reflect.UndeclaredThrowableException
            at $Proxy0.execute(Unknown Source)
            at se.redhat.supportcase.netent.client.RemoteClient.execute(RemoteClient.java:60)
            at main.Main$1.run(Main.java:44)
            at java.lang.Thread.run(Thread.java:722)
      Caused by: org.jboss.remoting3.ChannelBusyException: JBREM000207: Failed to send a message (channel is busy)
            at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:313)
            at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:249)
            at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:196)
            at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
            at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
            at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
            at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
            at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
            at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
            at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
            at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
            ... 4 more
      

      There doesn't have to be a huge load on the client side, but this does make all the threads fail faster. Also note that the client and server need to be on different machines (ie you can't use 'localhost') to reproduce the problem.

        Attachments

          Activity

            People

            Assignee:
            dmlloyd David Lloyd
            Reporter:
            klape Kyle Lape
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: