Memory leak with XMLRPC and Perl...
Hello,
I wrote a program in Perl (using version 5.8.4), that using XMLRPC to
communicate between the client and the server. The call from the
client to the server sitting in a infinite loop that can be run in
random inteval time.
After sometime that the client is running the perl's proccess taking
~70MB of ram and ~100% of the CPU usage.
May you know why?
TNX.
.
Relevant Pages
- Re: What doesnt lend itself to OO?
... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
(comp.object) - This is going straight to the pool room
... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
(comp.os.vms) - Re: jboss normal client/server communication
... > some client side libraries for marshalling and setting up the ... > Setting up a servlet on the server and communicate directly with this ... The servlet could even emit ... > going to run in the same local area network as the server, ...
(comp.lang.java.programmer) - [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
(Full-Disclosure) - Re: What doesnt lend itself to OO?
... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
(comp.object) |
|
