Project

General

Profile

Actions

Bug #9753

closed

UNIX Socket doesn't handle multiple clients

Added by ThomasWLynch (Thomas Lynch) over 10 years ago. Updated over 10 years ago.

Status:
Rejected
Assignee:
-
Target version:
-
ruby -v:
ruby 2.0.0p353 (2013-11-22 revision 43784) [x86_64-linux]
[ruby-core:62073]

Description

When a first client session is still active, a second client session starting then closing its connection causes the first session to hang.

This can be reproduced every time by using the included source files and these directions:

A. open three terminals, say T1,T2, and T3

1. in T1 start the server2

   > ./simple_server2.rb

2. in T2 run the slow client and see that it works

   > ./simple_client_slow.rb


3. in T3 run the regular client and see that it works too

   > ./simple_client.rb

B. now go back to T2 and run simple_client_slow, then reasonably quickly
go to T3 and run simple_client

what you will see:  simple_client finishes first, and simple_slow hangs

Note also the enclosed screen shots showing the hang.

Hanging sessions with no known workaround for Unixsockets is fairly serious so I'll set this to priority high. I didn't set it to urgent because the code can be rewritten to use TCP sockets, however it is unknown of the problem is there also.


Files

simple_server2.rb (482 Bytes) simple_server2.rb ThomasWLynch (Thomas Lynch), 04/17/2014 10:23 AM
simple_client_slow.rb (578 Bytes) simple_client_slow.rb ThomasWLynch (Thomas Lynch), 04/17/2014 10:23 AM
simple_client.rb (407 Bytes) simple_client.rb ThomasWLynch (Thomas Lynch), 04/17/2014 10:23 AM
Screenshot from 2014-04-17 09_50_35.png (74 KB) Screenshot from 2014-04-17 09_50_35.png ThomasWLynch (Thomas Lynch), 04/17/2014 10:30 AM
Screenshot from 2014-04-17 09_53_26.png (82 KB) Screenshot from 2014-04-17 09_53_26.png ThomasWLynch (Thomas Lynch), 04/17/2014 10:30 AM
Actions

Also available in: Atom PDF

Like0
Like0