Uploaded image for project: 'HiveMind'
  1. HiveMind
  2. HIVEMIND-206

registryDidShutdown not called on Hivemind services on undeploy

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.1.1
    • Fix Version/s: 4.1.2
    • Component/s: None
    • Labels:
      None
    • Environment:
      Tomcat 5, Java 1.6

      Description

      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.

        Attachments

        1. HivemindSchedulerFactory.txt
          2 kB
          Michael Gloegl
        2. hivemodule.xml
          1 kB
          Michael Gloegl

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gloeglm Michael Gloegl
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: