[jcifs] Intermittent Broken Pipes
Allen, Michael B (RSCH)
Michael_B_Allen at ml.com
Fri Jul 25 08:43:48 EST 2003
Ok. Thanks for the followup.
> -----Original Message-----
> From: todd runstein [SMTP:todd_run at yahoo.com]
> Sent: Thursday, July 24, 2003 4:44 PM
> To: Allen, Michael B (RSCH)
> Subject: RE: [jcifs] Intermittent Broken Pipes
>
> Mike,
>
> Thanks for your quick response. The problem seems to
> have fixed itself. This was the first symptom of a
> problem which finally culminated in a server crash.
> Once the server was brought back up, the problem
> magically disappeared.
>
> I was pretty certain jcifs was not a contributing
> factor, but I figured it would be better to see if
> anyone had any ideas or had seen this before. Thanks
> again for taking time to respond!
>
> Todd
>
>
> --- "Allen, Michael B (RSCH)" <Michael_B_Allen at ml.com>
> wrote:
> > The server is trying to write to a closed socket.
> >
> > How long does it take to happen? Does this happen
> > after the jcifs client is
> > sitting there doing nothing for a while? The only
> > thing I can think of is
> > the scenario where jcifs connects and waits for the
> > server to write
> > something. I believe the client may close the
> > connection after
> > jcifs.smb.client.soTimeout in this case.
> >
> > Otherwise, can you get a packet capture of this
> > happening? That will tell us
> > which is culprit, jcifs or the server.
> >
> > Tell me more about what the app is doing. What pipe
> > modes are you using
> > on both the server and with jCIFS.
> >
> > Mike
> >
> > > -----Original Message-----
> > > From: todd [SMTP:todd_run at yahoo.com]
> > > Sent: Wednesday, July 23, 2003 8:12 PM
> > > To: jcifs at lists.samba.org
> > > Subject: [jcifs] Intermittent Broken Pipes
> > >
> > > I'm get intermittent errors trying to create
> > directories on a Linux/Smb
> > > machine using mkdirs. I've tried using 0.7.9 and
> > 0.7.11. This tends to
> > > work fairly reliably if I run the code on a Linux
> > machine with a Linux
> > > target machine or if I run it on either platform
> > to a Windows target.
> > > Running the code on Windows to a Linux target
> > yeilds anywhere from 0%
> > > success (yesterday afternoon) to 50% success
> > (today).
> > >
> > > The error code from the SmbException is 5000 with
> > a message of "Timeout
> > > waiting for response from server". Here is a
> > sample of the error from
> > > the samba log on the target machine:
> > >
> > >
> > > [2003/07/23 14:57:13, 0]
> > lib/util_sock.c:write_socket_data(499)
> > > write_socket_data: write failure. Error =
> > Broken pipe
> > > [2003/07/23 14:57:13, 0]
> > lib/util_sock.c:write_socket(524)
> > > write_socket: Error writing 43 bytes to socket
> > 12: ERRNO = Broken pipe
> > > [2003/07/23 14:57:13, 0]
> > lib/util_sock.c:send_smb(704)
> > > Error writing 43 bytes to client. -1. (Broken
> > pipe)
> > >
> > >
> > > Any ideas why this is occuring or what steps I can
> > take to troubleshoot
> > > it and make it more reliable?
> > >
> > > Thanks in advance
> > >
> > > Todd
> > >
> > >
> > >
> >
>
>
> =====
> The only "dumb question" is the one you were too afraid to ask.
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
More information about the jcifs
mailing list