I think a quick fix is to change from calling scheduleAtFixedRate to just
calling schedule, this different being the way the interval between
executions is controlled.
For scheduleAtFixedRate which we use now execution rate is scheduled based
on the time that the task was first scheduled.
>
hmm, that sounds like a reasonable theory... seems like a scheduled
executor is the answer or a scheduler that uses cpu relative time...
so that sleep time is ignored.
Can you raise a jira issue to track this, there are a few schedulers
in the code base, so they may all need the same treatment.
O
Using activemq 5.4.0 for a P2P desktop applicaiton, I get an OOME when
my computer awakes from sleep:
Exception in thread "InactivityMonitor WriteCheck"
java.lang.OutOfMemoryError: unable to create new native thread
The cause appears to be:
- WRITE_CHECK_TIMER schedules checks at a fixed rate
