Petals ESB Container

Delete endpoint failure at the stop of the container

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 3.1
  • Fix Version/s: 5.0.0
  • Component/s: Registry
  • Security Level: Public
  • Description:
    Hide

    When stopping Petals, the following message is displayed :

    SEVERE 2010-05-04 16:37:42,539 Failed to stop the component 'petals-bc-soap'
javax.jbi.messaging.MessagingException: org.ow2.petals.jbi.messaging.registry.RegistryException: Can not delete endpoint under > /endpoints/0/{http://orange.com/ros/services/movecustomer/v1}MoveCustomerService@MoveCustomerEndpoint2
  at org.ow2.petals.jbi.messaging.exchange.DeliveryChannelImpl.close(DeliveryChannelImpl.java:170)
  at org.ow2.petals.container.lifecycle.ComponentLifeCycle.doShutdown(ComponentLifeCycle.java:187)
  at org.ow2.petals.container.lifecycle.ComponentLifeCycle.stopComponentLifeCycle(ComponentLifeCycle.java:327)
  at org.ow2.petals.container.lifecycle.ComponentLifeCycle.stopFc(ComponentLifeCycle.java)
  at org.objectweb.fractal.julia.generated.Cbd2013d7_0.setFcContentState(BasicControllerMixin.java:8130)
  at org.objectweb.fractal.julia.generated.Cbd2013d7_0.setFcStopped(BasicControllerMixin.java:8087)
  at org.objectweb.fractal.julia.generated.C18c4c884_0.setFcStopped(INTERFACE[LifeCycleCoordinator])
  at org.objectweb.fractal.julia.generated.Cbd2013d7_0.stopFc(BasicControllerMixin.java:3187)
  at org.objectweb.fractal.julia.generated.Cbd2013d7_0.stopFc(BasicControllerMixin.java:4131)
  at org.objectweb.fractal.julia.generated.C18c4c884_0.stopFc(INTERFACE[LifeCycleCoordinator])
  at org.ow2.petals.kernel.server.FractalHelper.stopComponent(FractalHelper.java:379)
  at org.ow2.petals.kernel.server.PetalsServerImpl.stopPetalsComposite(PetalsServerImpl.java:508)
  at org.ow2.petals.kernel.server.PetalsServerImpl.stop(PetalsServerImpl.java:220)
  at org.ow2.petals.kernel.server.PetalsStopThread.run(PetalsStopThread.java:49)
Caused by: org.ow2.petals.jbi.messaging.registry.RegistryException: Can not delete endpoint under /endpoints/0/{http://orange.com/ros/services/movecustomer/v1}MoveCustomerService@MoveCustomerEndpoint2
  at org.ow2.petals.jbi.messaging.registry.BaseEndpointRegistry.deactivateEndpoint(BaseEndpointRegistry.java:179)
  at org.objectweb.fractal.julia.generated.C2304ecde_0.deactivateEndpoint(INTERCEPTOR[EndpointRegistry])
  at org.objectweb.fractal.julia.generated.C2eb804c9_0.deactivateEndpoint(INTERFACE[EndpointRegistry])
  at org.ow2.petals.jbi.component.context.ComponentContextImpl.deregisterAllEndpoints(ComponentContextImpl.java:236)
  at org.ow2.petals.jbi.messaging.exchange.DeliveryChannelImpl.close(DeliveryChannelImpl.java:168)
  ... 13 more
Caused by: org.ow2.petals.registry.api.exception.RegistryException: net.sf.ehcache.CacheException: org.ow2.petals.registry.core.repository.bo.EndpointCache: Could not remove disk store entry for org.ow2.petals.registry.core.repository.bo.Endpoint#8a2a4bde2863bcdd012863be9d1c0002. Error was org.ow2.petals.registry.core.repository.bo.Endpoint Cache: The Disk store is not active.
 at org.ow2.petals.registry.core.repository.jdbc.JDBCRepository.doDelete(JDBCRepository.java:86)
 at org.ow2.petals.registry.core.repository.AbstractRepository.delete(AbstractRepository.java:159)
 at org.ow2.petals.registry.core.AbstractLocalRegistry.doDelete(AbstractLocalRegistry.java:453)
 at org.ow2.petals.registry.core.AbstractRegistry.delete(AbstractRegistry.java:60)
 at org.ow2.petals.registry.client.RegistryClientImpl.delete(RegistryClientImpl.java:57)
 at org.ow2.petals.jbi.messaging.registry.BaseEndpointRegistry.deactivateEndpoint
    Show
    When stopping Petals, the following message is displayed : 
    SEVERE 2010-05-04 16:37:42,539 Failed to stop the component 'petals-bc-soap'
javax.jbi.messaging.MessagingException: org.ow2.petals.jbi.messaging.registry.RegistryException: Can not delete endpoint under > /endpoints/0/{http://orange.com/ros/services/movecustomer/v1}MoveCustomerService@MoveCustomerEndpoint2
  at org.ow2.petals.jbi.messaging.exchange.DeliveryChannelImpl.close(DeliveryChannelImpl.java:170)
  at org.ow2.petals.container.lifecycle.ComponentLifeCycle.doShutdown(ComponentLifeCycle.java:187)
  at org.ow2.petals.container.lifecycle.ComponentLifeCycle.stopComponentLifeCycle(ComponentLifeCycle.java:327)
  at org.ow2.petals.container.lifecycle.ComponentLifeCycle.stopFc(ComponentLifeCycle.java)
  at org.objectweb.fractal.julia.generated.Cbd2013d7_0.setFcContentState(BasicControllerMixin.java:8130)
  at org.objectweb.fractal.julia.generated.Cbd2013d7_0.setFcStopped(BasicControllerMixin.java:8087)
  at org.objectweb.fractal.julia.generated.C18c4c884_0.setFcStopped(INTERFACE[LifeCycleCoordinator])
  at org.objectweb.fractal.julia.generated.Cbd2013d7_0.stopFc(BasicControllerMixin.java:3187)
  at org.objectweb.fractal.julia.generated.Cbd2013d7_0.stopFc(BasicControllerMixin.java:4131)
  at org.objectweb.fractal.julia.generated.C18c4c884_0.stopFc(INTERFACE[LifeCycleCoordinator])
  at org.ow2.petals.kernel.server.FractalHelper.stopComponent(FractalHelper.java:379)
  at org.ow2.petals.kernel.server.PetalsServerImpl.stopPetalsComposite(PetalsServerImpl.java:508)
  at org.ow2.petals.kernel.server.PetalsServerImpl.stop(PetalsServerImpl.java:220)
  at org.ow2.petals.kernel.server.PetalsStopThread.run(PetalsStopThread.java:49)
Caused by: org.ow2.petals.jbi.messaging.registry.RegistryException: Can not delete endpoint under /endpoints/0/{http://orange.com/ros/services/movecustomer/v1}MoveCustomerService@MoveCustomerEndpoint2
  at org.ow2.petals.jbi.messaging.registry.BaseEndpointRegistry.deactivateEndpoint(BaseEndpointRegistry.java:179)
  at org.objectweb.fractal.julia.generated.C2304ecde_0.deactivateEndpoint(INTERCEPTOR[EndpointRegistry])
  at org.objectweb.fractal.julia.generated.C2eb804c9_0.deactivateEndpoint(INTERFACE[EndpointRegistry])
  at org.ow2.petals.jbi.component.context.ComponentContextImpl.deregisterAllEndpoints(ComponentContextImpl.java:236)
  at org.ow2.petals.jbi.messaging.exchange.DeliveryChannelImpl.close(DeliveryChannelImpl.java:168)
  ... 13 more
Caused by: org.ow2.petals.registry.api.exception.RegistryException: net.sf.ehcache.CacheException: org.ow2.petals.registry.core.repository.bo.EndpointCache: Could not remove disk store entry for org.ow2.petals.registry.core.repository.bo.Endpoint#8a2a4bde2863bcdd012863be9d1c0002. Error was org.ow2.petals.registry.core.repository.bo.Endpoint Cache: The Disk store is not active.
 at org.ow2.petals.registry.core.repository.jdbc.JDBCRepository.doDelete(JDBCRepository.java:86)
 at org.ow2.petals.registry.core.repository.AbstractRepository.delete(AbstractRepository.java:159)
 at org.ow2.petals.registry.core.AbstractLocalRegistry.doDelete(AbstractLocalRegistry.java:453)
 at org.ow2.petals.registry.core.AbstractRegistry.delete(AbstractRegistry.java:60)
 at org.ow2.petals.registry.client.RegistryClientImpl.delete(RegistryClientImpl.java:57)
 at org.ow2.petals.jbi.messaging.registry.BaseEndpointRegistry.deactivateEndpoint
  • Environment:
    OS:all

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Wed, 4 May 2011 - 11:14:05 +0200 - edited

The few provided elements indicate:

  • The problem is due to an EhCache error linked to the disk store,
  • The problem occurs when the cache of the registry is enabled,
  • Into Petals ESB, the disk store is used by default when the memory store is full (see the EhCache configuration provided through ehcache-failsafe.xml of the EhCache JAR)

Searching with Google possible error causes about the disk store, we can found that it is recommended to set the directory of the disk storage to prevent collision between two applications using EhCache.
Moreover, I'm not sure that the disk store is needed. A memory store should be sufficient all the more it is set to 10000 entities (endpoints) in the EhCache consiguration.

Reading source code where the problem occurs in the registry core, we can see that few HQL request don't use named parameters, and so an optimization can be done: PETALSESBCONT-141

Show
Christophe DENEUX added a comment - Wed, 4 May 2011 - 11:14:05 +0200 - edited The few provided elements indicate:
  • The problem is due to an EhCache error linked to the disk store,
  • The problem occurs when the cache of the registry is enabled,
  • Into Petals ESB, the disk store is used by default when the memory store is full (see the EhCache configuration provided through ehcache-failsafe.xml of the EhCache JAR)
Searching with Google possible error causes about the disk store, we can found that it is recommended to set the directory of the disk storage to prevent collision between two applications using EhCache. Moreover, I'm not sure that the disk store is needed. A memory store should be sufficient all the more it is set to 10000 entities (endpoints) in the EhCache consiguration. Reading source code where the problem occurs in the registry core, we can see that few HQL request don't use named parameters, and so an optimization can be done: PETALSESBCONT-141
Hide
Permalink
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 12:06:30 +0200 - edited

Resolved with the new distributed registry, based on Hazelcast, introduced with Petals ESB 5.0.0.

Show
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 12:06:30 +0200 - edited Resolved with the new distributed registry, based on Hazelcast, introduced with Petals ESB 5.0.0.

People

Dates

  • Created:
    Thu, 22 Jul 2010 - 13:53:11 +0200
    Updated:
    Mon, 5 Oct 2015 - 12:07:31 +0200
    Resolved:
    Mon, 5 Oct 2015 - 12:07:31 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.