[jcifs] Thread deadlock

[Michael B.Allen]

On Wed, 19 Mar 2003 11:11:58 -0700 (MST)
"Jason Scherer" <jscherer at blackfintech.com> wrote:

> I am using Windows 2000 server and Sun JDK 1.3.1.  The samba api is being

JCIFS != Samba

> used to go from one Windows 2000 server to another Windows 2000 server.
> After looking at this more, I think you are right that it isn't deadlock. 
> What seems to happen is this:
> The file that is being copied from the source machine to the destination
> machine is created on the destination machine with 0 bytes, and then the
> process hangs.  Using the samba api I can delete the 0 byte file but if I
> try to do anything else with the file I get an "invalid file handle"
> error.
> I have waited 30 minutes for the process to timeout, but it never seems to
> timeout.

If this is really true then it is a deadlock. If a request is sent
and *that request* does not timeout in one way or another then it is a
deadlock. Or it's a JVM or Win2K bug.

> One time the process gets in this state, and the next time it runs fine
> with the same set of files so it isn't the files that are being copied
> that are the problem.

Can you please send me a copy of your program with the necessary
instructions to run it? Perhaps you can reduce it to the minimum amount
of code necessary to trigger the problem?

Send it to my ml.com address.

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.