Bug 777503 (SOA-12)

Summary: Document the ways to end up with bad EPRs and the strategies for cleansing your registry.
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Len DiMaggio <ldimaggi>
Component: DocumentationAssignee: Mark Little <mark.little>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 CR3   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-12
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-10 09:42:46 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Len DiMaggio 2007-09-10 01:41:34 UTC 
Date of First Response: 2007-09-10 05:42:46
project_key: SOA

This topic came up during the discussion of failover.

Item: Bad EPRs

The registry often gets cluttered with "stale" EPRs at this time, however, the routing/service invoker logic will attempt to redeliver a message after it determines an EPR is stale (hopefully there is a way to determine that it is no longer valid). Bad EPRs are often the result of deployment & undeployment & redeployment of a .esb where slight tweaks have been made to the listener in the jboss-esb.xml moving a service from JMS to FTP can result in a "stale" EPR lingering around on the JMS transport. Or failures, or services that have moved. 

To do - document the ways to end up with bad EPRs and the strategies for cleansing your registry.
Comment 1 Mark Little 2007-09-10 09:42:46 UTC 
Documentation was updated for ESB 4.2.