If it is a session hang you're possibly looking at locking issues so check
the lock table to see what is waiting and also check for any group locks
that persist.
If it is UniVerse, It's also a good idea to check the errlog file in the uv
account: if that does not exist, create it as a zero length
I will chime in since I work with Ravi and I am dealing with this issue
along with him.
Thanks for the response Brian, PORT.STATUS should be useful for our
situation.
I'll try and be a little more specific and hopefully I know what I'm
talking about: We have a web application which is using
Andy:
The first place I'd look for any UO errors is the UO error log. In UD,
you need to create a serverdebug item in the @UDTHOME directory (in my
case this is in E:\U2\ud). The contents of this item is:
udcs 10 E:\U2\ud\log\udcs\udcs.log
...which indicates maximum logging and the log
Good point. I would start by checking the health of the uvdlockd
process. We had an issue a few years ago where a misbehaving JDBC
client application would cause a lot of work for the uvdlockd process.
Eventually the uvdlockd.log file in the uv home directory hit 2GB in
size and uvdlockd stopped
