EJB timer itself because it's persistent by definition, is implemented as an EJB
with persistent support (CMP prior to v3, and as a SLSB with JPA backing in v3).
So this explains the transaction appearance in your test.
But how does it affect the rest of your app? EJB timer bean accesses its own
(XA) database, if you didn't change anything.
thanks,
-marina
glassfish_at_javadesktop.org wrote:
> Ok, the problem appears to be related to the execution from the ejb timer. If I execute by making the ejb call directly from a client app the call is not in a transaction and the web service call succeeds. When it is called from the timer it fails.
>
> I have marked all the methods in my timer and ejb with the TransactionAttributeType.NOT_SUPPORTED but it still seems to put it in a transaction and the web service call fails with the WSTX error.
>
> Is there any way to force the timer to not use a transaction?
> [Message sent by forum member 'abll' (jodendahl_at_tandbergtv.com)]
>
> http://forums.java.net/jive/thread.jspa?messageID=367677
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>