I'm pretty sure this has been discussed before, but I'm in somewhat of a quandary: my service would like a reasonably large timeout value, but this means that if it /does/ go wrong, then whatever value I pick is multiplied thrice, since a method timeout doesn't cause immediate maintenance.
In my case I'd ideally like to give up straight after my first timeout. I couldn't find a bug/RFE on this, although there was a related one about a global timeout on system shutdown. regards john
