Summary: | java process spinning and using 100% of a cpu after test completes | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | RH <richard_hubbe11> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.3 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | other |
Description
RH
2007-10-18 11:00:30 UTC
Thans for the info so far, but there's not enough to draw any conclusions. Can you attach a copy of the JMX file? If it contains any private information, be sure to change that first. Does it happen with different tests, or only one? Does it happen every time? How many threads? Any message in jmeter.log when ii does happen? Are there any threads still running? - this can be seen from the closedown messages. There should be two messages for each, for example: jmeter.threads.JMeterThread: Thread Thread Group 1-1 is done jmeter.engine.StandardJMeterEngine: Ending thread Thread Group 1-1 This has not been reported by anyone else, and it does not seem to be reproducible. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2037 |