You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jay D. McHugh (JIRA)" <ji...@apache.org> on 2009/10/02 22:52:23 UTC
[jira] Created: (GERONIMO-4901) Shutting down Geronimo destroys
pending Timers
Shutting down Geronimo destroys pending Timers
----------------------------------------------
Key: GERONIMO-4901
URL: https://issues.apache.org/jira/browse/GERONIMO-4901
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: OpenEJB
Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0
Environment: Geronimo 2.1.4
Reporter: Jay D. McHugh
Here is what SEEMS to be happening:
Shutting down and bringing Geronimo back up seems to be effectively undeploying everything, then redeploying it.
So, pending Timers are being destroyed.
This may not be the actual cause of this - Based upon the log entries during shutdown and restart.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4901) Shutting down Geronimo destroys
pending Timers
Posted by "Jay D. McHugh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761772#action_12761772 ]
Jay D. McHugh commented on GERONIMO-4901:
-----------------------------------------
Here is a portion of the geronimo.log file that seems to show my app being disassembled
during shutdown and reconstituted during startup:
(Using current 2.1.5 snapshot as of 10/02/2009)
During shutdown:
2009-10-02 18:01:56,810 INFO [startup] Undeploying app: /opt/geronimo-tomcat6-javaee5-2.1.5-SNAPSHOT/var/temp/geronimo-deploymentUtil4824243862298920212.jar
2009-10-02 18:01:56,835 INFO [startup] Undeploying app: /opt/geronimo-tomcat6-javaee5-2.1.5-SNAPSHOT/var/temp/geronimo-deploymentUtil1436047464632244742.jar
2009-10-02 18:02:02,120 INFO [startup] Undeploying app: /usr/src/mavenRepository/org/apache/geronimo/plugins/geronimo-mejb/2.1.5-SNAPSHOT/geronimo-mejb-2.1.5-SNAPSHOT.jar
2009-10-02 18:02:02,163 INFO [remote] Received stop signal
While coming back up - after starting all of the Geronimo services:
2009-10-02 18:10:54,602 INFO [startup] Assembling app: /opt/geronimo-tomcat6-javaee5-2.1.5-SNAPSHOT/var/temp/geronimo-deploymentUtil4824243862298920212.jar
2009-10-02 18:10:58,546 INFO [startup] Jndi(name=ComponentClassBeanLocal) --> Ejb(deployment-id=palmBeans.jar/ComponentClassBean)
2009-10-02 18:10:58,547 INFO [startup] Jndi(name=VClean7Local) --> Ejb(deployment-id=palmBeans.jar/VClean7)
2009-10-02 18:10:58,547 INFO [startup] Jndi(name=GenericComponentBeanLocal) --> Ejb(deployment-id=palmBeans.jar/GenericComponentBean)
2009-10-02 18:10:58,547 INFO [startup] Jndi(name=VClean2Local) --> Ejb(deployment-id=palmBeans.jar/VClean2)
2009-10-02 18:10:58,547 INFO [startup] Jndi(name=ESDBeanLocal) --> Ejb(deployment-id=palmBeans.jar/ESDBean)
......
> Shutting down Geronimo destroys pending Timers
> ----------------------------------------------
>
> Key: GERONIMO-4901
> URL: https://issues.apache.org/jira/browse/GERONIMO-4901
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: OpenEJB
> Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0
> Environment: Geronimo 2.1.4
> Reporter: Jay D. McHugh
>
> Here is what SEEMS to be happening:
> Shutting down and bringing Geronimo back up seems to be effectively undeploying everything, then redeploying it.
> So, pending Timers are being destroyed.
> This may not be the actual cause of this - Based upon the log entries during shutdown and restart.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.