[esb-issues] [JBoss JIRA] Updated: (JBESB-3224) Add somekind of caching mechanism to ActionProcessingPipeline for jBPM to improve performance.

Tue Jun 15 05:16:46 EDT 2010

     [ https://jira.jboss.org/browse/JBESB-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Conner updated JBESB-3224:
--------------------------------

    Priority: Minor  (was: Critical)

Dropping priority given workaround.

> 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
>            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