Thanks for your answer.
The stacktrace doesn't really indicate a deadlock situation.
=> thats why I called it 'invisible'
Could also be a condition wherein you are using far too many timers
and thus starving the
EDT ??? (The javadoc comment of the postExpiredTimers method of the
TimerQueue
class seems to indicate that this could happen if there are a lots of
timers)
=> my app creates directly about 10 timer in a range between 1 and 3
seconds - I think that's not the problem.
Also check your threads that are in sleep() state to see if they are
holding any
locks.
=> I checked this with eclipse - no locks to see. Can I get more Info
than eclipse or the dump offers?
In the freeze situation my App uses less than 1% CPU time - no
indication for a loop situation.
I have removed most of the Timer.stop() to see if it works now better.
I am not in the office the next 14 days - vacation :-) - I'll report
about the result when I am back.
Peter