| Key: |
JS1-540
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Vesa
|
| Votes: |
1
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Windows/Linux, Tomcat4.1/Tomcat5.0
|
|
|
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.
|
|
Description
|
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. |
Show » |
| No work has yet been logged on this issue.
|
|
Continuously increasing number of Oracle sessions
