WSO2 ESB
  1. WSO2 ESB
  2. ESBJAVA-526

No error thrown when executing a configuration which accesses an integrated registry entry which has been removed from the registry

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Lowest Lowest
    • Resolution: Fixed
    • Affects Version/s: NIGHTLY
    • Fix Version/s: 2.1.2
    • Component/s: None
    • Labels:
      None
    • Environment:
      Ubuntu7.10, JDK1.5.0_14, Firefox2.0.0.12
    • Estimated Complexity:
      Moderate

      Description

      Steps to reproduce

      1. Created a sequence which access an entry which is created in the Integrated Registry.
      2. When the client is invoked the sequence calls the registry entry and the response is received.
      3. Then delete the registry entry and invoke the client once more and it would show that it still picks up the registry entry which was removed and does not display any error messages.

      I assume a proper error message should be thrown to let the user know that the particular registry entry has been removed etc.

        Activity

        Hide
        Hiranya Jayathilaka
        added a comment -
        The following warning is logged when the ESB attempts to load a resource which does not exist anymore:

        [2010-02-05 14:35:34,495] WARN - SynapseConfiguration Error while loading the resource /meta/endpoints/foo from the remote registry. Previously cached value will be used. Check the registry accessibility.
        Show
        Hiranya Jayathilaka
        added a comment - The following warning is logged when the ESB attempts to load a resource which does not exist anymore: [2010-02-05 14:35:34,495] WARN - SynapseConfiguration Error while loading the resource /meta/endpoints/foo from the remote registry. Previously cached value will be used. Check the registry accessibility.

          People

          • Assignee:
            Hiranya Jayathilaka
            Reporter:
            Evanthika Amarasiri
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: