Weird exception in server.log

0 views

Skip to first unread message

hrajchert

unread,

Mar 16, 2010, 11:45:33 AM3/16/10

to mobicents-public

Hi, I'm using mobicents 1.2.6.GA with a server that is running 24/7.
Aparently 3 times a day it throws me this exception:

2010-03-12 21:35:24,208 WARN
[org.mobicents.slee.runtime.facilities.TimerFacilityImpl] Failed to
schedule new task with system timer. Will recycle system timer and
retry.
java.lang.IllegalStateException: Task already scheduled or cancelled
at java.util.Timer.sched(Timer.java:358)
at java.util.Timer.schedule(Timer.java:184)
at org.mobicents.slee.runtime.facilities.TimerFacilityImpl
$TimerFacilityAction
$TimerStarterTask.scheduleOneTimeTask(TimerFacilityImpl.java:167)
at org.mobicents.slee.runtime.facilities.TimerFacilityImpl
$TimerFacilityAction$TimerStarterTask.run(TimerFacilityImpl.java:127)
at
EDU.oswego.cs.dl.util.concurrent.DirectExecutor.execute(DirectExecutor.java:
30)
at org.mobicents.slee.runtime.facilities.TimerFacilityImpl
$TimerFacilityAction.execute(TimerFacilityImpl.java:214)
at
org.mobicents.slee.runtime.transaction.TxLocalEntry.executeActions(TxLocalEntry.java:
151)
at
org.mobicents.slee.runtime.transaction.TxLocalEntry.executeAfterCommitActions(TxLocalEntry.java:
111)
at
org.mobicents.slee.runtime.transaction.TransactionManagerImpl.executeAfterCommitActions(TransactionManagerImpl.java:
405)
at
org.mobicents.slee.runtime.transaction.TransactionManagerImpl.access
$200(TransactionManagerImpl.java:60)
at
org.mobicents.slee.runtime.transaction.TransactionManagerImpl
$SynchronizationHandler.afterCompletion(TransactionManagerImpl.java:
232)
at
com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:
136)
at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:
340)
at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:
93)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:
177)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:
1389)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:
135)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:
87)
at
org.mobicents.slee.runtime.transaction.TransactionManagerImpl.commit(TransactionManagerImpl.java:
348)
at
org.mobicents.slee.runtime.EventRouterImpl.routeQueuedEvent(EventRouterImpl.java:
1111)
at org.mobicents.slee.runtime.EventRouterImpl.access
$100(EventRouterImpl.java:64)
at org.mobicents.slee.runtime.EventRouterImpl
$EventExecutor.run(EventRouterImpl.java:121)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)

I can´t figure out why this occur, but following the code I was a
little concern about the timer "recycling". It cancels the timer, and
I don´t know what task are still awaiting execution or if they ever
gonna be executed.

I having a larger problem which involves running out of memory for
creating threads (even when having a lot of heap space), so I wanted
to se if this could be related.