Re: Connection reset

On Mon, Sep 01, 2008 at 02:37:39AM -0400, Peter Jones wrote:
> On Thu, Aug 28, 2008 at 04:03:06AM -0700, Robert Gibson wrote:
>> 3) While I wait for the underlying problem to be fixed, in the face
>> of systematically dropped packets, would you still advise adjusting
>> the property sun.rmi.transport.tcp.responseTimeout assuming we can
>> find a value that allows "normal" calls to complete?
> 
> If it is helpful, then I suppose that it is fine to do.  But it
> doesn't seem related to the problem.  A possible workaround,
> although hacky, could be to set a server-side socket factory that
> wraps the socket output stream in a layered output stream that
> (re)buffers the data being written and forces all writes to the
> underlying socket output stream to be less than the maximum TCP data
> payload for the true path MTU of the connection (whatever that
> really is).

I should emphasize that this hack suggestion would be making various
implementation assumptions, and even then it might not keep the packet
size low enough if retransmission is necessary.  So it would not
guarantee a workaround to the problem, just perhaps reduce its
likelihood.  And if a workable value can be found, setting the timeout
property on the client may well be desired to avoid the client being
held up in the event of any network problem.

-- Peter

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html