I should probably also mention that implementing a timeout to this backend
systems is not possible (at least I don't know how), as it is a RMI call to a
weblogic server...
As far as I know, no client timeouts can be set for RMI calls, and the version
of weblogic that the server runs doesn't sup
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=viewtopi
First off, I know that there are several related topics to this (i've done
plenty of searching), however I haven't found an answer yet that's satisfying.
We have two different systems in production, one of which on JBoss 3.2.3 and
the other on 3.2.5. Both use stateless session beans.
The issue
