[JBoss JIRA] Created: (JBESB-2604) Document registry interceptors
by Aaron Pestel (JIRA)
Document registry interceptors
------------------------------
Key: JBESB-2604
URL: https://jira.jboss.org/jira/browse/JBESB-2604
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation
Environment: SOA-P 4.3 SP1
Reporter: Aaron Pestel
Priority: Minor
This is a request to document the two known registry interceptors: org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor and org.jboss.internal.soa.esb.services.registry.CachingRegistryInterceptor
The InVMRegistryInterceptor is listed in the services guide, section 2.1 and 3.2: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP01/html-single/...
In section 2.1, it shows an extract of the registry portion of the jbossesb-properties.xml - which includes InVMRegistryInterceptor, and then goes on to describe each property, but neglects to describe the org.jboss.soa.esb.registry.interceptors property where InVMRegistryInterceptor is set.
I am requesting a description in section 2.1 of the org.jboss.soa.esb.registry.interceptors property to include:
1.) format for adding 1 or many interceptors (using ", ")
2.) description of two currently available interceptors (InVMRegistryInterceptor and CachingRegistryInterceptor)
3.) description of when it would make sense or not make sense to use these two interceptors
Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Created: (JBESB-3373) Handle websphere broken connections
by Kevin Conner (JIRA)
Handle websphere broken connections
-----------------------------------
Key: JBESB-3373
URL: https://jira.jboss.org/browse/JBESB-3373
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.4 CP4
Reporter: Kevin Conner
Fix For: 4.4 CP5
We currently handle the detection of connection failures for JBoss Messaging by examining the exceptions thrown by the JMS operations, we need to extend this to include Websphere MQ
The only known error, at this stage, is a JMSException with error code "MQJE001: Completion Code 2, Reason 2009" and a linked exception with message "MQJMS2008".
This should be configurable so that we have an opportunity to augment this if necessary.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months