[
https://issues.apache.org/jira/browse/TAPESTRY-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert updated TAPESTRY-1226:
------------------------------------
Fix Version/s: 4.1.2
> registryDidShutdown not called on Hivemind services on undeploy
> ---------------------------------------------------------------
>
> Key: TAPESTRY-1226
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1226
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 4.1
> Environment: Tomcat 5, Java 1.6
> Reporter: Michael Gloegl
> Fix For: 4.1.2
>
> Attachments: HivemindSchedulerFactory.txt, hivemodule.xml
>
>
> When undeploying a Tapestry app from the Server, registryDidShutdown does not
> get called on services implementing the RegistryShutdownListener interface. I
> had to do a manual call to shutdownCoord.addRegistryShutdownListener(this);
> for the notification to work.
> I verified that _registry.shutdown() gets called in the destroy() method of
> the Tapestry servlet, however the listener does not get notified.
> Attatched are the Service and the hivemodule.xml I used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
