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
