Session timeout - Apache overriding Tomcat?

[Manish Hatwalne]

The session timeout we have set for our application in Tomcat is 90 minutes, however session times out very quickly. When I did dig deeper, I found that Apache's timeout is 300 sec (5 mins) and I think the session timeout I experienced was similar.

I use Tomcat as my standalone server on my local machine and 90 mins timeout works fine on it. However, the live server we have uses Tomcat as plug-in and Apache as web-server -- only Java code is served by Tomcat, static files are served by Apache. I thought (or I have read before?), the Tomcat session timeout (configured in context's web.xml) will override the Apache default session timeout, but it doesn't see so - what could be the reason? Do I need to change Apache's session timeout as well?

Any pointers, help would be highly appreciated!

[Akhilesh Trivedi]

Why not change the timeout for Apache and check it out??

You may have to do decision making if Apache on live-server would be good or on configuring one on local, because i understand as per process developer can not access live-server.

[Manish Hatwalne]

I do not have access to apache configuration to check this out.