0 Replies Latest reply on Jun 17, 2003 8:37 AM by ddesmeu

    Jboss node not answering during load test using clustering

    ddesmeu Newbie

      Hi, I'm running jboss 3.2.1 (same problem happens with 3.0.(7|8)). This problem happens pretty consistently during a load test. It can take more than 12 hours before it happens. Once it happened, jboss seems to be totally locked. It doesn't even go to the jmx-console anymore. I see the following stack trace in the logs. (Sorry for the strange output, we use our own layout for the logs)
      The process eventually ran out of memory after that.
      I'm planning on trying 3.2.2 rc1 to see if it helps.
      Any idea what could be the problem ?

      I'm using clustering without farming and my config is an almost complete "all" configuration (without the jbossnet.sar since I use another version of axis)

      20,de0aa8c0_00000674_3dd59030_0004_0000-88113,LOG,ERROR,0,2003/06/16 23:59:41.548,mtl-sust14,CTI Gateway,d0ddf0f2-0a03-0196-001d-332bc313551b,744287928,org.jboss.ejb.plugins.LogInterceptor,LogInterceptor.java:336,7081,EJBException:
      javax.ejb.EJBException: No entry exists (any more?) with this id: feBlwd53I82D1V1TFLbdOw**
      at org.jboss.ejb.plugins.CMPClusteredInMemoryPersistenceManager.loadEntity(CMPClusteredInMemoryPersistenceManager.java:367)
      at org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity(CMPPersistenceManager.java:386)
      at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:232)
      at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:174)
      at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:89)
      at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
      at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
      at org.jboss.ha.httpsession.beanimpl.ejb.ServerTCLInterceptor.invoke(ServerTCLInterceptor.java:40)
      at org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:483)
      at org.jboss.ejb.Container.invoke(Container.java:674)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101)
      at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:83)
      at org.jboss.ha.httpsession.beanimpl.ejb.ClientTCLInterceptor.invoke(ClientTCLInterceptor.java:41)
      at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:164)
      at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85)
      at $Proxy27.remove(Unknown Source)
      at org.jboss.ha.httpsession.server.ClusteredHTTPSessionService.removeHttpSession(ClusteredHTTPSessionService.java:161)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy36.removeHttpSession(Unknown Source)
      at org.jboss.web.catalina.session.ClusterManager.removeSession(ClusterManager.java:605)
      at org.jboss.web.catalina.session.ClusterManager.remove(ClusterManager.java:354)
      at org.jboss.web.catalina.session.ClusteredSession.expire(ClusteredSession.java:589)
      at org.jboss.web.catalina.session.ClusteredSession.invalidate(ClusteredSession.java:967)
      at org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:211)
      at org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:211)
      .......