no one can help me?
I'm so urgent for this question, thanks a lot
if you're doing a potentially long running transaction and you don't want the client to wait, i would choose a MDB instead of a stateless session bean. client posts message and is done.
though i would think that if a transaction timed out, the container should throw a remote exception possibly even a transactiontimeout excepiton?
btw, i created a simple slsb, and set the timeout to 2 seconds. the client (remote java app) did indeed just hang. a message was posted on the server that the transaction timed out.
thanks for you reply.
I know what 's your meaning.
so the result is ejb 's session bean doesn't support timeout ( although you can set transaction timeout , but as you just said, it has a long term bug in jboss).
but I found it so strange, why ejb couldn't support timeout on session bean's invocation? I estimate , at the lower layer of ejb implementation, session bean's invocation is actually implemented by tcp/ip
and this layer is in asyn mode, and ejb provide a sync mode encapsulation for this action, but why it could not support a timeout into this action?