java - What's your experience with adding SSL to Tomcat 6? -
At the weekend we have added SSL protection in a Tomcat 6 example, which is running for a while without error. In the morning, after increasing the number of sessions on machines, Tommack began to throw 500 errors to users. I checked the logs and found an example of out-of-memory memorisation, after which Google Guice attempted to introduce new threads of errors. I can only do the image that with the addition of SSL, more threads are being used, or more storage is being used than such a situation, I am not sure where and how to use additional resources going.
I was hoping that people with experience using SSL on Tomcat can tell me in some directions on places to find clues. At the moment I am not sure where this issue can be. Here are some statistics about our setup and configuration:
-XX: Threadstacks = 512
Initial memory pool: 128MB
Maximum memory pool: 1024MB
Thread Stack size: 512 kb
I am adjusting them in different ways to try at least towards success. Up to now, the performance starts reducing after about 5 minutes after the server restarts. Any direction will be greatly appreciated.
Here's a possibility, though it's a bit of a long shot: the browser is much less than the HTC content Aggressively cache an https content. Therefore, if your end users are now accessing the service on HTTPS, but more than HTTP already, you want to handle a lot of requests (though with the same number of sessions).
On not accepting this, I want to go above the suggestion of Matt B.; To find the profile where the heap is being used add -robbose: gc-xloggc: /path/to/where/you/want/gc.log to your startup JVM arguments, And use gc.log to see if you can jump in the heap size jmap-dump: format = b, file = / path / to / dump {tomcat PID} with special sequences of requests. Use to generate a heap dump. If you take one immediately after starting Tomcat, and when it starts dying, you can use jhat to show the difference between the two.
Comments
Post a Comment