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

Thu Jul 31 07:48:27 EDT 2008

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

Kevin Conner commented on JBESB-1675:
-------------------------------------

The object references for a single binding look like the following, ServiceBinding -> Service -> Organisation, but as you traverse up the hierarchy you discover new versions of previous objects.

The service contains a fresh copy of each binding and the Organisation contains a fresh copy of each service.

Therefore
 - the original binding will exist in three places (binding, associated service, service in organisation).
 - the associated service (and each additional binding for that service) will exist twice.
 - every other service (and associated bindings) will exist once.

> 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