[esb-issues] [JBoss JIRA] Commented: (JBESB-1675) Possible Juddi Performance problems

[Luc DEW (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12422822#action_12422822 ] 

Luc DEW commented on JBESB-1675:
--------------------------------

Thanks Bodo for the patch,

 i would like to apply it for my current project since i noticed that internal ESB communications (between a jms gateway and non-gateway listener) were slow partially due
to the services and category lookups in database (I also had 5000 selects created for just on message.).

 We configured Jboss ESB to persist the juddi tables in Oracle server.

I would like to be sure how i can apply your patch:
- deploy the sar file in the server's deploy directory
- make my ESB archive depends on the "jboss.esb:service=CachedESBRegistry" MBean

But am i supposed to reconfigure the jboss ESB sar's registry (jbossesb-properties.xml ) and especially
the org.jboss.soa.esb.registry.implementationClass attribute ? Or can i just make the jboss ESB 's sar depend
on your MBean and clients will use the RegistryFactory to retrieve the Registry ?

I also can't wait for the next release. 

Hope you will read me
Thanks
Luc

> Possible Juddi Performance problems
> -----------------------------------
>
>                 Key: JBESB-1675
>                 URL: https://jira.jboss.org/jira/browse/JBESB-1675
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Registry and Repository
>    Affects Versions: 4.2.1
>            Reporter: Tom Cunningham
>            Assignee: Kevin Conner
>             Fix For: 4.4
>
>         Attachments: esb-util-cache-src.jar, esb-util-cache.sar, server.rar
>
>
> From forum post :
> We are not using juddi directly, I do not know if it is a core required component of ESB. After a few runs, we are having performance problems that seems to be related to juddi. It happens only on shutdow/startup operations. The time spent to create the auth tokens (sorry, what are they used for anyway??) are taking longer and longer. JBoss takes over 2 minutes (in a 8 processor machine??) just to delete the template bindings for juddi on the shutdown process. 

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