java.util.concurrent.ExecutionException: javax.ejb.EJBException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node-0, see cause for remote stack trace

GitHub | wildfly-ci | 2 months ago
  1. 0

    GitHub comment 8961#251512887

    GitHub | 2 months ago | wildfly-ci
    java.util.concurrent.ExecutionException: javax.ejb.EJBException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node-0, see cause for remote stack trace
  2. 0

    GitHub comment 8992#255447560

    GitHub | 1 month ago | wildfly-ci
    java.util.concurrent.ExecutionException: javax.ejb.EJBException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node-0, see cause for remote stack trace
  3. 0

    GitHub comment 9303#256809579

    GitHub | 1 month ago | wildfly-ci
    java.util.concurrent.ExecutionException: javax.ejb.EJBException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node-0, see cause for remote stack trace
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 8580#241634993

    GitHub | 3 months ago | wildfly-ci
    java.util.concurrent.ExecutionException: javax.ejb.EJBException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node-0, see cause for remote stack trace
  6. 0

    GitHub comment 8998#242368071

    GitHub | 3 months ago | wildfly-ci
    java.util.concurrent.ExecutionException: javax.ejb.EJBException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node-0, see cause for remote stack trace

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. javax.ejb.EJBException

      org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node-0, see cause for remote stack trace

      at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run()
    2. JBoss Application Server: EJB Subsystem
      VersionOneProtocolChannelReceiver.processMessage
      1. org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:222)
      2. org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.processMessage(MethodInvocationMessageHandler.java:268)
      3. org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.processMessage(VersionOneProtocolChannelReceiver.java:213)
      3 frames
    3. WildFly: EJB Subsystem
      VersionTwoProtocolChannelReceiver.processMessage
      1. org.jboss.as.ejb3.remote.protocol.versiontwo.VersionTwoProtocolChannelReceiver.processMessage(VersionTwoProtocolChannelReceiver.java:76)
      1 frame
    4. JBoss Application Server: EJB Subsystem
      VersionOneProtocolChannelReceiver.handleMessage
      1. org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.handleMessage(VersionOneProtocolChannelReceiver.java:159)
      1 frame
    5. JBoss Remoting
      EndpointImpl$TrackingExecutor$1.run
      1. org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:456)
      2. org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:731)
      2 frames
    6. Java RT
      Thread.run
      1. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      2. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      3. java.lang.Thread.run(Thread.java:745)
      3 frames