[jcifs] WebSphere

eglass1 at comcast.net eglass1 at comcast.net
Wed Oct 22 18:59:48 EST 2003

I had seen this intermittently awhile back as well, but never had it cause any operational issues (other than the annoying messages dumped to stderr).  If I recall, it seemed to be caused by a timeout; I never got it when activity was occurring on the connection, but would get it on a background thread a couple minutes after i.e. an HTTP authentication with the NTLM filter.  Could the dc be closing the connection due to lack of activity?  I'll see if I can reproduce it; if that's all it is, the easiest fix might just be to skip the log statement for SocketExceptions.

Has anyone had any "bad" errors caused by this?

> > I use the NtlmHttpFilter from jcifs-0.7.8 on WebSphere 5.
> <snip>
> > I get the following error:
> >
> > Okt 21 16:29:15.177 - exception reading from socket input:
> ><00>/
> > java.net.SocketException: Connection reset by peer: socket closed
> <snip>
> > Does anyone know what the problem is?
> No, but someone else just reported the exact same problem using 0.7.14 on
> WebSphere. What are the circumstances with which you get this exception?
> Does the filter work? Does the exception occur frequently?
> Also, you might consider asking IBM support too.
> Mike
> -- 
> A program should be written to  model the concepts of the task it
> performs rather than the physical world or a process because this
> maximizes the  potential for it  to be applied  to tasks that are
> conceptually similar and, more  important, to tasks that have not
> yet been conceived.

More information about the jcifs mailing list