We are running UV11.3.1 ( Pick Format ) on AIX 7200-05-08-2420
Yesterday, we started getting reports from the call centers about user's sessions freezing up. Normally, our first thought when this happens is a record lock of some kind.
If we tried to log into the application, we got to the login prompt and were able to authenticate. But once we successfully entered our userid/password to get into the application the session would hang.
We create thousands of uniobjects connections to the DB throughout the day from our web sites and IVR, and these were timing out.
Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.[IBM U2][UODOTNET - UNIRPC][ErrorCode=81009] The RPC failed
UniVerse itself was running fine. I could start new sessions and as long as I stayed on the UV account ( bypassing the application login process ), I could move around the system, do TCL queries, etc…
When I did a LIST.READU EVERY, the system showed no waiters. So it didn't seem to be a situation where everyone was backed up waiting for a specific record to be released.
We went to the UV account ( logged in as root ) and did an UNLOCK ALL, an UNLOCK GROUPLOCK ALL, pretty much every UNLOCK combination that we could think of. This did not release the hung sessions.
I'm not sure if this is related, but I also saw record locks on device 0, inode 0.
Ultimately, we resorted to stopping and restarting UniVerse to free things up and allow the users to resume their normal work.
We encountered a similar, if not the exact same scenario, once previously.
I'm wondering if anyone else has ever run into this? Also wondering if there are other things either in UniVerse or at the Unix level that we might have tried before resorting to the restart.
------------------------------
Anthony Pontecorvo
------------------------------