Petals ESB Container

EndpointServiceImpl.updateNewEnpoint can be invoked endlessly

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6.2
  • Fix Version/s: 1.6.3
  • Component/s: Registry
  • Security Level: Public
  • Description:
    Hide

    When a desynchronization occurs on the registry (Joram JNDI), wa can have a container A containing new-endpoints hold by a container B, and these new-endpoints does not exist into the container B. In this case, each call initiated on container A calls EndpointServiceImpl.updateNewEnpoint that decrease performances.
    It seems that such new-endpoints are correctly activated. So, in that case, if no new-endpoints is remotely processed, they should be removed from the context 'new-endpoints'.

    Show
    When a desynchronization occurs on the registry (Joram JNDI), wa can have a container A containing new-endpoints hold by a container B, and these new-endpoints does not exist into the container B. In this case, each call initiated on container A calls EndpointServiceImpl.updateNewEnpoint that decrease performances. It seems that such new-endpoints are correctly activated. So, in that case, if no new-endpoints is remotely processed, they should be removed from the context 'new-endpoints'.
  • Environment:
    -

People

Dates

  • Created:
    Mon, 15 Nov 2010 - 10:39:44 +0100
    Updated:
    Mon, 15 Nov 2010 - 11:49:56 +0100
    Resolved:
    Mon, 15 Nov 2010 - 11:49:56 +0100
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.