Skip Menu |

This queue is for tickets about the Catalyst-Plugin-Server CPAN distribution.

Report information
The Basics
Id: 31163
Status: resolved
Priority: 0/
Queue: Catalyst-Plugin-Server

People
Owner: Nobody in particular
Requestors: alexp [...] transitive.com
Cc:
AdminCc:

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



Subject: Server::XMLRPC fails to close filehandles
Date: Mon, 03 Dec 2007 11:48:23 +0000
To: bug-catalyst-plugin-server [...] rt.cpan.org
From: Alex Page <alexp [...] transitive.com>
Hi there, I set up a Catalyst application which provides an XMLRPC backend. The application runs on Apache 2 under mod_perl. Functionally it works fine, but as it runs, it generates many files in /tmp which seem to contain the raw XML of the XMLRPC queries. Not only do these files take up disk space, but Apache rapidly collects open file descriptors to these files. This causes my web server to fall over in ~24 hours because it runs out of file descriptors. Disabling Server::XMLRPC in my application's "use Catalyst" line means that these files are not created and that Apache doesn't collect filehandles. Alex -- Alex Page, Release Engineer, Transitive Limited Maybrook House, 40 Blackfriars Street, Manchester M3 2EG, UK Web: http://www.transitive.com/ | Phone: (+44) 161-214-0406
On Mon Dec 03 06:48:49 2007, alexp@transitive.com wrote: Show quoted text
> I set up a Catalyst application which provides an XMLRPC backend. The > application runs on Apache 2 under mod_perl. Functionally it works fine, > but as it runs, it generates many files in /tmp which seem to contain > the raw XML of the XMLRPC queries.
I didn't see any open calls in Server::XMLRPC, but the module it uses for parsing XML, RPC::XML seems to be full ofthem: lib/RPC/XML/Client.pm: return "$me: Error opening $tmpfile: $!" lib/RPC/XML/Client.pm: unless (open($req_fh, "+> $tmpfile")); lib/RPC/XML/Client.pm: return "$me: Error opening $tmpfile: $!" lib/RPC/XML/Client.pm: unless (open($fh2, "+> $tmpfile")); Could you verify if it's not this module that has the issue? If so, the ticket should probably be moved.
No new input and not reproducable, closing.