Description of problem: In case the service is being deployed for the first time, this setting prevents it from being registered: try { if ("true".equalsIgnoreCase(removeOldService)) registry.unRegisterService(category, name); registry.registerEPR(category, name, serviceDescription, epr, eprDescription) ; } catch (ServiceNotFoundException ex) { // ignore as it's possible another client just did the removal for us. logger.debug("Could not unregister service < "+category+", "+name+" >."); } The registry.registerEPR call should happen after the ServiceNotFoundException is caught? How reproducible: always Steps to Reproduce: 1. Add remove-old-service attribute to EPR: <jms-listener name="JMS-ESBListener" busidref="quickstartEsbChannel"> <property name="remove-old-service" value="true"/> </jms-listener> 2. Start against a clean DB 3. Service registration fails Actual results: Service not registered Expected results: Service getting registered
Tom Cunningham <tcunning> updated the status of jira JBESB-3747 to Resolved
Tom Cunningham <tcunning> made a comment on jira JBESB-3747 Move the registerEpr so that it will happen whether or not a ServiceNotFoundException occurs.
Tom Cunningham <tcunning> updated the status of jira JBESB-3747 to Closed
Customer-facing, seems done. Please include this 'medium' issue if at all possible.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: A problem occurs when launching the JBoss ESB which prevents it from being registered. When adding the remove-old-service attribute to the EPR, the service registration fails and a ServiceNotFoundException error is thrown. The registerEpr should be moved to prevent this from occuring.
Verified in ER3
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -A problem occurs when launching the JBoss ESB which prevents it from being registered. When adding the remove-old-service attribute to the EPR, the service registration fails and a ServiceNotFoundException error is thrown. The registerEpr should be moved to prevent this from occuring.+A problem occurs when the user tries to deploy a service for the frist time. When adding the remove-old-service attribute to the EPR, the service registration fails and a ServiceNotFoundException error is thrown. The registerEpr should be moved to prevent this from occuring.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.