[jira] Commented: (JS1-540) Continuously increasing number of Oracle sessions

["Jeremy Ford (JIRA)" <je...@jakarta.apache.org>]

     [ http://issues.apache.org/jira/browse/JS1-540?page=comments#action_62020 ]
     
Jeremy Ford commented on JS1-540:
---------------------------------

By default, Jetspeed uses the TorqueDataSourceFactory for session pooling.  This is a rather old factory and Torque suggests using the Jdbc2PoolDataSourceFactory.  Try changing your Torque.properties file to use the Jdbc2PoolDataSourceFactory and see if this resolves the issue.

> 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: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org