Bug 1031720 - The LocalRegistryInterceptor
The LocalRegistryInterceptor
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: doc-Installation_and_Configuration_Guide (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Anshu
Depends On:
  Show dependency treegraph
Reported: 2013-11-18 10:37 EST by Rick Wagner
Modified: 2014-01-06 05:56 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Instance Name: Not Defined Build: CSProcessor Builder Version 1.7 Build Name: 6483, Installation and Configuration Guide-5-5.3.1 Build Date: 05-02-2013 11:48:50
Last Closed: 2014-01-06 05:56:31 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rick Wagner 2013-11-18 10:37:17 EST
Description of problem:

The description of the interceptors stack is inadequate.  Please enhance it by doing the following:

- use the description (and illustration) at [1] as an example.  Maybe even copy it outright.

- give the full classname for the LocalRegistryInterceptor, the user will need it to configure it.  (org.jboss.internal.soa.esb.services.registry.LocalRegistryInterceptor)

- explain the downside to using the LocalRegistryInterceptor:  It will result in the local node always using it's own version of a Service if it has one.  (If it does not, it will look further for it). This will cause load balancing to stop for that Service-- the single node will try to do all the work itself.

It has the upside of a more direct path to execution for services (does not go to the registry and then on to another machine) and reduces calls to the registry.

Please follow up with ESB Engineering for validation/more details.  Kevin Conner would be the definitive source.

[1] http://docs.jboss.org/jbossesb/docs/4.9/manuals/html/Services_Guide/index.html

Note You need to log in before you can comment on or make changes to this bug.