[esb-issues] [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time

[Len DiMaggio (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]

Len DiMaggio updated JBESB-1507:
--------------------------------

    Attachment: standalone.zip

This is about as standalone as I can make it.

To run the test - unzip the attached file to yield:

|-- auth.conf
|-- build.properties
|-- build.xml
|-- jbossesb-properties.xml
|-- jndi.properties
|-- juddi_test.jar
|-- log4j.xml
|-- org
|   `-- jboss
|       `-- soa
|           `-- esb
|               `-- qa
|                   `-- tests
|                       `-- performance
|                           `-- juddi
|                               |-- JUDDITest$1.class
|                               |-- JUDDITest$Finder.class
|                               |-- JUDDITest$OpType.class
|                               |-- JUDDITest.class
|                               |-- PerformanceJUDDITest1.class
|                               |-- PerformanceJUDDITest2.class
|                               |-- PerformanceJUDDITest3.class
|                               |-- PerformanceJUDDITest4.class
|                               `-- PerformanceJUDDITest5.class
|-- test-result-service.sar
`-- testng-5.6-jdk15.jar

Edit build.properties to point to the local postgres DB and SOA-P server and then: 'ant'



> 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, 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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira