Hi,
Strange, this should only happen if you are holding
on to a Transaction reference, and that transaction
was terminated (committed or rolled back).
For more information about what is going on in the
default TM, change the trace flag near the top of
org.jboss.tm.TxCapsule to true, and recompile.
You are not trying to use UserTransaction in your
web tier? I don't think that works, though it should
not give this error.
Anyway, if your transaction is propagated with an
optimized local call, where and how do you start it?
Best Regards,
Ole Husgaard.
Dan OConnor wrote:
>
> Hi guys,
>
> I was hoping someone would know where this bug would be as
> soon as I described the symptoms.
>
> A bean-managed entity registers a synchronization object with a
> transaction. If it is called from a web-tier client with optimizations
> turned on, it fails like this:
>
> java.lang.IllegalStateException: No transaction.
> at
> org.jboss.tm.TransactionImpl.registerSynchronization(TransactionIm
> pl.java:135)
>
> If this method is called from a remote client, it always works. If it is
> called from a web-tier client with optimizations turned off, this
> always works. (The transaction attribute of the business method is
> Required.)
>
> Anyone know the answer?
>
> -Dan
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
