[
https://jira.jboss.org/jira/browse/JBESB-1507?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1507:
-------------------------------------
There have been three changes involved with this
- Fix the code retrieving the organisation information as it was not safe and, in fact,
retrieved the organisation information every time it was called.
- Add another aspect into the AOP configuration, to prevent the JBDCDataStore
fetchBusiness method from retrieving all the services.
- Changed findAllServices to query the registry now that the organisation no longer
contains the service information.
Odd jUDDI behaviour when under the load for longer time
-------------------------------------------------------
Key: JBESB-1507
URL:
https://jira.jboss.org/jira/browse/JBESB-1507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2.1
Environment: FC7/PostgreSQL/embedded CR1
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Priority: Critical
Fix For: 4.2.1 CP5
Attachments: server.log, server2.log.gz, standalone.zip
I have run something like performance/stress test simulating access to jUDDI by many
clients. After few runs the jUDDI started to generate exceptions.
See attached log
--
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