[esb-issues] [JBoss JIRA] Closed: (JBESB-3224) Add somekind of caching mechanism to ActionProcessingPipeline for jBPM to improve performance.
[
https://jira.jboss.org/browse/JBESB-3224?page=com.atlassian.jira.plugin.s...
]
Kevin Conner closed JBESB-3224.
-------------------------------
Resolution: Done
The caching registry interceptor is now enabled by default, using the same value as the
service invoker cache life unless overridden.
Updated in revision 34131.
Add somekind of caching mechanism to ActionProcessingPipeline for
jBPM to improve performance.
----------------------------------------------------------------------------------------------
Key: JBESB-3224
URL: https://jira.jboss.org/browse/JBESB-3224
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Process flow, Rosetta
Affects Versions: 4.8
Reporter: Marek Baluch
Assignee: Kevin Conner
Priority: Minor
Fix For: 4.9
Each time an ESB service is invoked from a jBPM node a jUDDI lookup is made to find the
endpoint reference for JBpmCallback Service. This reference will be used as the target to
which the response will be sent.
The JBpmCallback Service is represented inside the message as LogicalEPR and for each
LogicalEPR a new ServiceInvoker is created. This is the place where jUDDI is accessed.
Each such jUDDI lookup takes about 200-300 ms.
--
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