[
http://jira.jboss.com/jira/browse/JBESB-1507?page=comments#action_12413586 ]
Len DiMaggio commented on JBESB-1507:
-------------------------------------
the params that conforms to the test descriptions
http://intranet.corp.redhat.com/ic/intranet/SOAPerformanceTests.html#juddi are
test.performance.juddi.count.find=100
test.performance.juddi.count.service=500
test.performance.juddi.count.epr=1 and 5
test.performance.juddi.count.maxservice=10000
test.performance.juddi.count.maxepr=50
Odd jUDDI behaviour when under the load for longer time
-------------------------------------------------------
Key: JBESB-1507
URL:
http://jira.jboss.com/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
Assigned To: Tom Cunningham
Priority: Critical
Fix For: 4.2.1 CP3
Attachments: server.log
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira