On 16/Feb/2010, at 12:13 PM, Amedeo Mantica wrote: > no, is inside the R-R Loop
Hey Amedeo! I would set a breakpoint on the setTimeOut() method and see when the timeout is being set! Using jdb, this would be something like: path/to/woa -NSJavaDebugging YES > stop in com.webobjects.appserver.WOSession.setTimeOut > run > ... Breakpoint hit: "thread=WorkerThread0", com.webobjects.appserver.WOSession.setTimeOut(), line=678 bci=0 > where [1] com.webobjects.appserver.WOSession.setTimeOut (WOSession.java:678) [2] com.webobjects.appserver.WOSession.<init> (WOSession.java:233) ... > cont Repeat until you find the case where the timeOut is getting set. ;-) Note that the first time is the WOSession constructor setting the initial value. It's the times after that are most interesting! M. P.S. I'm open to learning how to do this in Eclipse however my understand is that Eclipse can't set break points when it doesn't have the source code. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
