[
http://jira.jboss.com/jira/browse/JBESB-1675?page=all ]
Bodo Junglas updated JBESB-1675:
--------------------------------
Attachment: esb-util-cache.sar
esb-util-cache-src.jar
In our current project we can't wait for the next release, so I created a little
patch/workaround for the SOA-Platform 4.2 (should work for community edition too):
It's quite simple:
1. Added a clustered TreeCache
2. Wrote my own implementation of org.jboss.soa.esb.services.registry.Registry that's
using the above TreeCache and delegates to the real Registry-Implementation (usually
JAXR/JUDDI)
3. Wrote a smal service that puts the above implementation into the RegistryFactory
On my test system (with Oracle database) I get a multiplier of 10 ;)
Possible Juddi Performance problems
-----------------------------------
Key: JBESB-1675
URL:
http://jira.jboss.com/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
Assigned To: Tom Cunningham
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira