Option 2 is a system side setting which you might not control. Option 3 will only work if you write the clients.
Regards, Adrian xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Director of Support Back Office JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx -----Original Message----- From: Craig Berry [mailto:[EMAIL PROTECTED] On Behalf Of Craig Berry Sent: 31 May 2003 04:21 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Per-method CMT timeout control? Thank you. I'm sorry there's not a more direct way, but also glad that I'm not completely clueless. :) Why wouldn't my options 2 and 3 be portable, by the way? (Allowing for use of appropriate default-timeout setting mechanism per app server in option 2, of course.) I'm especially curious about option 3. -----Original Message----- From: Adrian Brock [mailto:[EMAIL PROTECTED] Sent: Fri 5/30/2003 5:21 PM To: [EMAIL PROTECTED] Cc: Subject: RE: [JBoss-user] Per-method CMT timeout control? The javax.transaction.Transaction interface unlike javax.transaction.UserTransaction doesn't allow a timeout to be set. The only portable mechanism is to use a BMT fa�ade (option 1). If you want it declarative, bind the timeout value into java:comp/env as an env-entry. xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Director of Support Back Office JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Craig Berry > Sent: 31 May 2003 00:15 > To: [EMAIL PROTECTED] > Subject: [JBoss-user] Per-method CMT timeout control? > > > Our app uses a variety of session and entity beans operating under > container-managed transactions. For most of these, the default > transaction timeout value set in transaction-service.xml is > fine, but a > few methods are expected to run much longer than that. So > far, the only > solutions I've found to this problem are: > > 1. Run those methods without CMT > 2. Increase the transaction-service.xml timeout value to accommodate > these methods > 3. Start a client-side UserTransaction before calling these > methods, and > set its timeout to be high enough > > Obviously, none of these are especially attractive. What I'd really > like is a declarative way (presumably in ejb-jar.xml) to override the > default CMT timeout for specific bean methods. This seems like > something that should naturally be there, but I can't find > any trace of > such a capability in the docs or through a web search. > > Am I missing something, or do I have to fall back on my three > suboptimal > choices above? > > -- > Craig Berry > Principal Architect and Technical Manager > PortBlue > (310) 566-7546 > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
