OTM Session Timeout

[naveengupta4s]

Hi,

I'm facing this issue of frequent Server Timeout displaying the error as "503 Service Temporarily Unavailable". We are having OTM 5.5 CU3 installed on a 4GB Server with a SGA of 500 MB in Linux environment. The link to the server gets reestablished after a few seconds time delay & on browser refresh directs back to the login window.

Any early suggestions in this regard are highly appreciated.

Thanks in advance,

Naveen

[chrisplough]

Re: OTM Session Timeout

Naveen,

It sounds like you may not have enough physical memory to support your Java heaps. Could you post your $OTM_HOME/tomcat/bin/tomcat.conf and $OTM_HOME/weblogic/config/gc3domain/weblogic.conf files? Or, at the very least, list the Java heap sizes defined in each? Also, what OS are you running on?

Another possibility is that not enough memory is allocated to Tomcat, causing it to freeze when unable to garbage collect -- which Java Service Wrapper detects and forces a restart of the Tomcat service. You can determine if this is happening by monitoring the console.log files for Tomcat and WebLogic: $OTM_HOME/logs/tomcat/console.log and $OTM_HOME/logs/weblogic/console.log.

Thanks,
Chris

[naveengupta4s]

Re: OTM Session Timeout

Hi Chris,

Attached is the tomcat.conf file as mentioned. We are using Linux RHEL ES4 hence have not installed weblogic. Regarding the Java heap sizes, if you can just mention the file/location where this value is mentioned, I can revert on that as well.

Many Thanks & Regards,
Naveen

[chrisplough]

Re: OTM Session Timeout

Naveen,

Your tomcat.conf file looks fine and your Tomcat Java heap size is 1024MB, so you should have at least 2.5GB of physical memory installed on your server (1024MB for Java heap, 768MB for JRockit caching and overhead, 256MB for Apache and 512MB for Linux OS). This will ensure that you don't run out of memory and start swapping heavily, which would cause issues similar to what you described. Otherwise, I don't see any issues with this configuration.

Your next steps will be to verify the Tomcat console.log file to see if exceptions are being thrown, or if Tomcat is unexpectedly restarting. This log file is located on your OTM Web server under $OTM_HOME/logs/tomcat/console.log.

Also - it appears that you're running OAS instead of WebLogic as the OTM App server (note: both WebLogic and OAS are supported on Linux, so either can be used with RHEL ES4). Double-check your OAS logs for any connection errors - indicating issues with the connection between Tomcat and OAS.

Feel free to post any of these logs here and I can take a look as I'm able.

Thanks,
Chris