Console socket from agent cycling close_wait

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Console socket from agent cycling close_wait

Darren Ball
I am wondering why I see the following behaviour, which eventually causes error sending messages to the console on worker startup.
Seems like the connection is bouncing frequently.


tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 


This ends up causing:
net.grinder.communication.CommunicationException: Exception whilst sending message

Anyone else have this?

I see this when my test startup (I have an initialization) takes a longer period of time than usual.

Anyway to solve for this?



------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
grinder-use mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/grinder-use
Reply | Threaded
Open this post in threaded view
|

Re: Console socket from agent cycling close_wait

Darren Ball
Here is the 'fix' for this. A co-worker and I simply added a keep-alive on the socket.
Seems to work for me.



On Fri, Mar 18, 2016 at 11:09 AM, Darren Ball <[hidden email]> wrote:
I am wondering why I see the following behaviour, which eventually causes error sending messages to the console on worker startup.
Seems like the connection is bouncing frequently.


tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50973         10.82.151.5:6372            ESTABLISHED 
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 
tcp       73      0 192.168.12.105:50973         10.82.151.5:6372            CLOSE_WAIT  
tcp        0      0 192.168.12.105:50963         10.82.151.5:6372            ESTABLISHED 


This ends up causing:
net.grinder.communication.CommunicationException: Exception whilst sending message

Anyone else have this?

I see this when my test startup (I have an initialization) takes a longer period of time than usual.

Anyway to solve for this?




------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
grinder-use mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/grinder-use

my_changes_for_keepalive_for_grinder_agents.patch (2K) Download Attachment