Re: Tomcat 6.x leak with WSS4J library

2013-06-20 Thread Jose María Zaragoza
Thanks you very much, Christopher : 1) Finally - -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false worked for me, but I want to find out the root cause for leaking. I afraid to accelerate OOM in PermGen with many redeploys 2) Perhaps a container-loaded component

Tomcat 6.x leak with WSS4J library

2013-06-19 Thread Jose María Zaragoza
Hello: This isn't an error in Tomcat, but it's an error what happens in my web application by using Apache CXF + WSS4J. I'm using Tomcat 6.0.24 and I've found that it's fixed in 7.0.41 ( but not in 6.03.7 ) But , for bussiness matters, I cannot upgrade from 6.0.24 to 7.x I would like if

Re: Tomcat 6.x leak with WSS4J library

2013-06-19 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jose, On 6/19/13 11:04 AM, Jose María Zaragoza wrote: This isn't an error in Tomcat, but it's an error what happens in my web application by using Apache CXF + WSS4J. I'm using Tomcat 6.0.24 and I've found that it's fixed in 7.0.41 ( but

Re: Tomcat 6.x leak with WSS4J library

2013-06-19 Thread Jose María Zaragoza
Thanks ! You should at least upgrade to 6.0.37. 6.0.24 I agree with you but I can't. Anyway, I tested my webapp in Tomcat 6.0.37 and it throws the same error; it only works in latest Tomcat 7.x Why is your web application attempting to get a message's signature during shutdown? I explained

Re: Tomcat 6.x leak with WSS4J library

2013-06-19 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jose, On 6/19/13 5:02 PM, Jose María Zaragoza wrote: Thanks ! You should at least upgrade to 6.0.37. 6.0.24 I agree with you but I can't. Anyway, I tested my webapp in Tomcat 6.0.37 and it throws the same error; it only works in latest