[jcifs] jcifs.dcerpc.DcerpcPipeHandle: when close() doesn't

Del Merritt del at alum.mit.edu
Tue Mar 23 12:23:49 MDT 2010

In the 1.3.14 version of jcifs.dcerpc.DcerpcHandle's close() method the
SmbFileOutputStream "out" is closed but the corresponding
SmbFileInputStream "in" is not.  In practice this seems to mean there is
no way to guarantee the SmbTransport thread(s) created to handle
response data will be closed in a timely manner. 

This is a problem in a J2ME environment, where thread resources can be

Am I missing an "approved" way to ensure the timely closure of "in" and
thus the termination of the response thread(s)?


More information about the jCIFS mailing list