Hi all
How can be closed client connection @ server side if server is based on Net::Server::Multiplex module? In my code I used
for $h ($mux->handles()) {
if ($fhs->{$h}{object}{user}{_id} == $id) {
$mux->remove($h); # remove from multiplexer loop
$mux->close($h); # close handle
last;
}
}
to find handle of connection to be closed an close it. Sometimes this works ok, but sometimes it broke down whole server with message 'Use of uninitialized value in exists at /opt/perl-5.8.0_t/lib/site_perl/5.8.0/IO/Multiplex.pm line 596 (#1)'. IO::Multiplex contain
591:
592: foreach my $fh (values %{$self->{_handles}}) {
593: # Avoid creating a permanent empty hash ref for "$fh"
594: # by attempting to access its {object} element
595: # if it has already been closed.
596: next unless exists $self->{_fhs}{$fh};
597:
$mux->remove($h) call shold remove entry for closed connection from this %{$self->{_handles}} hash. Is it a race condition? How to fix it?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|