4.0.1 dying daily
Sindre something is going on with 4.01 where the servlet is dying within tomcat and I have to restart tomcat to get the server back up and running. Tomcat process is still running strong but the subsonic servlet is dead and non responsive. Here's an error within the tomcat log I'm seeing:
May 23, 2010 2:48:27 PM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status
This has happened twice and it's staying up an avg of 2 to 3 days only whereas before it would be up for months. The subsonic log isn't showing anything what other log would be effective for what is happening? This is still happening where it'll be up for a day or two and then the server just quit responding yet tomcat processes are still alive and active so therefore something in the java has to be dying. Can't really find anything in the logs other than the max threads above.
Now it's happening every 24 hrs and occasoinally I have to delete the subsonic folder and restart tomcat and let the war redeploy the code as it's getting corrupted somehow.
I've never had any issues with this until I went to 4.0.1 and I'm not seeing anything really within the subsonic log or the tomcat logs as to why its happening.
May 23, 2010 2:48:27 PM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status
This has happened twice and it's staying up an avg of 2 to 3 days only whereas before it would be up for months. The subsonic log isn't showing anything what other log would be effective for what is happening? This is still happening where it'll be up for a day or two and then the server just quit responding yet tomcat processes are still alive and active so therefore something in the java has to be dying. Can't really find anything in the logs other than the max threads above.
Now it's happening every 24 hrs and occasoinally I have to delete the subsonic folder and restart tomcat and let the war redeploy the code as it's getting corrupted somehow.
I've never had any issues with this until I went to 4.0.1 and I'm not seeing anything really within the subsonic log or the tomcat logs as to why its happening.