On 27 Jul 01, at 3:32, Ole Husgaard wrote:
> Hi,
>
> Strange, this should only happen if you are holding
> on to a Transaction reference, and that transaction
> was terminated (committed or rolled back).
Hi Ole,
This is certainly a possible defect in my application, but if this is
the cause, shouldn't the defect appear whether or not I had set the
optimize flag to true or false--or even whether or not the application
is called from the web tier or the client tier?
>
> 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.
I hope to have time to look into this tomorrow. Thanks for the hint
about the trace flag. That's a good idea.
>
> You are not trying to use UserTransaction in your
> web tier? I don't think that works, though it should
> not give this error.
No. I'm not a UserTransaction kind of guy. :-)
> Anyway, if your transaction is propagated with an
> optimized local call, where and how do you start it?
I'm not doing anything strange. The transaction should start at the
EJB tier with the interceptor, like normal. The web tier should be
just another client.
I haven't really looked into this yet. I was hoping someone would
go, "Oh, of course, it must be X," and save me a little work. I'll take
the trace flag, and Marc's suggestion of using a newer version, and
Dain's suggestion about where to look, and investigate this. I hope
tomorrow...
Thanks again, everyone.
-Dan
>
>
> 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
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
