This content has been marked as final. Show 3 replies
Well what I would do is add trace logging. Let the application log out what it does at trace logging level, then check what was last in the logs. That should give a clue where the problem originates.
And THEN... its a question of trying to reproduce the problem locally, which can be an incredibly annoying and time consuming process :/
Do you have a clue how long it takes before the application 'suddenly disappears' ? It might be related to the heap space running out, meaning you have a memory or resource leak somewhere.
user6820833 wrote:Catch "Throwable" not Exception at the root of every thread. And log it.
Any suggetion to debug this problem ????
You can also look at java.lang.Thread.setUncaughtExceptionHandler();
Also create a log statement for the exit of every thread. Because if every thread exits then so does the application.
You would need to do the above in every thread.