You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2016/04/30 23:42:14 UTC
[Bug 59400] New: ClientJMeterEngine remote exit reports IOException
https://bz.apache.org/bugzilla/show_bug.cgi?id=59400
Bug ID: 59400
Summary: ClientJMeterEngine remote exit reports IOException
Product: JMeter
Version: Nightly (Please specify date)
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: sebb@apache.org
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.
--
You are receiving this mail because:
You are the assignee for the bug.
Re: [Bug 59400] ClientJMeterEngine remote exit reports IOException
Posted by Philippe Mouawad <ph...@gmail.com>.
Hi,
Same line as Felix.
Regards
On Sunday, May 1, 2016, Felix Schumacher <fe...@internetallee.de>
wrote:
>
>
> Am 1. Mai 2016 00:00:04 MESZ, schrieb sebb <sebbaz@gmail.com
> <javascript:;>>:
> >I think this is safe to commit, but am a bit wary of doing so just
> >before the release.
> >
> >It works for me.
> >
> >It's not a big deal if it is deferred (just a WARN message in the log).
>
> As it is only a warning, I think we should wait. I haven't looked at the
> patch, though.
>
> Regards,
> Felix
>
> >
> >On 30 April 2016 at 22:55, <bugzilla@apache.org <javascript:;>> wrote:
> >> https://bz.apache.org/bugzilla/show_bug.cgi?id=59400
> >>
> >> --- Comment #1 from Sebb <sebb@apache.org <javascript:;>> ---
> >> Created attachment 33816
> >> -->
> >https://bz.apache.org/bugzilla/attachment.cgi?id=33816&action=edit
> >> Stop backing engine asynchronously
> >>
> >> --
> >> You are receiving this mail because:
> >> You are the assignee for the bug.
>
>
--
Cordialement.
Philippe Mouawad.
Re: [Bug 59400] ClientJMeterEngine remote exit reports IOException
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 1. Mai 2016 00:00:04 MESZ, schrieb sebb <se...@gmail.com>:
>I think this is safe to commit, but am a bit wary of doing so just
>before the release.
>
>It works for me.
>
>It's not a big deal if it is deferred (just a WARN message in the log).
As it is only a warning, I think we should wait. I haven't looked at the patch, though.
Regards,
Felix
>
>On 30 April 2016 at 22:55, <bu...@apache.org> wrote:
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=59400
>>
>> --- Comment #1 from Sebb <se...@apache.org> ---
>> Created attachment 33816
>> -->
>https://bz.apache.org/bugzilla/attachment.cgi?id=33816&action=edit
>> Stop backing engine asynchronously
>>
>> --
>> You are receiving this mail because:
>> You are the assignee for the bug.
Re: [Bug 59400] ClientJMeterEngine remote exit reports IOException
Posted by sebb <se...@gmail.com>.
I think this is safe to commit, but am a bit wary of doing so just
before the release.
It works for me.
It's not a big deal if it is deferred (just a WARN message in the log).
On 30 April 2016 at 22:55, <bu...@apache.org> wrote:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=59400
>
> --- Comment #1 from Sebb <se...@apache.org> ---
> Created attachment 33816
> --> https://bz.apache.org/bugzilla/attachment.cgi?id=33816&action=edit
> Stop backing engine asynchronously
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
[Bug 59400] ClientJMeterEngine remote exit reports IOException
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59400
--- Comment #1 from Sebb <se...@apache.org> ---
Created attachment 33816
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33816&action=edit
Stop backing engine asynchronously
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59400] ClientJMeterEngine remote exit reports IOException
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59400
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |p.mouawad@ubik-ingenierie.c
| |om
--- Comment #2 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
+1 for commiting the patch
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59400] ClientJMeterEngine remote exit reports IOException
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59400
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|Nightly (Please specify |3.0
|date) |
Hardware|PC |All
OS|Mac OS X 10.1 |All
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59400] ClientJMeterEngine remote exit reports IOException
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59400
Felix Schumacher <fe...@internetallee.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Felix Schumacher <fe...@internetallee.de> ---
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
--
You are receiving this mail because:
You are the assignee for the bug.