[ http://issues.apache.org/jira/browse/JS1-540?page=comments#action_62065 ] Vesa commented on JS1-540: --------------------------
I've already tried that but Changing TorqueDataSourceFactory to Jdbc2PoolDataSourceFactory does not fix the problem. The behaviour remains the same. > Continuously increasing number of Oracle sessions > ------------------------------------------------- > > Key: JS1-540 > URL: http://issues.apache.org/jira/browse/JS1-540 > Project: Jetspeed > Type: Bug > Components: Database > Versions: 1.5 > Environment: Windows/Linux, Tomcat4.1/Tomcat5.0 > Reporter: Vesa > Priority: Critical > > If the user keeps the browser open until the session expires and after that > (he or anyone else) goes to login page (gets anonymous user profile) a new > Oracle session is created in database and the previously used one stays > inactive forever. This happens every time someone's session expires and a new > user logs in until we get 'ORA-00020: maximum number of processes (150) > exceeded' and Jetspeed crushes. > In addition to this a new database session is also created every eight hours > counting from the startup of Tomcat. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
