Here's an excerpt from a stack trace I just got out of jboss:
[Auto deploy] Auto undeploy of file:/tools/jboss_jetty/jboss-PRE-2.1/deploy/t8.ear
[J2EE Deployer] Stopping module factory.jar
[Container factory] Undeploying:file:/tools/jboss_jetty/jboss-PRE-2.1/bin/../tmp/deploy/t8.ear/ejb1043.jar
[Container factory] java.rmi.ServerException: Could not passivate; nested exception is:
[Container factory] java.io.NotSerializableException: au.com.asc.ejb2html.HTMLFragmentFactory
[Container factory] java.io.NotSerializableException: au.com.asc.ejb2html.HTMLFragmentFactory
[Container factory] at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
[Container factory] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
[Container factory] at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
[Container factory] at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
[Container factory] at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
[Container factory] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
[Container factory] at org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:271)
[Container factory] at org.jboss.ejb.plugins.StatefulSessionInstanceCache.passivate(StatefulSessionInstanceCache.java:54)
[Container factory] at org.jboss.ejb.plugins.EnterpriseInstanceCache$1.execute(EnterpriseInstanceCache.java:341)
[Container factory] at org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:199)
[Container factory] at java.lang.Thread.run(Thread.java:484)
[Container factory] Undeployed application: file:/tools/jboss_jetty/jboss-PRE-2.1/bin/../tmp/deploy/t8.ear/ejb1043.jar
[J2EE Deployer] Stopping module test.war
[Jetty] Stopped SecurityHandler in file:/tools/jboss_jetty/jboss-PRE-2.1/tmp/deploy/t8.ear/war1042/
[Jetty] test: destroy
[Jetty] Stopped ServletHandler in file:/tools/jboss_jetty/jboss-PRE-2.1/tmp/deploy/t8.ear/war1042/
[Jetty] Stopped ResourceHandler in file:/tools/jboss_jetty/jboss-PRE-2.1/tmp/deploy/t8.ear/war1042/
[Jetty] trying - /test/* - file:/tools/jboss_jetty/jboss-PRE-2.1/tmp/deploy/t8.ear/war1042/
[Jetty] found WebApp for removal : 0
[J2EE Deployer] Destroying application t8.ear
[J2EE Deployer] deployment.cfg file deleted.
[Container factory] java.lang.NullPointerException
[Container factory] at org.jboss.util.LRUCachePolicy.insert(LRUCachePolicy.java:152)
[Container factory] at org.jboss.ejb.plugins.EnterpriseInstanceCache$1.execute(EnterpriseInstanceCache.java:352)
[Container factory] at org.jboss.util.WorkerQueue$QueueLoop.flush(WorkerQueue.java:218)
[Container factory] at org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:194)
[Container factory] at java.lang.Thread.run(Thread.java:484)
[Container factory] java.lang.NullPointerException
[Container factory] at org.jboss.util.LRUCachePolicy.insert(LRUCachePolicy.java:152)
[Container factory] at org.jboss.ejb.plugins.EnterpriseInstanceCache$1.execute(EnterpriseInstanceCache.java:352)
[Container factory] at org.jboss.util.WorkerQueue$QueueLoop.flush(WorkerQueue.java:218)
[Container factory] at org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:194)
[Container factory] at java.lang.Thread.run(Thread.java:484)
[Container factory] java.lang.NullPointerException
[Container factory] at org.jboss.util.LRUCachePolicy.insert(LRUCachePolicy.java:152)
[J2EE Deployer] File tree file:/tools/jboss_jetty/jboss-PRE-2.1/tmp/deploy/t8.ear deleted.
[Container factory] at org.jboss.ejb.plugins.EnterpriseInstanceCache$1.execute(EnterpriseInstanceCache.java:352)
and the NPEs just keep on coming. When I Ctrl-C'd it, it had put about 1Mb of log on disk, about 99% of which is NPEs.
The first stack trace seems to be a result of trying to passivate a stateful session bean which is being undeployed; surely it shouldn't try to do this?
The second might be connected to this, but I don't really have any ideas on it; it looks like a bug to me, though.
I'm using the jboss-jetty distro off the web site, which has the 'URL caching on re-deploy' bug. I'm working around this by renaming the EAR file each time I deploy (t1.ear, t2.ear ...) and as you can see this was the eighth time I'd deployed it, and there had been no problems previously.
BTW is there a fix for the URL caching bug in CVS?
Also, any sign of bugzilla coming back?
Tom
--
Tom Cook
Systems Development
Australian Submarine Corporation
Mersey Road
Outer Harbour
+61 8 8348 7645
"From the instant I picked your book up, until the moment I put it down, I was convulsed with laughter. I fully intend to read it one day."
- Groucho Marx
