Valid actions to prevent "Waiting for in-flux to clear"
pstgliaFeb 6 2010 — edited Oct 25 2011Hi all,
In our application we use to do heavy processing with some connections to Timesten instance (about 20).
Sometimes, we got this in-flux message on syslog:
<wait not in flux> Waiting for in-flux to clear (now reason 2=connect pid 14515 nwaiters 87 count 597
ds /tt02/ttvl2/timesten/RT_02/ds/mta4350_64_02)
While these messages are printed on syslog, we're unable to create new connections to this instance. Normally we rename this instance entry on ODBC.ini to avoid new connections and wait until there's no in-flux messages with a so high value of nwaiters. This may take several hours...
What is the real meaning of this message? Perhaps some bootleneck or invalid configuration...
And what is the actions we can adopt to avoid this?
Thanks in advance,