[EMAIL PROTECTED] penned > I have this item in a try catch block and I was hoping it would throw > an exception after 5 seconds, then I could carry on what I am doing.
Do you mean that you call the transactional bean method from within a try-catch hoping an exception would be thrown by the bean wrapper? That makes sense, but ... > But it does not. It still waits 30 seconds every time before > returning. 30 seconds is just too long. This makes it sound like WL *is* aborting the thread and throwing an exception at 30 seconds, but it's merely ignoring your transaction timeout of 5 seconds. I still don't see how that's possible (aborting the thread since the JVM doesn't support that). Is it possible that the transaction is completing in 30 seconds, and thus the transaction is not actually timing out. Rather, WL is ignoring your timeout value of 5 in favor of its default of 30. So, have you verified that XDoclet is putting the timeout value in the correct place in the deployment descriptor? -- David Harkness Sony Pictures Digital Sr. Software Engineer 310.482.4756 [EMAIL PROTECTED] A "No" uttered from deepest conviction is better and greater than a "Yes" merely uttered to please, or what is worse, to avoid trouble. -- Mahatma Ghandi ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
