Aborting a Long-Running Call

Question

If I have a Java client process that makes a call to an EJB which in turn calls
a second EJB, and the second EJB takes a very long time, is there any way to kill
it? It seems from the testing that we done that: 1) if you kill the client process,
the EJB call continues to run; and 2) even if the transaction times out, the call
continues to run. In the latter case, once the call completes, the transaction
will roll back, because of the timeout, but in the meantime, the EJB continues
to run.
Thanks,
Dale

Answer 1

Ejbs do not know the state of the caller. So it continues to
run.
What kind of your second ejb is it? If it is a session bean,
maybe you can try:
1. when you get the second ejb, save it handler in a variable.
2. when the time out, call hander.remove().
Of course, you need to do it using thread on client.
From what you have described, it seems the most of the time
was spent in database (transaction still goes ..). If so,
there is nothing you can do before database finishes it job.
Ejb passes sql statement to database, database is completed
another independent program.
"Dale V. Georg" <[email protected]> wrote:
>
If I have a Java client process that makes a call to an EJB which in
turn calls
a second EJB, and the second EJB takes a very long time, is there any
way to kill
it? It seems from the testing that we done that: 1) if you kill the
client process,
the EJB call continues to run; and 2) even if the transaction times out,
the call
continues to run. In the latter case, once the call completes, the transaction
will roll back, because of the timeout, but in the meantime, the EJB
continues
to run.
Thanks,
Dale