On Behalf Of Daly, Mark > I've tried using the UniSession setTimeout() method. But it > doesn't seem to have any effect.
Dave Meeks posted in April'02 suggesting setTimeout(), so I assume it was working then. No telling whether IBM broke it after that, though! Have you tested it outside your webapp? Check, and possibly increase, the timeout in the /usr/unishared/unirpc/unirpcservices file. http://www.indexinfocus.com/dl/u2list/200204/29998.html http://www.indexinfocus.com/dl/u2list/200110/21548.html What about trying the latest and greatest UOJ code, I don't *think* there were enough changes to cause the newest version to not work against an old version of U2. It comes with the Personal Edition if you don't have a newer version of U2 around. I discarded connection pooling very early on in favor of a simple Factory class. It's just not that hard to create a new session compared with all the trouble of keeping them alive and hanging around. So I'd take a hard look at whether connection pooling really is worth it for your app. (See http://www.pickwiki.com for UniSessionFactory.) -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
