Is it possible for competing file access to cause deadlock in Java?

Temporarily setup your production process to startup with debugging support, add this to how you're starting your java program or to say the tomcat startup.

Temporarily setup your production process to startup with debugging support, add this to how you're starting your java program or to say the tomcat startup: -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n Then attach to it: jdb -connect com.sun.jdi. SocketAttach:hostname=localhost,port=8000 And take a look at your stack(s).

FileLock is an inter-process locking mechanism. It does nothing within the same JVM, so that isn't it. I would look at your synchronizations, and specifically at making sure you always acquire multiple locks in the same order.

I've gotten some useful tips for chasing the underlying bug, but based on the responses I've gotten, it would seem the correct answer to the actual question is: No. Damn. That was anti-climactic.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.