Re: [Py4j-users] A question about life cycle control of sockets in GatewayServer instance
Status: Beta
Brought to you by:
barthe
From: Barthelemy D. <ba...@cs...> - 2012-07-14 15:24:16
|
Hi Jason, If you are speaking of GatewayServer on the Java side, it is a bug. Sockets in the connections list should be removed once a GatewayConnection is closed. This will require a small refactoring because the gateway connection is closed in one thread and the shutdown method on the gatewayserver can be called in another thread. Thanks for reporting this bug, Barthélémy On 2012-07-14, at 10:42 AM, Jason Ni wrote: > Hello, > > There is a List member "connections" in GatewayServer object. It holds every socket object until the GatewayServer is shutdown. This may be not good for this use case: the GatewayServer is providing a kind of service. Python clients connect to the GatewayServer, do some communication, close the connect and end the Python process, but not shutdown the server. After many times of this kind of connections, I see those socket objects are held in the "connections" list and not garbage collected. > Is this working as design or I did something wrong? > > Thanks, > > - Jason > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ > Py4j-users mailing list > Py4...@li... > https://lists.sourceforge.net/lists/listinfo/py4j-users |