If you are using RH HEAD (with Jetty), then the answer is "YES".
I hadn't thought of this.
TimeOuts are run on a shared background thread to save stack.
I could either run a separate thread per webapp instance - expensive, or cache a reference to the classloader with each timeout and reset it when I run the timeout???
I'll think about it.
Thanks for bringing this to my attention.
Have you tried theis on Tomcat (standalone or with JBoss?). What behaviour do you see ?
We are currently using JBoss 2.4.4 with Tomcat 4.0.1. So it seems that Tomcat has the same problem as Jetty. Do you know if there is any quick solution to that. We are planning to go 'live' with this in about a month or so.
Sorry I spelled your name wrong in the reply before.
I've checked a fix into the Jetty integration to handle this.
I would be interested to hear if this works for you, and any other problems that prevent you from using Jetty over TomCat.
As far as TomCat goes, it's a 3rd-party app with no particular affiliation to JBoss. If you need a bug fixed you will have to approach that project on bended knee.
Sorry I can't be of more help.....
If you are feeling daring, fix TomCat and run on that if they won't take your changes back.
It is for exactly this sort of reason that JBoss ships with Jetty by default. The Jetty community is determined to make the JBoss/Jetty integration a success by integrating the two as tightly as possible and resolving problems thrown up by this integration ASAP. You would not have had to wait the time that you have if my monitor had not blown up and my laptop battery given up the ghost.....