RFR: 8017195 : Introduce option to setKeepAlive parameter on CORBA sockets
chris.hegarty at oracle.com
Tue Sep 3 12:58:03 UTC 2013
I remember discussing this (offlist) with you a while back, and I agree
with the proposed solution.
The logic for checking the system property looks a little odd. But I
will admit views differ on exactly what values should be accepted. So,
trivially I would suggest making keepAlive final and always setting it
in the static initializer.
Otherwise, looks fine to me.
On 09/03/2013 01:04 PM, Seán Coffey wrote:
> Sockets created by the
> com.sun.corba.se.impl.transport.DefaultSocketFactoryImpl factory can be
> affected by firewalls if that connection is left idle for long periods
> of time. (closed out). A workaround for such an issue could be to have a
> simple corba thread send some simple ping traffic on the socket at
> scheduled intervals. That may not be possible for legacy applications.
> Proposed solution is to add an implementation specific system property
> flag which would have the keepAlive feature turned on for sockets
> returned by the CORBA DefaultSocketFactoryImpl class. The application is
> then in a better position to manage the keepAlive settings via the OS.
> This had been fixed in Java SE 6 and I'm looking to port the new
> property to jdk7u & jdk8.
More information about the core-libs-dev