You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Serlet Jean-Claude <je...@insee.fr> on 2006/03/13 15:08:43 UTC
TR: Time out on sessions with AJP13
> Hello
> Third and last send of this message : i didn't get any answer until to
> day
>
> My environment : OS= Windows 2000
> Web Server = Apache 2.0
> Tomcat-Apache = 1.4.31 with AJP 13 connector
> Application uses JSP, Servlet and Driver JDBC Thin of Oracle
> RDBMS = Oracle 7.3.62 under z/OS (mainframe IBM)
> The application does'nt use connexion pooling : one physical connexion is
> used for each user
> The connexion is explicitly closed only when the user click on the button
> "Quit" of the application
> What's happen when a session is timed out ( without activity during the
> time set in web.xml)
> for the processor(limited by maxProcessor of ajp13) in which the last
> request was executed ? does this processor be released ?
> what's happen for the connexion to the database ?
> i didn't find documentation for this situation on the web : only about
> "howto" configure AJP13 connector ( that is done )
> Last day i have to reboot the tomcat instance because the maxProcessor was
> reached ( saw it in the log of Tomcat )
> I suppose that many users don't quit the application properly
> I see many more sessions open in the database than users connected ( under
> z/os the connection not cleanly closed stay ther
> until the shutdown of database)
> Any idea about the code built by the developpers : i asked them to close
> properly every object created after the end of its use specially "prepare
> statement, result set..."?
> Regards
>
> jean-claude.serlet@insee.fr
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: TR: Time out on sessions with AJP13
Posted by Mark Thomas <ma...@apache.org>.
Serlet Jean-Claude wrote:
>>Third and last send of this message : i didn't get any answer until to
>>day
http://tomcat.apache.org/faq/tomcatuser.html#why
>>The application does'nt use connexion pooling : one physical connexion is
>>used for each user
A connection pool would help you here. Alternatively look at using an
HttpSessionListener.
>>The connexion is explicitly closed only when the user click on the button
>>"Quit" of the application
This is bad. You have no guarantee that the user will click this button.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org