|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...
get a repro case. It will take you minutes.
marcf
|
|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
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
