I would not have thought this would be such an uncommon and/or complicated problem. I don't really see how jndi/rmi calls could be practical at the enterprise level without the ability to set a timeout.
Agreed! I've got pretty much exactly the same problem and I thought as well that this would be a fairly common problem. Apparently not so. I tried to approach it from a different side (see my post about transaction timeout behaviour: [URL]http://www.jboss.org/index.html?module=bb&op=viewtopic&t=61726[/URL]), to see if there's anything we can do in JBoss when the transaction times out.
Jboss currently only marks the transaction as rollback. It would be much more usefull if it would actually perform the rollback and as a result release all the resources and terminate the RMI call.
So far I haven't found anything useful, but if I do I'll certainly share it...
I thought this would be easy, but was disappointed when I searched the forum. Is there no solution for this? What do other people do? Use a different invoker? Write their own invokers?