[jcifs] Alternative to jcifs.http.NtlmHttpFilter
Allen, Michael B (RSCH)
Michael_B_Allen at ml.com
Thu Oct 24 07:58:55 EST 2002
I noticed a Socket exception in the Resin stderr log. It was the exception
you get when you try to use a socket that was quitely closed at the
server side. I didn't get an error in IE and the client authenticated ok but it lead
me to believe 10 minutes was a little too long so I bumped it down to 5. I
would rather close the socket knowing what state it's in before the server
closes the socket at it's end and have to resumit a request. By all means feel
free to explore that more.
> -----Original Message-----
> From: eglass1 at attbi.com [SMTP:eglass1 at attbi.com]
> Sent: Wednesday, October 23, 2002 5:08 AM
> To: Allen, Michael B (RSCH)
> Cc: 'Michael Piscatello'; jcifs at lists.samba.org
> Subject: RE: [jcifs] Alternative to jcifs.http.NtlmHttpFilter
> I noticed that the jcifs.smb.client.soTimeout in the
> filter was set to 5 minutes. Is this still necessary?
> Also, was there a significance behind the change from 10
> to 5 minutes? Just curious.
More information about the jcifs