RTD-10243: Decision Service session timed out but timer task could not acquire session's run lock. S

Pierre Lautrou

Hi all,

We are using Oracle Real-Time Decisions 3.2 and on our preproduction environment we are seeing recurring "Decision Service session timed out but timer task could not acquire session's run lock. Session ID={0}" messages in the Decision Service logs when soliciting the system at 20 requests per second.

We don't have these messages on our other environments.

I only found the following information regarding these messages in the Oracle documentation (RTD-10001 to RTD-10532) :

RTD-10243: Decision Service session timed out but timer task could not acquire session's run lock. Session ID={0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Programmatic

It does not give detail about the cause or the impact of these messages.

Has anyone come across these messages before?

Any idea what causes these messages and what are the impacts?