There are still some "known issues" with ASF.
* It does the transaction begin/commit so any changes in TxInterceptorCMT
for other EJBs are usually not reflected here. Although the semantics are different.
* There is the outstanding issue of WSMQ XA where we use the xa session
when for WSMQ it should be the plain session, e.g.
/**
* Runs in an own thread, basically calls the session.run(), it is up to the
* session to have been filled with messages and it will run against the
* listener set in StdServerSessionPool. When it has send all its messages it
* returns.
*/
public void run()
{
boolean trace = log.isTraceEnabled();
if (trace)
log.trace("running...");
try
{
if (xaSession != null)
xaSession.run();
else
session.run();
}
finally
{
if (trace)
log.trace("recycling...");
recycle();
if (trace)
log.trace("finished run");
}
}
This isn't documentated in the spec. At least for JBossMQ it makes no
difference, since they are the same object.
