Home > Archive > PERL POE > February 2007 > resource leak in PoCo::Server::SOAP ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
resource leak in PoCo::Server::SOAP ?
|
|
| Nicest of the Damned 2007-02-20, 4:18 am |
| Allo,
I think I'm seeing an edge case resource leak in PoCo::Server::SOAP
(or perhaps ::Server::SimpleHTTP , which handles the network interface
for ::SOAP) .
I have a monitoring system which connects to my daemon to make sure
the TCP socket is still connecting. The monitor just checks for
socket open, and then closes the socket without sending input or
recv'ing output.
this connection is leaving a socket stuck open on the server side in
CLOSE_WAIT state.
turning on TRACE_DEFAULT, I see in the closing heap-scan that the
SimpleHTTP object is building up REQUEST id's , with undef'd and 0'd
items.
if the server gets any data, the info gets into the SimpleHTTP
handler, and the connection is closed cleanly.
it's just this edge case where there's nothing to read from the socket
where the server-side isn't closing out cleanly if the client side
closes.
Thanks
-jer johnson
| |
| Nicest of the Damned 2007-02-20, 7:15 pm |
| On Feb 19, 3:12 pm, druelch...@gmail.com (Nicest of the Damned) wrote:
> I think I'm seeing an edge case resource leak in PoCo::Server::SOAP
> (or perhaps ::Server::SimpleHTTP , which handles the network interface
> for ::SOAP) .
that posting worked ! first time, coming from groups.google.
I should mention that the leak is with POE 0.9917 , PoCo::Server::SOAP
1.10 , PoCo::Server::SimpleHTTP 1.19
| |
| Rocco Caputo 2007-02-20, 7:15 pm |
| Please send a small test case, and cc bug-poe-component-server-
soap@rt.cpan.org. The author/maintainer for this component may not
be watching the list.
--
Rocco Caputo - rcaputo@pobox.com
On Feb 19, 2007, at 15:12, Nicest of the Damned wrote:
> Allo,
>
> I think I'm seeing an edge case resource leak in PoCo::Server::SOAP
> (or perhaps ::Server::SimpleHTTP , which handles the network interface
> for ::SOAP) .
>
> I have a monitoring system which connects to my daemon to make sure
> the TCP socket is still connecting. The monitor just checks for
> socket open, and then closes the socket without sending input or
> recv'ing output.
> this connection is leaving a socket stuck open on the server side in
> CLOSE_WAIT state.
>
> turning on TRACE_DEFAULT, I see in the closing heap-scan that the
> SimpleHTTP object is building up REQUEST id's , with undef'd and 0'd
> items.
>
> if the server gets any data, the info gets into the SimpleHTTP
> handler, and the connection is closed cleanly.
> it's just this edge case where there's nothing to read from the socket
> where the server-side isn't closing out cleanly if the client side
> closes.
>
> Thanks
>
> -jer johnson
| |
| Nicest of the Damned 2007-02-21, 7:25 pm |
| using POE-Component-Server-SOAP-1.10/examples/test-server.perl
1) run test-server.pl
2) telnet to localhost:32080
3) ^] escape out of telnet, and close the session
4) lsof on the test-server.pl pid shows the stuck socket:
perl 13566 jer 4u IPv4 88567728 TCP
localhost.localdomain:32080->localhost.localdomain:39865 (CLOSE_WAIT)
On Feb 20, 5:34 pm, rcap...@pobox.com (Rocco Caputo) wrote:[color=darkred]
> Please send a small test case, and cc bug-poe-component-server-
> s...@rt.cpan.org. The author/maintainer for this component may not
> be watching the list.
>
> --
> Rocco Caputo - rcap...@pobox.com
>
> On Feb 19, 2007, at 15:12, Nicest of the Damned wrote:
>
>
>
>
>
>
>
|
|
|
|
|