[jcifs] Newbie question
jonathan.lister at vaisala.com
jonathan.lister at vaisala.com
Fri Nov 18 11:58:08 GMT 2005
I'm using jcifs to connect to a samba share on a linux server.
Using a call like this seems to work nicely from the client side;
public static String[] getSmbFileListEndingWith(String source, String
extension)
{
String [] sArray = null;
try
{
sArray = new SmbFile(source).list(new SmbEndsWithFilter(extension));
}
catch (MalformedURLException e)
{
log.severe("bad URL " + source + " " + e);
}
catch (SmbException e)
{
log.severe("Samba problem: " + e);
}
return sArray;
}
but in the samba log file on the server I get errors like:
[2005/11/18 11:41:58, 0] lib/util_sock.c:write_socket_data(500)
write_socket_data: write failure. Error = Broken pipe
[2005/11/18 11:41:58, 0] lib/util_sock.c:write_socket(523)
write_socket: Error writing 43 bytes to socket 12: ERRNO = Broken pipe
[2005/11/18 11:41:58, 0] lib/util_sock.c:send_smb(688)
Error writing 43 bytes to client. -1. (Broken pipe)
I have updated to jcifs 1.2.6, still get same errors on server.
client side log file includes these transport mesages:
Transport1: connect: state=0
Transport1: run connected
Transport1: connected: state=3
...
Transport1: disconnecting: state=3,mapsize=0,hard=false
Transport1: disconnected: state=3
Question: am I doing something stupid in the call, do I need to explicitly
close a connection?
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the jcifs
mailing list