Broken Pipe when agents report to console
Joel Lucuik <[email protected]> Tue, 1 Nov 2016 13:33:36 -0400
| Newsgroups | gmane.comp.java.grinder.user |
|---|---|
| Message-ID | <CAA4qVTLunumsHz1f7GhmjdnSu9fTpbKQuM=bxorT2M8Scd1FzA@mail.gmail.com> |
--===============6128286402023687502== Content-Type: multipart/alternative; boundary=001a1134f1646c7c4d054040b974 --001a1134f1646c7c4d054040b974 Content-Type: text/plain; charset=UTF-8 Hi, Grinder version is 3-11. 4 vms, each VM has an agent, and the console shares a VM with the first agent. 10,0000 users (threads). Problem: We are occasionally seeing broken pipes when the agent(s) report anything to the console. My Investigation: I have been looking at the Grinder source. There is some code which traps CommunicationException such as AbstractSender.send() or ClientSender.blockingSend() but doesn't do anything with it. Such as attempt a reconnect if it's a Broken Pipe. Has this been fixed in newer versions? More specifically if the agent tries to send stats to the console, or a status update, and encounters a broken pipe, can it reconnect? Suggestions on which code/class/method to fix? We have very good unix people on our team. They have already upped the OS files, so we are (fairly) sure this is not the issue. Right now we are debating on a port to JMeter. Any advice would be appreciated. Joel --001a1134f1646c7c4d054040b974 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div><div><div>Hi,<br><br>Grinder version is 3-11.<br= >4 vms, each VM has an agent, and the console shares a VM with the first ag= ent. 10,0000 users (threads). <br><br></div>Problem: We are occasionally se= eing broken pipes when the agent(s) report anything to the console. <br></d= iv></div><div><br>My Investigation:<br><br>I have been looking at the Grind= er source. There is some code which traps CommunicationException such as <b= r><br>AbstractSender.send() or <br>ClientSender.blockingSend()<br><br>but d= oesn't do anything with it. Such as attempt a reconnect if it's a B= roken Pipe.<br><br></div><div>Has this been fixed in newer versions? More s= pecifically if the agent tries to send stats to the console, or a status up= date, and encounters a broken pipe, can it reconnect?<br><br></div><div>Sug= gestions on which code/class/method to fix?<br><br></div><div><br></div><di= v>We have very good unix people on our team. They have already upped the OS= files, so we are (fairly) sure this is not the issue.<br><br></div><div>Ri= ght now we are debating on a port to JMeter.<br><br></div><div>Any advice w= ould be appreciated.<br></div><div><br></div><div>Joel<br></div></div><br><= br></div> --001a1134f1646c7c4d054040b974-- --===============6128286402023687502== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi --===============6128286402023687502== 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 --===============6128286402023687502==--