vr has asked for the wisdom of the Perl Monks concerning the following question:

Hi, I have a large script which, among other things, gets output from several external workers. A problem occurs when workers complete at nearly the same time. At least, I think that is the reason. Then, randomly, instead of data, application may receive an empty string.

Here's a watered down version of server:

use strict; use warnings; use feature qw/ say /; use utf8; use Sereal qw/ sereal_decode_with_object /; use IO::Async::Loop; use IO::Async::Listener; use Future; $, = "\t"; my $PORT = 53123; my $num = 0; my $dec = Sereal::Decoder-> new; my $loop = IO::Async::Loop-> new; my $lst = IO::Async::Listener-> new( on_stream => sub { my ( $self, $stream ) = @_; $stream-> configure( on_read => sub { 0 }); $loop-> add( $stream ); $stream-> read_until_eof-> on_ready( sub { my $F = shift; my ( $buf, $eof ) = $F-> get; print ++$num, length( $buf ), unpack( 'H*', $buf ), ''; say sereal_decode_with_object( $dec, $buf ) }) } ); $loop -> add( $lst ); $lst-> listen( addr => { family => 'inet', socktype => 'stream', ip => '127.0.0.1', port => $PORT, }, )->on_done( sub { say "Listening on $PORT..." }); $loop-> run;

And here is a simple worker:

use strict; use warnings; use feature qw/ say /; use utf8; use autodie; use Sereal qw/ encode_sereal /; use IO::Socket::INET; my $PORT = 53123; say "hi, i'm $$"; while () { my $sock = new IO::Socket::INET( PeerHost => '127.0.0.1', PeerPort => $PORT, Proto => 'tcp', ) or die; binmode $sock; print $sock encode_sereal $$; $sock-> close; select( undef, undef, undef, 0.01 ); }

Then I run server and a single worker. After random interval, server crashes:

... 1685 9 3df3726c030020e009 1248 1686 9 3df3726c030020e009 1248 1687 9 3df3726c030020e009 1248 1688 9 3df3726c030020e009 1248 Sereal: Error: Bad Sereal header: Not a valid Sereal document. at offs +et 1 of input at srl_decoder.c line 573 at server.pl line 29. 1689 0

Why does it happen and can anything be done about it?

Replies are listed 'Best First'.
Re: Problem with IO::Async application
by zentara (Cardinal) on May 02, 2017 at 14:12 UTC
    Hi, your scripts seem to run fine for me running Slackware Linux and the latest modules.

    I'm not really a human, but I play one on earth. ..... an animated JAPH

      Thanks for testing. I checked, scripts run OK indefinitely long with Windows Server 2008, where real application is supposed to run. The failure occurs at old 32 bit WinXP, where I have a copy for tests and development. So, false alarm, sorry. Perl is Strawberry 5.24 both, + latest modules

      Update. Still, something strange is happening. Let now "server" be as simple as:

      use strict; use warnings; use IO::Socket::INET; my $PORT = 53123; my $num = 0; my $sock = new IO::Socket::INET( LocalHost => '127.0.0.1', LocalPort => $PORT, Proto => 'tcp', Listen => 5, Reuse => 1, ) or die; binmode $sock; while ( my $client = $sock-> accept ) { my $str = do { local $/; <$client> }; die "$num\n" unless $str eq '123'; print "$num\n" unless $num ++ % 1000; }

      And worker:

      use strict; use warnings; use autodie; use IO::Socket::INET; my $PORT = 53123; while () { my $sock = new IO::Socket::INET( PeerHost => '127.0.0.1', PeerPort => $PORT, Proto => 'tcp', ) or die; binmode $sock; print $sock '123'; $sock-> close; select( undef, undef, undef, 0.01 ) }

      Again, runs OK indefinitely long with Windows Server 2008, 64-bit Perl. And rarely does it go past a few thousands in WinXP, in:

      This is perl 5, version 24, subversion 0 (v5.24.0) built for MSWin32-x86-multi-thread-64int

      Which is somewhat disturbing. Is this my machine / installation somehow broken? Can't believe it's Perl issue. For not so long ago 32-bit OS (Windows i.e.) and 32-bit Perl were common.

        "Can't believe it's Perl issue."

        Clearly it is a Windows limitation. Would you mind sharing the requirements as to why you need asynchronous IO? Most of us do very well by leveraging existing tools such as database and web servers. xD