Follow up: It turns out, if I leave 'them' alone..... i.e. Don't run PORT.STATUS, everything is fine.
It's as though PORT.STATUS triggers some kind of clean up. I can live with that..... But if anyone can give some insight into what PORT.STATUS may be doing behind the scenes I'd be curious to hear about it. Thanks, Mark. -----Original Message----- From: Daly, Mark Sent: Tuesday, April 13, 2004 5:37 PM To: 'U2 Users Discussion List' Subject: UOJ - UniSession Timeout We are running UV 9.4. And I am hoping that is the cause of my problem.... I have developed a connection pooling mechanism for our Java apps. Pretty standard stuff (java wise). Just a bunch of UniSession objects in a Stack. When the application fires up, it logs in 10 sessions and pushes them on the stack. The problem I'm seeing is that after less than 30 seconds they all 'expire'. I've tried using the UniSession setTimeout() method. But it doesn't seem to have any effect. Has any one else experienced anything like this. It may well be that I'm on 9.4, and a lot has changed with the RPC side of things. Any pointers would be greatly appreciated. Mark. -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
