Well, it may be. But why it happens on finalizing a component and not when injecting EMs?
Also, if it is a classpath problem, I would expect to see it everytime, not in few, exact conditions. Isn't that there is a classloader problem somewhere? Like, say, the tomcat's thread pool is grown from a different classloader then the one that creates the initial pool. (NOTE NOTE: just guessing). Or... I have this in jboss-app.xml: | <jboss-app> | <loader-repository>seam.jboss.org:loader=mywebapp</loader-repository> | <module><service>login-service.xml</service></module> | </jboss-app> | Is it this the problem? I faithfully copied this on suggestion. I don't even know what's supposed to do... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939076#3939076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939076 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
