[MAGNOLIA-6353] (Database) sessions are kept alive after stopping the application using the console Created: 21/Aug/15  Updated: 11/Mar/21  Resolved: 11/Mar/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.1, 5.2, 5.3
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Teresa Miyar Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: devwl, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2015-08-21 at 08.06.32.png     PNG File Screen Shot 2015-08-21 at 08.27.36.png    
Issue Links:
Relates
relates to MAGNOLIA-4456 Leftover Jackrabbit thread after shut... Closed
relates to MAGNOLIA-6249 Eliminate log warnings and errors on ... Accepted
dependency
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Story Points: 8

 Description   

When using oracle 12c administration console, and Magnolia with Derby, you can stop the application, everything seems ok except for the guide thread that keeps running, see sreenshoots. When you try to restart the application you get the error "invalid session".
With JConsole you can see that all jcr sessions are still open.



 Comments   
Comment by Teresa Miyar [ 21/Aug/15 ]

Doing the same in Tomcat you can see the following trace:
Shutting down Log4J
ago 19, 2015 10:10:51 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/magnoliaAuthor] registered the JDBC driver [org.apache.derby.jdbc.AutoloadedDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
ago 19, 2015 10:10:51 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

That I think is why does not happen in Tomcat, using the manager you can start and stop the web app, it has a clearReferencesJdbc that does the cleanup

Comment by Jan Haderka [ 21/Aug/15 ]

In Tomcat you are shutting down whole server not just undeploying the app. If you try to only un-deploy and or re-deploy the app you end up with same problem also in Tomcat. This issue is not specific to Weblogic and unfortunately you can't just re-deploy, you always need to restart whole server.

Comment by Jan Haderka [ 11/Mar/21 ]

Restart of the server is going to be always necessary.

Generated at Mon Feb 12 04:13:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.