0 Replies Latest reply on Jul 31, 2018 3:46 PM by wahoobill

    No such EJBException error using jboss 6.4.1

    wahoobill

      Hello,

       

      We are seeing the following error trying to fetch remote interface bean from our presentation layer.  The only way to correct this now is to

      restart the app server.  I have tried to look at jboss source code but no good indicators as to what root cause is.. We observe that AS still seems

      to be running fine as its processing messages, but nothing from the remote call is allowed-- Once this exception happens, it never

      gets cleared up other than a restart:

       

      7/30/2018 20:26:51,448 INFO  [play] (http-/10.7.108.29:39140-12) LoginChain: User PW last modified -1615 days ago. Expiration length is 180 days.

      07/30/2018 20:27:02,005 INFO  [org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler] (Remoting "config-based-naming-client-endpoint" task-12) Retrying invocation which failed on node master:opscenter-server01 with exception:: javax.ejb.NoSuchEJBException: No such EJB[appname=,modulename=opscenter,distinctname=,beanname=UserBean,viewclassname=com.consert.core.ejb.session.interfaces.UserBeanRemote]

              at org.jboss.ejb.client.remoting.NoSuchEJBExceptionResponseHandler.processMessage(NoSuchEJBExceptionResponseHandler.java:64) [jboss-ejb-client-1.0.30.Final-redhat-1.jar:1.0.30.Final-redhat-1]

              at org.jboss.ejb.client.remoting.ChannelAssociation.processResponse(ChannelAssociation.java:369) [jboss-ejb-client-1.0.30.Final-redhat-1.jar:1.0.30.Final-redhat-1]

              at org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver.handleMessage(ChannelAssociation.java:461) [jboss-ejb-client-1.0.30.Final-redhat-1.jar:1.0.30.Final-redhat-1]

              at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:451) [jboss-remoting-4.0.0.Final.jar:4.0.0.Final]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_72]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_72]

              at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_72]

       

      We are stuck-- Any idea?

       

      Thanks

      Bill Rodriguez

      Technical Lead for Advanced Load Management

      Landis&Gyr

      bill.rodriguez@landisgyr.com