Skip Menu |

This queue is for tickets about the POE CPAN distribution.

Report information
The Basics
Id: 19797
Status: resolved
Priority: 0/
Queue: POE

People
Owner: Nobody in particular
Requestors: manly.mike [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Please mail the following information to bug-POE@rt.cpan.org:
Date: Thu, 8 Jun 2006 17:20:57 -0400
To: bug-POE [...] rt.cpan.org
From: "Mike Adkins" <manly.mike [...] gmail.com>
can't watch the same handle in the same mode 2+ times yet at /usr/lib/perl5 /site_perl/5.8.1/POE/Resource/FileHandles.pm line 410 POE::Kernel::_data_handle_add('POE::Kernel=ARRAY(0x87c2a98)','IO::S ocket::INET=GLOB(0x93fc4f8)',1,'POE::Session=ARRAY(0x934927c)','write') cal led at /usr/lib/perl5/site_perl/5.8.1/POE/Kernel.pm line 1795 POE::Kernel::_internal_select('POE::Kernel=ARRAY(0x87c2a98)','POE:: Session=ARRAY(0x934927c)','IO::Socket::INET=GLOB(0x93fc4f8)','write',1) cal led at /usr/lib/perl5/site_perl/5.8.1/POE/Kernel.pm line 1862 POE::Kernel::select_write('POE::Kernel=ARRAY(0x87c2a98)','IO::Socke t::INET=GLOB(0x93fc4f8)','write') called at /usr/lib/perl5/site_perl/5.8.3/ POE/Component/Client/UserAgent.pm line 184 POE::Component::Client::UserAgent::_add_out_socket('POE::Component: :Client::UserAgent=HASH(0x9345498)','IO::Socket::INET=GLOB(0x93fc4f8)') cal led at /usr/lib/perl5/site_perl/5.8.3/LWP/Parallel/UserAgent.pm line 754 LWP::Parallel::UserAgent::_connect('POE::Component::Client::UserAge nt=HASH(0x9345498)','LWP::Parallel::UserAgent::Entry=HASH(0x93fc744)') call ed at /usr/lib/perl5/site_perl/5.8.3/POE/Component/Client/UserAgent.pm line 174 POE::Component::Client::UserAgent::_connect('POE::Component::Client ::UserAgent=HASH(0x9345498)','LWP::Parallel::UserAgent::Entry=HASH(0x93fc74 4)') called at /usr/lib/perl5/site_perl/5.8.3/LWP/Parallel/UserAgent.pm lin e 644 LWP::Parallel::UserAgent::_check_bandwith('POE::Component::Client:: UserAgent=HASH(0x9345498)','LWP::Parallel::UserAgent::Entry=HASH(0x93fc744) ') called at /usr/lib/perl5/site_perl/5.8.3/LWP/Parallel/UserAgent.pm line 586 LWP::Parallel::UserAgent::_make_connections_unordered('POE::Compone nt::Client::UserAgent=HASH(0x9345498)') called at /usr/lib/perl5/site_perl/ 5.8.3/LWP/Parallel/UserAgent.pm line 549 LWP::Parallel::UserAgent::_make_connections('POE::Component::Client ::UserAgent=HASH(0x9345498)') called at /usr/lib/perl5/site_perl/5.8.3/POE/ Component/Client/UserAgent.pm line 116 POE::Component::Client::UserAgent::_pococ_ua_request('POE::Componen t::Client::UserAgent=HASH(0x9345498)','POE::Session=ARRAY(0x934927c)','POE: :Kernel=ARRAY(0x87c2a98)','HASH(0x93491bc)','request','POE::Session=ARRAY(0 x92b5b38)','undef','/home/madkins/asia/lib/ASIA/Monitor.pm',174,...) called at /usr/lib/perl5/site_perl/5.8.1/POE/Session.pm line 646 POE::Session::_invoke_state('POE::Session=ARRAY(0x934927c)','POE::S ession=ARRAY(0x92b5b38)','request','ARRAY(0x93f3f04)','/home/madkins/asia/l ib/ASIA/Monitor.pm',174) called at /usr/lib/perl5/site_perl/5.8.1/POE/Kerne l.pm line 858 POE::Kernel::_dispatch_event('POE::Kernel=ARRAY(0x87c2a98)','POE::S ession=ARRAY(0x934927c)','POE::Session=ARRAY(0x92b5b38)','request',1,'ARRAY (0x93f3f04)','/home/madkins/asia/lib/ASIA/Monitor.pm',174,1149515557.54137, ...) called at /usr/lib/perl5/site_perl/5.8.1/POE/Resource/Events.pm line 2 46 POE::Kernel::_data_ev_dispatch_due('POE::Kernel=ARRAY(0x87c2a98)') called at /usr/lib/perl5/site_perl/5.8.1/POE/Loop/Select.pm line 325 POE::Kernel::loop_do_timeslice('POE::Kernel=ARRAY(0x87c2a98)') call ed at /usr/lib/perl5/site_perl/5.8.1/POE/Loop/Select.pm line 333 POE::Kernel::loop_run('POE::Kernel=ARRAY(0x87c2a98)') called at /us r/lib/perl5/site_perl/5.8.1/POE/Kernel.pm line 1001 POE::Kernel::run('POE::Kernel=ARRAY(0x87c2a98)') called at asia.plline 90
Thanks for the bug report. The message you encountered is most often caused by a file descriptor leak. You can also get it by explicitly closing a filehandle before unregistering it with POE. Both of these problems originate in your code, not POE itself. I've changed the error message so that POE stops taking responsibility for so many problems is user code.