Re: Grinder agent communication shut down when worker process launched

--===============2569244363524698648==
Content-Type: multipart/alternative; boundary=001a1143b40c1deb8e0524fd67fd

--001a1143b40c1deb8e0524fd67fd
Content-Type: text/plain; charset=UTF-8

Thanks guys for all the guidance.   I found the root cause of our issue.
The worker process jvm was passing grinder.useConsole=False as an
argument.  This was causing the worker process to terminate the connection
to the console when it's jvm was started up.  I believe during
troubleshooting this flag was switched from true to false thinking it was
required to run headless.

Hope this helps anyone who might hit a similar issue in the future.
On Nov 20, 2015 12:07 PM, "Ouray Viney" <[email protected]> wrote:

> Hey Alfin,
>
> I have seen this before.  It sounds like the worker processor is not
> reporting back.
>
> Why else would a rest call to get agent status report nothing even though
> your tests are running?
>
> Have you tried to trace the comms using netstat?  You can do from both the
> console and agent host.  The agent host is more interesting.  I am guessing
> the worker processor initially opens a socket to the console; but closes
> soon after init (which it should not).
>
> HTH,
>
> Ouray
>
> On Thursday, November 19, 2015, Gary Mulder <[email protected]>
> wrote:
>
>> On 19 November 2015 at 22:09, Ouray Viney <[email protected]> wrote:
>>
>>> Hi Alfin ,
>>>
>>> How restrictive are the firewall rules between the agent and the console?
>>>
>>
>> Firewalls dropping or blocking connections are unlikely to cause
>> successful HTTP 200 codes but empty responses.
>>
>> Chances are you're seeing a blank JSON document because one or more of
>> the components that make up the document is not being generated by the
>> worker. At the end of the test this value is likely populated and so valid
>> info starts getting returned. I'd guess running the worker within a
>> debugger might help isolate the issue.
>>
>> Gary
>>
>
>
> --
> Sent from Gmail Mobile
>
> Ouray Viney
> Blog: https://www.viney.ca
> Skype: Ouray Viney
> LinkedIn: https://ca.linkedin.com/in/ourayvine
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> grinder-use mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/grinder-use
>
>

--001a1143b40c1deb8e0524fd67fd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Thanks guys for all the guidance.=C2=A0=C2=A0 I found the ro=
ot cause of our issue.=C2=A0=C2=A0 The worker process jvm was passing grind=
er.useConsole=3DFalse as an argument.=C2=A0 This was causing the worker pro=
cess to terminate the connection to the console when it&#39;s jvm was start=
ed up.=C2=A0 I believe during troubleshooting this flag was switched from t=
rue to false thinking it was required to run headless.<br></p>
<p dir=3D"ltr">Hope this helps anyone who might hit a similar issue in the =
future. </p>
<div class=3D"gmail_quote">On Nov 20, 2015 12:07 PM, &quot;Ouray Viney&quot=
; &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br ty=
pe=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hey Alfin,<div><br></div>=
<div>I have seen this before.=C2=A0 It sounds like the worker processor is =
not reporting back. =C2=A0</div><div><br></div><div>Why else would a rest c=
all to get=C2=A0agent status report nothing even though your tests are runn=
ing?</div><div><br></div><div>Have you tried to trace the comms using netst=
at?=C2=A0 You can do from both the console and agent host.=C2=A0 The agent =
host is more interesting.=C2=A0 I am guessing the worker processor initiall=
y opens a socket to the console; but closes soon after init (which it shoul=
d not).</div><div><br></div><div>HTH<span></span>,</div><div><br></div><div=
>Ouray</div><div><br>On Thursday, November 19, 2015, Gary Mulder &lt;<a hre=
f=3D"mailto:[email protected]" target=3D"_blank">flyingkiwiguy@gmail.=
com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div =
class=3D"gmail_extra"><div class=3D"gmail_quote">On 19 November 2015 at 22:=
09, Ouray Viney <span dir=3D"ltr">&lt;<a>[email protected]</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">Hi Alfin ,<div><br></div><div>How rest=
rictive are the firewall rules between the agent and the console?</div></bl=
ockquote><div><br></div><div>Firewalls dropping or blocking connections are=
 unlikely to cause successful HTTP 200 codes but empty responses.</div><div=
><br></div><div>Chances are you&#39;re seeing a blank JSON document because=
 one or more of the components that make up the document is not being gener=
ated by the worker. At the end of the test this value is likely populated a=
nd so valid info starts getting returned. I&#39;d guess running the worker =
within a debugger might help isolate the issue.</div><div><br></div><div>Ga=
ry</div></div></div></div>
</blockquote></div><br><br>-- <br>Sent from Gmail Mobile<p>Ouray Viney<br>B=
log: <a href=3D"https://www.viney.ca" target=3D"_blank">https://www.viney.c=
a</a><br>Skype:  Ouray Viney<br>LinkedIn: <a href=3D"https://ca.linkedin.co=
m/in/ourayvine" target=3D"_blank">https://ca.linkedin.com/in/ourayvine</a><=
br></p>
<br>-----------------------------------------------------------------------=
-------<br>
<br>_______________________________________________<br>
grinder-use mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]=
ceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/grinder-use" rel=3D=
"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo=
/grinder-use</a><br>
<br></blockquote></div>

--001a1143b40c1deb8e0524fd67fd--


--===============2569244363524698648==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------

--===============2569244363524698648==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
grinder-use mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/grinder-use

--===============2569244363524698648==--