anonymous wrote : | Moderated: It is an FAQ on the WIKI | (at http://www.jboss.org/wiki/Wiki.jsp?page=IGetInterruptedWhileRequestPermit&version=1), I assume). But that answer implies that a "well-designed application" should do something else than the "interrupted()" trick mentioned below. What is this "something else"? (If there is something on the Wiki, I'm sorry to have asked - I looked around, but did not find anything):
| 1. Make JBoss transaction timeouts very long? ... but this is (a) just a "statistical solution"; and (b) will backfire because then someone will write even longer transactions (usually the too long TXs are from batch runs). | | 2. Do retries - seems the right thing to do?!? Is there any code pattern/idiom around how to do this - or am I asking for the trivial now? (I dont think so, as it seems one needs "RequiresNew wrapper methods" in case the outermost transaction times out - which is usually a nuisance because client applications have to change) | | 3. ??? | | | I (more or less) happily accept any punishment that I didn't find the answers in the Wiki, the mailing archive, doc, or the source myself ;-) | | Regards | Harald M. Mueller View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867232#3867232 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867232 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
