>>>>> "JA" == Jim Archer <[EMAIL PROTECTED]> writes:
JA> We have seen this behavior as well. If we have an error in the
JA> matching of our bean interface and our remote interface (a
JA> different parameter list or exception list, for example) and my
JA> client calls into the app (I think and call to any bean will do
JA> it, but I'm not sure and the client is a servlet in a WAR file in
JA> the EAR) jBoss 2.2.1_Tomcat 3.2.1 will start launching threads. It
JA> will continue to do so until the kernel thread limit (we have it
JA> set right now to 256 threads) is hit, then it will become
JA> uncontrolable.
Yep. *sigh* Nasty. But does it really have to do this?
JA> We have never seen this happen of the EJB JAR has no errors of the
JA> type I described. It was a concern to us as well, but soince it
JA> only happens when we have a bug, we decided to just be carefull.
JA> I would be interested to know if you find the cause of this on
JA> your system, especially if it is different than thr cause on
JA> mine. Its easy to miss this error if you have many beans, as the
JA> verifier messages scroll off the window quickly.
Yes. This happens when the file to be deployed does not pass the
verifier test, has a method missing on it's home interface
etc... etc... etc... I can confirm your experiences. However, I am
seriously concerned about this "feature" for JBoss in a production
environment.
--
Nicolai P Guba http://www.gnu.org http://www.frontwire.com
mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
GSM: +44 (0)7909 960 751 DDI: +44 (0)20 7368 9708
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
