BrowserUk has asked for the wisdom of the Perl Monks concerning the following question:
I attempted to extend the sample code I posted in Re: Transfer a hash using client and server in perl to make it do and handle concurrent clients. I tried this:
#! perl -slw use strict; use threads; use IO::Socket; use Storable qw[ freeze thaw ]; use Data::Dump qw[ pp ]; $|++; my %hash; @hash{ 'a'..'h' } = 1 .. 8; my $lsn = new IO::Socket::INET( Listen => 5, LocalPort => '12345' ) or die "Failed to open listening port: $!\n"; async{ print 'accept loop started'; while( my $c = $lsn->accept ) { print "Connect from $c"; binmode $c; async { while( my $cmd = <$c> ) { print "Got '$cmd'"; last if $cmd =~ m[^quit]; printf $c "%s", pack "N/a*", freeze \%hash; } print "Got quit from $c"; close $c; }->detach; } }->detach; sleep 2; for my $client ( 1 .. 2 ) { # async { print "Client $client started"; my $s = new IO::Socket::INET( 'localhost:12345' ) or die "Failed to connect to server: $!"; print "client $client connected"; binmode $s; for ( 1 .. 2 ) { print $s 'givemeit'; print 'Sent givemeit'; my $len; read( $s, $len, 4 ) or die "Read failed: $!"; $len = unpack 'N', $len; print "read length: $len"; my $hashStr; read( $s, $hashStr, $len ) or die "Read failed: $!"; print "Read hashstr length: ", length $hashStr; my %hash = %{ thaw $hashStr }; pp \%hash; } print $s 'quit'; close $s; print "client; $client disconnected"; # }->detach; } sleep 1 while 1;
Which works perfectly. It serially connects to the server (twice), transmits a couple of hashes and disconnects. The server then awaits further connection until ^C.
But if you uncomment the #async{ & }->detach; lines in order to allow the clients to run concurrently, nothing happens. The listener starts and awaits a connection. The clients loop is entered and the async() is dispatched, but the thread never starts and async doesn't return. No errors. Just nothing.
But the weird part is, if I connect to the listener from an external process (telnet), the client threads start, run concurrently and finish as designed.
So the question is, what is it about connecting from an external process that causes the in-process client threads to start?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: threads + sockets stalling question
by ikegami (Patriarch) on Mar 16, 2010 at 14:04 UTC | |
by BrowserUk (Patriarch) on Mar 16, 2010 at 14:54 UTC | |
by BrowserUk (Patriarch) on Mar 17, 2010 at 14:38 UTC | |
by Corion (Patriarch) on Mar 17, 2010 at 14:53 UTC | |
by BrowserUk (Patriarch) on Mar 17, 2010 at 16:08 UTC | |
by ikegami (Patriarch) on Mar 17, 2010 at 16:24 UTC | |
| |
Re: threads + sockets stalling question
by almut (Canon) on Mar 16, 2010 at 13:36 UTC |