Time out on sessions with AJP13

[Serlet Jean-Claude <je...@insee.fr>]

> Hello
Secund send of this message : i didn't see the first one in the digest i
received

> 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)
> 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