Bugs item #548051, was opened at 2002-04-24 05:31
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=548051&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Christian Riege (lqd)
Assigned to: Scott M Stark (starksm)
Summary: Bug in StatefulSessionInstanceCache
Initial Comment:
There seems to be a rather serious bug regarding
Stateful Session Beans. After having my server running
for a time I got this exception:
13:47:39,083 ERROR [STDERR] java.lang.NullPointerException
13:47:39,083 ERROR [STDERR] at
org.jboss.ejb.plugins.StatefulSessionInstanceCache.removePassivated(StatefulSessionInstanceCache.java:127)
13:47:39,083 ERROR [STDERR] at
org.jboss.ejb.plugins.LRUStatefulContextCachePolicy$RemoverTask.run(LRUStatefulContextCachePolicy.java:138)
13:47:39,083 ERROR [STDERR] at
java.util.TimerThread.mainLoop(Timer.java:430)
13:47:39,083 ERROR [STDERR] at
java.util.TimerThread.run(Timer.java:380)
the server continues to run but once a jar gets
deployed/redeployed, the stacktraces just go on and on
(just the first part of the trace, can post more if
wanted):
14:19:06,259 ERROR [EntityContainer] Exception in
service lifecyle operation: start
java.lang.IllegalStateException: Timer already cancelled.
at java.util.Timer.sched(Timer.java:310)
at java.util.Timer.schedule(Timer.java:126)
at
org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy.start(LRUEnterpriseContextCachePolicy.java:129)
at
org.jboss.ejb.plugins.AbstractInstanceCache.start(AbstractInstanceCache.java:308)
at
org.jboss.ejb.EntityContainer.start(EntityContainer.java:373)
[...]
this is against an 3.0.0RC1 build as of yesterday.
BTW: The client accessing the StatefulSessionBean
didn't call remove() on it so it had been idling in the
container for a while ...
sorry if this report is not clear enough but i don't
have sufficient time to evaluate this further right now.
----------------------------------------------------------------------
>Comment By: Scott M Stark (starksm)
Date: 2002-04-25 02:31
Message:
Logged In: YES
user_id=175228
Try the Branch_3_0 fix and reopen with more information on
the app if the exceptions still exist.
----------------------------------------------------------------------
Comment By: Scott M Stark (starksm)
Date: 2002-04-24 11:16
Message:
Logged In: YES
user_id=175228
Its all part of the container memory leak cleanup showing
that the passivation threads usage is not well designed
with regard to container shutdowns. I'll look at fixing
this.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=548051&group_id=22866
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
