views:

38

answers:

1

acording to the docs on service lifecycle i should be able to implement RegistryShutdownListener and tidy up my resources (in this case, shutdown a threadpool) however it is throwing an exception and seems to be trying to re-initialise my service in order to perform the shutdown listener!?

2010-01-14 10:59:01,750 [main] ERROR org.apache.hivemind.impl.ShutdownCoordinatorImpl - Unable to shutdown <SingletonProxy for svc.MyService($MyService_1262a1db992)>: Unable to construct service svc.MyService: The HiveMind Registry has been shutdown.
org.apache.hivemind.ApplicationRuntimeException: Unable to construct service svc.MyService: The HiveMind Registry has been shutdown.
    at org.apache.hivemind.impl.servicemodel.AbstractServiceModelImpl.constructNewServiceImplementation(AbstractServiceModelImpl.java:166)
    at org.apache.hivemind.impl.servicemodel.AbstractServiceModelImpl.constructServiceImplementation(AbstractServiceModelImpl.java:140)
    at org.apache.hivemind.impl.servicemodel.SingletonServiceModel.getActualServiceImplementation(SingletonServiceModel.java:69)
    at $$MyService_1262a1db992_1262a1db994._service($$MyService_1262a1db992_1262a1db994.java)
    at $$MyService_1262a1db992_1262a1db994.registryDidShutdown($$MyService_1262a1db992_1262a1db994.java)
    at $$MyService_1262a1db992_1262a1db993.registryDidShutdown($$MyService_1262a1db992_1262a1db993.java)
    at org.apache.hivemind.impl.ShutdownCoordinatorImpl.shutdown(ShutdownCoordinatorImpl.java:97)
    at org.apache.hivemind.impl.ShutdownCoordinatorImpl.shutdown(ShutdownCoordinatorImpl.java:80)
    at org.apache.hivemind.impl.RegistryInfrastructureImpl.shutdown(RegistryInfrastructureImpl.java:379)
    at org.apache.hivemind.impl.RegistryImpl.shutdown(RegistryImpl.java:94)
    at org.apache.tapestry.ApplicationServlet.destroy(ApplicationServlet.java:322)
    at org.apache.catalina.core.StandardWrapper.unload(StandardWrapper.java:1394)
    ...
Caused by: org.apache.hivemind.ApplicationRuntimeException: The HiveMind Registry has been shutdown.
    at org.apache.hivemind.impl.RegistryInfrastructureImpl.checkShutdown(RegistryInfrastructureImpl.java:404)
    at org.apache.hivemind.impl.RegistryInfrastructureImpl.getServicePoint(RegistryInfrastructureImpl.java:153)
    at org.apache.hivemind.impl.ModuleImpl.getServicePoint(ModuleImpl.java:169)
    at org.apache.hivemind.impl.InvokeFactoryServiceConstructor.setupFactoryAndParameters(InvokeFactoryServiceConstructor.java:78)
    at org.apache.hivemind.impl.InvokeFactoryServiceConstructor.constructCoreServiceImplementation(InvokeFactoryServiceConstructor.java:55)
    at org.apache.hivemind.impl.servicemodel.AbstractServiceModelImpl.constructCoreServiceImplementation(AbstractServiceModelImpl.java:108)
    at org.apache.hivemind.impl.servicemodel.AbstractServiceModelImpl.constructNewServiceImplementation(AbstractServiceModelImpl.java:158)
    ... 31 more

Hivemodule.xml:

<service-point id="MyService" interface="package.MyService">
    <invoke-factory><construct class="package.MyService" /></invoke-factory>
</service-point>

package.MyService.java:

public class MyService implements RegistryShutdownListener
{
...
    private ExecutorService executors;

    private void intitialise()
    {
...
    executors = Executors.newFixedThreadPool(3);
...
    }

...

    @Override
    public void registryDidShutdown()
    {
        if (executors.isShutdown())
            return;
        executors.shutdown();
    }
}

ps i understand that you can't refer to another hivemind service in registryDidShutdown() but executors isn't a hivemind service AFAIK, it's part of java.util.concurrent

A: 

after finding this i can see that it's a bug. work around is to use an interface for the service (something i skip sometimes) instead of using the implementation for both construction and interface in hivemodule.

pstanton