This exception has no message.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web4524

  • via Coderanch by Sudhakar Duraiswamy, 11 months ago
    This exception has no message.
  • via Coderanch by Delia Green, 7 months ago
    This exception has no message.
  • via Coderanch by Kemal Sokolovic, 8 months ago
    This exception has no message.
  • Stack trace

    • at org.jboss.remoting.transport.socket.SocketClientInvoker.transport( at org.jboss.remoting.transport.socket.SocketClientInvoker.transport( at org.jboss.remoting.RemoteClientInvoker.invoke( at org.jboss.remoting.RemoteClientInvoker.invoke( at org.jboss.remoting.Client.invoke( at org.jboss.remoting.Client.invoke( at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.invoke( at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$getClientAOPConfig_8697532701842707646.invokeNext(ClientConnectionFactoryDelegate$ at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.getClientAOPConfig( at org.jboss.jms.client.JBossConnectionFactory.ensureAOPConfigLoaded( at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal( at org.jboss.jms.client.JBossConnectionFactory.createConnection( at org.jboss.jms.client.JBossConnectionFactory.createConnection( at JBMService.JBMServiceImpl.init( at JBMService.Main.start( at JBMService.Main.main( Caused by: at at at at org.jboss.remoting.transport.socket.SocketClientInvoker.transport( ... 13 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Once, 2 days ago
    Once, 3 days ago
    Once, 1 week ago
    Once, 1 month ago
    4 times, 3 months ago
    15 more bugmates