In a recent application running on MySQL we frequently faced application deadlocks caused by irresponsive database. After looking at it carefully, in most of the cases, the tables were created using the MyISAM engine locking the entire table even when the user was just issuing long running SELECT statements.
After changing the engine to InnoDB to a number of tables with frequent updates, the problem has been solved.
Occassionally JDeveloper fails to start after an abnormal termination. The reasons are not obvious, but this small trick will help you identify the problems behind the failure.
Instead of starting JDeveloper from the normal jdeveloper.exe or a link pointing to it, start from the same directory by using the command jdev/bin/jdev.exe, passing the same parameters as when invoking the jdeveloper.exe. You will not be able to successfully restart, but a lot of debug information will be provided to you, enabling you to identify the error. In my case, jDeveloper had a lock on one of the adfc-config.xml files; I had to rename it, as I couldn’t find where this lock was kept, start jdeveloper and then rename it back to the original name.