| Summary: | JMeter will use 100%CPU if message broker is stopped | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | Alessio Tomasino <alessio.tomasino> |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | alessio.tomasino |
| Priority: | P2 | ||
| Version: | 2.3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | Diff file (Receiver.java) | ||
Created attachment 21083 [details]
Diff file (Receiver.java)
It closes the JMS QueueReceiver:
// close consumer, session & connection
if (consumer != null) {
try {
consumer.close();
if (session != null)
session.close();
if (conn != null)
conn.close();
} catch (JMSException e) {
e.printStackTrace();
}
Thanks for the report and patch. Code has been updated in SVN: URL: http://svn.apache.org/viewvc?rev=674234&view=rev Log: Bug 43791 - ensure QueueReceiver is closed This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2043 |
To reproduce: 1. create a JMS Point-To-Point Sampler 2. run the test 3. stop the JMS broker (I'm using Weblogic Server 10) Symtoms: 1. Jmeter will use 100% CPU 2. Message to stdout (continuosly repeated): weblogic.jms.common.IllegalStateException: [JMSClientExceptions:055088]The consu mer is closed at weblogic.jms.client.JMSConsumer.checkClosed(JMSConsumer.java:674) at weblogic.jms.client.JMSConsumer.receive(JMSConsumer.java:510) at weblogic.jms.client.WLConsumerImpl.receive(WLConsumerImpl.java:167) at org.apache.jmeter.protocol.jms.sampler.Receiver.run(Receiver.java:74) at java.lang.Thread.run(Thread.java:595) Root cause: QueueReceiver is not closed (Receiver.java) Thanks, Alessio