It asks the transcation manager if there is
a transaction still active on the thread.
If there is you get an error, you should commit()
Only Stateful BMT can exit a method with a transaction
Well I am using my own trasaction into a database (BMP) that JBoss would not have idea of. I was starting and closing the transaction over mutliple calls to a Stateless Session Bean. How did JBoss figure that out that Stateless Session Bean is not the right vehicle ?
Sorry, Adrian your explanation too cryptic and not too useful. I'm getting the same errors, intermittently. There was another post that say this is
a well known error with Jboss, but no solution was provided. So what is
the solution? With EJB spec, I believe it is perfectly legal to
a. use a BMP stateless bean to get a user transaction, then call
b. a CMP stateless bean to do the work. Of course in the
CMP it has to get a connection (which is under the Tx transactioin
obtained under the BMP earlier
c. the CMP does the work, then close the connection
d. the BMP then commit()
However, then we get ths BMP must commit before return (though
the error is actually that the commit was not allowed for some
reason by jboss).
Some points on this:
why does this problem only shows up intermittently? if JBOss does not
support the sequence a-d it should fail EVERYTIME, but that's not the
We don't see ANY such problem with Weblogic.
thanks for any replies!
Don't you think that you are being rather rude Sorry, Adrian your explanation too cryptic and not too useful., digging up a post that is over a year old and saying that it is not useful.
There was another post that say this is
a well known error with Jboss, - Where, you forgot to add the link.