[
https://issues.apache.org/jira/browse/JUDDI-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800274#action_12800274
]
Kurt T Stam commented on JUDDI-267:
-----------------------------------
After trying to change code and config, I'm still seeing the leak, and I
started a thread on the openjpa forum:
http://mail-archives.apache.org/mod_mbox/openjpa-users/201001.mbox/browser :
"memory leak - simple question?"
The problem is now simplified to a servlet which persists an authToken and we
still see the leak. So hopefully with this simply setup we can find out what is
going on. I'm getting help from the openjpa developers.
> Memory leak during load testing
> -------------------------------
>
> Key: JUDDI-267
> URL: https://issues.apache.org/jira/browse/JUDDI-267
> Project: jUDDI
> Issue Type: Bug
> Affects Versions: 3.0beta
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.0.1
>
>
> http://mail-archives.apache.org/mod_mbox/ws-juddi-dev/200907.mbox/%[email protected]%3e
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
