Bug 59400 - ClientJMeterEngine remote exit reports IOException
Summary: ClientJMeterEngine remote exit reports IOException
Status: RESOLVED FIXED
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 3.0
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-30 21:42 UTC by Sebb
Modified: 2016-06-12 13:19 UTC (History)
1 user (show)


Attachments
Stop backing engine asynchronously (1.03 KB, text/plain)
2016-04-30 21:55 UTC, Sebb 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sebb 2016-04-30 21:42:14 UTC 
The -X command option results in the following warning in the log:

2016/04/30 22:16:18 WARN  - jmeter.engine.ClientJMeterEngine: Could not perform remote exit: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.io.EOFException

This is because RemoteJMeterEngineImpl.rexit() processes the exit request synchronously. The rexit() RMI call never returns because the server exits first.

The rexit() method should return having scheduled the exit code in a separate thread.
Comment 1 Sebb 2016-04-30 21:55:03 UTC 
Created attachment 33816 [details]
Stop backing engine asynchronously
Comment 2 Philippe Mouawad 2016-06-11 08:27:07 UTC 
+1 for commiting the patch
Comment 3 Felix Schumacher 2016-06-12 13:19:12 UTC 
Date: Sun Jun 12 13:18:41 2016
New Revision: 1747998

URL: http://svn.apache.org/viewvc?rev=1747998&view=rev
Log:
Get rid of UnmarshalException on stopping when -X option is used.

Bugzilla Id: 59400

Modified:
    jmeter/trunk/src/core/org/apache/jmeter/engine/RemoteJMeterEngineImpl.java
    jmeter/trunk/xdocs/changes.xml