I've toyed around a demonstration, mainly out of curiosity. The example spawns a server process and 20 client processes via MCE::Flow. The server process itself has 10 background helpers.

For safety, never construct $pm inside a worker process. See Bugs and Limitations.

use strict;
use warnings;

use IO::Socket::INET;
use Parallel::ForkManager;
use MCE::Flow;
use POSIX ();

# Configure 10 bg_procs max for the server process.
# Never construct $pm inside a worker process.

my $pm = Parallel::ForkManager->new(10);
   $pm->set_waitpid_blocking_sleep(0);

# Configure MCE options. For this demonstration,
# 1 server process and 20 client processes.
# Stop the server after clients complete.

MCE::Flow::init {
    posix_exit  => 1,
    max_workers => [  1 ,  20 ],
    task_name   => [ 'S', 'C' ],
    task_end    => sub {
        my ($mce, $task_id, $task_name) = @_;

        if ($task_name eq 'C') {
            my ($client, $reply);

            $client = new IO::Socket::INET(
                PeerHost => 'localhost',
                PeerPort => 5000,
            );

            $reply = $client->getline;
            $reply =~ s/\r?\n//;

            $client->print("stop\n");
            $client->shutdown(SHUT_RDWR);
            $client->close;
        }
    },
};

# Run parallel 1 server process, 20 client processes.

mce_flow \&server, sub {
    my ($client, $reply);
    sleep 1;

    # Each client establishes a connection 4 times.

    for my $i ( 1 .. 4 ) {
        $client = new IO::Socket::INET(
            PeerHost => 'localhost',
            PeerPort => 5000,
        );

        $reply = $client->getline;
        $reply =~ s/\r?\n//;

        print "[$$:$i] got message : $reply\n";

        $client->print("Test $$:$i\n");

        $reply = $client->getline;
        $reply =~ s/\r?\n//;

        print "[$$:$i] got reply   : $reply\n";

        $client->print("quit\n");
        $client->shutdown(SHUT_RDWR);
        $client->close;
    }
};

exit;

sub server {
    require IO::Socket::INET::Daemon;

    IO::Socket::INET::Daemon->new(
        port => 5000, timeout => 20, callback => {
            add    => \&add,
            remove => \&remove,
            data   => \&data,
        },
    )->run;

    $pm->wait_all_children;
}

sub add {
    my $io = shift;
    $io->print("Welcome\n");
    return 1;
}

sub remove {
    my $io = shift;
}

sub data {
    my ($io, $host) = @_;
    my $line = $io->getline;

    $line =~ s/\r?\n//;

    if ($line eq 'quit') {
        return 0;
    }
    elsif ($line eq 'stop') {
        $host->stop;
    }
    else {
        $io->print("Reply $line\n");
        $pm->start and return 1;
        fork_work($line);
        $pm->finish; # not reached
    }
}

sub fork_work {
    my ($line) = @_;

    print "[$$] working from child -- $line\n";
    sleep 1;  # simulate work

    # A given CPAN module maybe multi-process unsafe regarding
    # DESTROY and END blocks. Fortunately, there's a way around it.

    POSIX::_exit(0);
}

[download]

The demonstration completes in 9 seconds. Initially, clients sleep for 1 second giving time for the server process. Although there are 20 clients, the server process allows 10 background processes max. Each client loops 4 times for a total of 80 connections. There's also a delay for simulating work.

[24169:1] got message : Welcome
[24167:1] got message : Welcome
[24155:1] got message : Welcome
[24169:1] got reply   : Reply Test 24169:1
[24170] working from child -- Test 24169:1
[24164:1] got message : Welcome
[24167:1] got reply   : Reply Test 24167:1
[24155:1] got reply   : Reply Test 24155:1
[24171] working from child -- Test 24167:1
[24172] working from child -- Test 24155:1
[24153:1] got message : Welcome
[24164:1] got reply   : Reply Test 24164:1
[24173] working from child -- Test 24164:1
...
[24151:4] got message : Welcome
[24156:4] got reply   : Reply Test 24156:4
[24246] working from child -- Test 24156:4
[24165:4] got message : Welcome
[24151:4] got reply   : Reply Test 24151:4
[24247] working from child -- Test 24151:4
[24154:4] got message : Welcome
[24165:4] got reply   : Reply Test 24165:4
[24154:4] got reply   : Reply Test 24154:4
[24248] working from child -- Test 24165:4
[24249] working from child -- Test 24154:4

[download]

Regards, Mario

In reply to Re^2: IO::Socket::INET::Daemon and Parallel::ForkManager working together by marioroy
in thread IO::Socket::INET::Daemon and Parallel::ForkManager working togheter by leostereo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.