Hi all, We're in the process of upgrading from hapi 1.2 to 2.2. With 1.2, we used to be able to call Socket.setSOTimeout() and when that timeout tripped, the connection using the socket would nicely shut down. 2.2 seems to catch the exception, ignore it and keep on going.
Is there some other mechanism we can use to automatically shut down a connection after a certain period of inactivity? We need this functionality to prevent leaks in our hl7 servers in environments where clients crash or firewalls silently drop connections. I'd be happy to submit a patch but would want some feedback first. Would it be acceptable to close the connection when a SocketTimeoutException happens? Are there legitimate use cases for triggering and then recovering from a timeout? Jeremy Huiskamp | karoshealth Software Engineer 7 Father David Bauer Drive, Suite 201 Waterloo, ON, N2L 0A2, Canada www.karoshealth.com
------------------------------------------------------------------------------
_______________________________________________ Hl7api-devel mailing list Hl7api-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hl7api-devel
