Bug 777503 (SOA-12) - Document the ways to end up with bad EPRs and the strategies for cleansing your registry.
Summary: Document the ways to end up with bad EPRs and the strategies for cleansing yo...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-12
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.2 CR3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Mark Little
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA-12
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-10 01:41 UTC by Len DiMaggio
Modified: 2007-09-10 09:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-10 09:42:46 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-12 0 Major Closed Document the ways to end up with bad EPRs and the strategies for cleansing your registry. 2014-01-30 17:42:32 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.