memory leaks

[Joshua Ellsworth]

I have had to restart tomcat twice in the last 3 days in order to get it to allow logins and password changes. The catalina.out log is full of entries like the following:

SEVERE: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.

SEVERE: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.

SEVERE: The web application [] appears to have started a thread named [Thread-55] but has failed to stop it. This is very likely to create a memory leak.

SEVERE: The web application [] appears to have started a thread named [Thread-56] but has failed to stop it. This is very likely to create a memory leak.

SEVERE: The web application [] appears to have started a thread named [Thread-57] but has failed to stop it. This is very likely to create a memory leak.

SEVERE: The web application [] appears to have started a thread named [Thread-58] but has failed to stop it. This is very likely to create a memory leak.

SEVERE: The web application [] appears to have started a thread named [Thread-59] but has failed to stop it. This is very likely to create a memory leak.

SEVERE: The web application [] appears to have started a thread named [Thread-60] but has failed to stop it. This is very likely to create a memory leak.

SEVERE: The web application [] appears to have started a thread named [Thread-61] but has failed to stop it. This is very likely to create a memory leak.

SEVERE: The web application [] appears to have started a thread named [Thread-62] but has failed to stop it. This is very likely to create a memory leak.

Any ideas for fixing this would be greatly appreciated. I do not think that the locally popular solution of cronning a restart of tomcat is the best way to go.

Josh

[Jason Rivard]

1) What is your java heap size set to?  

2) What does PWM-Admin -> Status -> show for max heap size and free memory?  

3) How much usage is your system getting

4) What version of tomcat and pwm are you running?

5) Are there any other errors in the catalina.out or other tomcat/log files?

--
You received this message because you are subscribed to the Google Groups "pwm-general" group.
To post to this group, send email to pwm-g...@googlegroups.com.
To unsubscribe from this group, send email to pwm-general...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.