Thanks Jeremi, this looks like a huge leak, so it should be easy to
find. I opened a bug for this
https://issues.apache.org/jira/browse/JUDDI-267
Hopefully we will have a fix soon, and I will release a snapshot. I saw
all the attachements, what do you think is the easiest way to reproduce it?
Thx!
--Kurt
Jeremi Thebeau wrote:
Hi all,
I ran a load test comprising of 30 virtual user continuously executing
a the following senario on a jUDDI node:
- publish a business to the node with a unique name;
- publish a random number of services (>0 but <8) under that business;
- and search for the newly published business name.
This was supposed to run for two hours but the application crashed
after 1h 46m. As can be seen in the attached jconsole screenshot, the
heap memory usage goes up almost linearly during the load test until
it hit the maximum alloted memory, 1G (inserted 'export
JAVA_OPTS=-Xmx1024m' in startup.sh). Then, it hung around one gig as
the request's response times got longer and longer as can be seen in
the attached XLT report at about 11:25 (go to 'Requests' via the
navigation drop down in the top right corner, most easily seen on the
'Averages' graphs). Eventually, I started getting
'java.lang.Exception: GC overhead limit exceeded' and
'java.lang.Exception: Java heap space' exceptions (stacktraces can be
seen under 'Errors' in the XLT report) and the application crashed.
Also attached is the testcase used
(TRegisterBusinessWithServices.java) and the actions called under it.
Jeremi Thebeau
QA Engineer/Consultant
Xceptance GmbH
------------------------------------------------------------------------
