Sporadic error

[apinto]

Hi there,

I'm using OSS/J Inventory system over JBoss. Sometimes, tipically when the system is running for some time, calls to the API fail with the following error:

java.rmi.NoSuchObjectException: Could not activate; CausedByException is:
/usr/local/jboss-3.0.4_tomcat-4.1.12/server/all/db/sessions/JVTResourceInventorySessionEJB/1052410963901.ser (No such file or directory)

at org.jboss.ejb.plugins.AbstractInstanceCache.get(AbstractInstanceCache.java:186)

at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:212)

at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:204)

at org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:380)

at org.jboss.ejb.Container.invoke(Container.java:712)

at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)

at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:382)

at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)

at sun.rmi.transport.Transport$1.run(Transport.java:148)

at java.security.AccessController.doPrivileged(Native Method)

at sun.rmi.transport.Transport.serviceCall(Transport.java:144)

at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)

at java.lang.Thread.run(Thread.java:536)


Can someone please help me? Thanks in advance.

Cirruz

[raja05]

Jboss Passivates instances of ur session bean and its not finding the beans when it needs to activate it.
I have seen a similar error being posted in the EJB forums. Try a search on that newsgroup.
Try increasing the number of session beans in memory or tweak the container-configurations. That might help.

[juhalindfors]

Also you might want to add some logging to your ejbPassivate to see how long the session has been passivated before this happens (ie. has the scavenger thread already removed the passivated session from disk before you try to activate it again.)

[apinto]

Thanks, where can I configure the maximum number of session beans? In standardjboss.xml?

Cirruz

[raja05]

Override the container-configuration in your jboss-xml and change the value of "max-bean-life" in the container-cache-conf section.

this is by default 1800. Increase this to a higher value and check if the error still persists.

Look in LRUStatefulContextCachePolicy.java for how this is removed from cache.

-Raj