12:34 a.m.
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
Reporter: Jiri Pechanec
Priority: Critical
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
12:34 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Jiri Pechanec updated JBESB-1507:
---------------------------------
Attachment: server.log
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
Reporter: Jiri Pechanec
Priority: Critical
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
12:34 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Jiri Pechanec updated JBESB-1507:
---------------------------------
Environment: FC7/PostgreSQL/embedded CR1
Assignee: Mark Little
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: Mark Little
Priority: Critical
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
12:38 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Jiri Pechanec updated JBESB-1507:
---------------------------------
Fix Version/s: 4.2.1 CP1
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: Mark Little
Priority: Critical
Fix For: 4.2.1 CP1
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
3:45 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Kevin Conner reassigned JBESB-1507:
-----------------------------------
Assignee: Kurt Stam (was: Mark Little)
Kurt, can you take a look at this one please.
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: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
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
8:41 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=comments#action_12396360 ]
Kurt Stam commented on JBESB-1507:
----------------------------------
Jiri, is this an issue specific to Postgres or does or does it happen with other dbs too?
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: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
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
8:54 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=comments#action_12396366 ]
Jiri Pechanec commented on JBESB-1507:
--------------------------------------
Oracle perf db is blocked by ESB testing, so I am doing some preliminary tests to get a
least some results now.
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: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
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
8:46 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=comments#action_12397351 ]
Mark Little commented on JBESB-1507:
------------------------------------
Kurt, if this is not a quick fix then let me know and we will push this until after GA.
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: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
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
9:10 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Work on JBESB-1507 started by Kurt Stam.
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: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
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
3:12 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=comments#action_12397545 ]
Kurt Stam commented on JBESB-1507:
----------------------------------
I cannot reproduce this on XP running postgres 8.2. Can you please provide a standalone
test that produces the same issue?
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: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
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
3:27 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Mark Little updated JBESB-1507:
-------------------------------
Fix Version/s: 4.3
(was: 4.2.1 CP1)
Moving to 4.3 release for now.
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: Kurt Stam
Priority: Critical
Fix For: 4.3
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
8:19 a.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Work on JBESB-1507 stopped by Kurt Stam.
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: Kurt Stam
Priority: Critical
Fix For: 4.3
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
8:02 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Kevin Conner updated JBESB-1507:
--------------------------------
Fix Version/s: 4.2.1 CP2
(was: 4.3)
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: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP2
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
8:39 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Kevin Conner updated JBESB-1507:
--------------------------------
Fix Version/s: 4.2.1 CP3
(was: 4.2.1 CP2)
Assignee: Tom Cunningham (was: Kurt Stam)
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
4:25 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=comments#action_12413281 ]
Len DiMaggio commented on JBESB-1507:
-------------------------------------
We're workingon a standalone test case for this...
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
11:32 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=comments#action_12413573 ]
Len DiMaggio commented on JBESB-1507:
-------------------------------------
It looks like the smallest footprint for running the test is:
java -Djava.security.auth.login.config=file:./auth.conf
-Dorg.jboss.esb.server.config=postgresql -Djbosstest.loginconfig=jmx-console
-Djbosstest.secure=true -Djbosstest.username=admin -Djbosstest.password=admin
-Dtest.performance.juddi.count.find=2 -Dtest.performance.juddi.count.service=2
-Dtest.performance.juddi.count.epr=2 -Dtest.performance.juddi.count.maxservice=8
-Dtest.performance.juddi.count.maxepr=8 \
-classpath /home/ldimaggi/Desktop/juddi_test.jar:\
/home/ldimaggi/Desktop/testng-5.6-jdk15.jar:\
/home/ldimaggi/Desktop/jboss-jars/test-result-service.sar:\
.:\
./jndi.properties:\
./auth.conf:\
./runtime/jars/commons-logging.jar:\
./runtime/jars/concurrent.jar:\
./runtime/jars/jboss-common.jar:\
./runtime/jars/jboss-j2ee.jar:\
./runtime/jars/jboss-remoting.jar:\
./runtime/jars/jboss-serialization.jar:\
./runtime/jars/jboss-test.jar:\
./runtime/jars/jboss-transaction.jar:\
./runtime/jars/jboss.jar:\
./runtime/jars/jbossesb-rosetta.jar:\
./runtime/jars/jbosssx.jar:\
./runtime/jars/jbossts-common.jar:\
./runtime/jars/jbossws-framework.jar:\
./runtime/jars/jbossws-spi.jar:\
./runtime/jars/jmx-adaptor-plugin.jar:\
./runtime/jars/jnpserver.jar:\
./runtime/jars/juddi-client-2.0rc5.jar:\
./runtime/jars/log4j.jar:\
./runtime/jars/scout-1.0rc1.jar:\
./runtime/jars/stax-api.jar:\
./runtime/jars/wstx-lgpl-3.2.1.jar:\
./runtime/jars/xbean.jar:\
./runtime/jars/xbean.jar:\
./runtime/jars/xercesImpl.jar:\
./runtime/jars/xmlpublic.jar:\
./runtime/jars/xpp3_min-1.1.3.4.O.jar org.testng.TestNG -testclass
org.jboss.soa.esb.qa.tests.performance.juddi.PerformanceJUDDITest5
(I'll write up a build.xml file or testNG script - and zip up all the jars needed. -
Not in my home dir.)
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
12:14 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ 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
10:28 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ 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
10:47 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Len DiMaggio updated JBESB-1507:
--------------------------------
Attachment: (was: standalone.zip)
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
10:47 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Len DiMaggio updated JBESB-1507:
--------------------------------
Attachment: standalone.zip
This is a corrected file.
The SOA-P server will need these files:
jboss-test.jar copied to server/name/lib
test-result-service.sar copied to server/name/deploy
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
12:49 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=comments#action_12414389 ]
Tom Cunningham commented on JBESB-1507:
---------------------------------------
I'm having a problem reproducing this. I'm seeing a "Too Many
Clients" error on Postgres and Oracle - how many min/max connections are being used
here with the schema script? What's suggested?
Tried this on MySQL, and saw no errors.
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
3:19 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=comments#action_12415118 ]
Jiri Pechanec commented on JBESB-1507:
--------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>juddiDB</jndi-name>
<connection-url>jdbc:postgresql://localhost:5432/soaesb1</connection-url>
<driver-class>org.postgresql.Driver</driver-class>
<user-name>soaesb1</user-name>
<password>soaesb1</password>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
<min-pool-size>10</min-pool-size>
<max-pool-size>20</max-pool-size>
<metadata>
<type-mapping>PostgreSQL 8.0</type-mapping>
</metadata>
</local-tx-datasource>
</datasources>
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
4:48 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Jiri Pechanec updated JBESB-1507:
---------------------------------
Attachment: server2.log.gz
I tried again to reproduce the issue, see attached log
The result is
2008-06-02 11:42:57,892 ERROR [org.apache.juddi.function.GetBusinessDetailFunction]
java.lang.NullPointerException
2008-06-02 11:42:57,892 ERROR [org.apache.juddi.registry.local.RequestHandler]
java.lang.NullPointerException
2008-06-02 11:42:57,892 ERROR [STDERR] java.lang.reflect.InvocationTargetException
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.apache.ws.scout.transport.LocalTransport.send(LocalTransport.java:67)
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:271)
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.apache.ws.scout.registry.RegistryImpl.getBusinessDetail(RegistryImpl.java:885)
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.apache.ws.scout.registry.RegistryImpl.getBusinessDetail(RegistryImpl.java:865)
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.getRegistryObject(BusinessQueryManagerImpl.java:721)
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.getServiceFromBusinessService(BusinessQueryManagerImpl.java:789)
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.getRegistryObject(BusinessQueryManagerImpl.java:753)
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.findServiceBindings(BusinessQueryManagerImpl.java:595)
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findServiceBindings(JAXRRegistryImpl.java:659)
2008-06-02 11:42:57,892 ERROR [STDERR] at
org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:271)
2008-06-02 11:42:57,892 ERROR [STDERR] at
sun.reflect.GeneratedMethodAccessor152.invoke(Unknown Source)
2008-06-02 11:42:57,892 ERROR [STDERR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2008-06-02 11:42:57,892 ERROR [STDERR] at
java.lang.reflect.Method.invoke(Method.java:585)
2008-06-02 11:42:57,893 ERROR [STDERR] at
org.jboss.internal.soa.esb.services.registry.RegistryService$1.invoke(RegistryService.java:61)
2008-06-02 11:42:57,893 ERROR [STDERR] at $Proxy36.findEPRs(Unknown Source)
2008-06-02 11:42:57,893 ERROR [STDERR] at
org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:226)
2008-06-02 11:42:57,893 ERROR [STDERR] at
org.jboss.soa.esb.monitoring.server.DataFilerJob.execute(DataFilerJob.java:70)
2008-06-02 11:42:57,893 ERROR [STDERR] at
org.quartz.core.JobRunShell.run(JobRunShell.java:203)
2008-06-02 11:42:57,893 ERROR [STDERR] at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
2008-06-02 11:42:57,893 ERROR [STDERR] Caused by:
java.lang.reflect.InvocationTargetException
2008-06-02 11:42:57,893 ERROR [STDERR] at
sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
2008-06-02 11:42:57,893 ERROR [STDERR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2008-06-02 11:42:57,893 ERROR [STDERR] at
java.lang.reflect.Method.invoke(Method.java:585)
2008-06-02 11:42:57,893 ERROR [STDERR] at
org.apache.ws.scout.transport.LocalTransport.send(LocalTransport.java:63)
2008-06-02 11:42:57,893 ERROR [STDERR] ... 18 more
2008-06-02 11:42:57,893 ERROR [STDERR] Caused by: java.lang.Exception: faultCode=null,
faultString=null, faultActor=null, errno=null, errCode=null, errText=null
2008-06-02 11:42:57,893 ERROR [STDERR] at
org.apache.juddi.registry.local.InquiryService.inquire(InquiryService.java:91)
2008-06-02 11:42:57,893 ERROR [STDERR] ... 22 more
I have used PerformanceJUDDITest5 with the values mentioned in previous comments
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, 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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[ http://jira.jboss.com/jira/browse/JBESB-1507?page=all ]
Kevin Conner updated JBESB-1507:
--------------------------------
Fix Version/s: 4.2.1 CP4
(was: 4.2.1 CP3)
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 CP4
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[
https://jira.jboss.org/jira/browse/JBESB-1507?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-1507:
--------------------------------
Fix Version/s: 4.2.1 CP5
(was: 4.2.1 CP4)
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: Tom Cunningham
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
11:06 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[
https://jira.jboss.org/jira/browse/JBESB-1507?page=com.atlassian.jira.plu...
]
Kevin Conner reassigned JBESB-1507:
-----------------------------------
Assignee: Kevin Conner (was: Tom Cunningham)
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
9:57 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[
https://jira.jboss.org/jira/browse/JBESB-1507?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1507:
-------------------------------------
I spent a lot of time over the weekend trying to reproduce this issue but have been
unable.
Examining the jUDDI code shows that there may be an issue with the JDBCDataStore in that
it is possible for the connection to remain null, leading to a similar issue in the log.
I am not convinced that this is the root cause as the issue is generic and I would expect
it to impact on more areas. One possible explanation could be that the error is transient
and that the attempt to handle the processing takes so long that the error becomes likely,
for example one of the responses in my testing exceeded 500K in size!
I will try to investigate this further during the week and see if anything else can be
discovered, although the impact of this has been reduced dramatically as a consequence of
the performance changes in JBESB-2155 as the business detail should no longer be requested
during normal EPR operations.
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
7:42 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[
https://jira.jboss.org/jira/browse/JBESB-1507?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1507:
-------------------------------------
The cause of the NPE is a race within the jUDDI codebase, specifically when reading in the
business details.
The function reads in a list of services associated with the business and then tries to
fill in the details. During this time it is possible for one of the services to be
deleted and, as a consequence, the code reading in the details can fail.
The specific location of this failure is the call to setNameVector as the value of service
is null.
public BusinessService fetchService(String serviceKey)
throws org.apache.juddi.error.RegistryException
{
BusinessService service = null;
try
{
if ((serviceKey != null) && (connection != null))
{
service = BusinessServiceTable.select(serviceKey,connection);
service.setNameVector(ServiceNameTable.select(serviceKey,connection));
service.setDescriptionVector(ServiceDescTable.select(serviceKey,connection));
Vector catVector = ServiceCategoryTable.select(serviceKey,connection);
if (catVector.size() > 0)
{
CategoryBag bag = new CategoryBag();
bag.setKeyedReferenceVector(catVector);
service.setCategoryBag(bag);
}
// 'fetch' the BusinessService's BindingTemplate objects
Vector bindingVector = fetchBindingByServiceKey(serviceKey);
BindingTemplates bindings = new BindingTemplates();
bindings.setBindingTemplateVector(bindingVector);
service.setBindingTemplates(bindings);
}
}
catch(java.sql.SQLException sqlex)
{
throw new RegistryException(sqlex);
}
return service;
}
I believe that the AOP modifications disable calls to this code, at least in the majority
of cases, but I need to see if there are any other paths which exist in the current
codebase.
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
8:46 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[
https://jira.jboss.org/jira/browse/JBESB-1507?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1507:
-------------------------------------
It looks like this code will still be accessed by the EPR registration process and the
invocation which retrieves the ESB organisation details.
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
1:14 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[
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
1:22 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time
[
https://jira.jboss.org/jira/browse/JBESB-1507?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-1507.
-------------------------------
Resolution: Done
Updated in revision 26212.
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
5712
days inactive
6167
days old
30 comments
6 participants
participants (6)
-
Jiri Pechanec (JIRA) -
Kevin Conner (JIRA)
-
Kurt Stam (JIRA)
-
Len DiMaggio (JIRA)
-
Mark Little (JIRA)
-
Tom Cunningham (JIRA)