> From: emailnbw_at_gmail.com
> Subject: EJB TX attr and Glassfish conn pool question
> Date: Fri, 14 Feb 2014 11:44:14 -0500
> To: users_at_glassfish.java.net
>
> I’m deploying to a Glassfish 3.1.2.2 environment which has a JDBC connection pool used by the application. The JDBC connection pool has a checkbox (off by default) called, “Non-Transactional Connections”.
>
> Can anyone shed some light on the relationship of this setting and TransactionAttributeType.NOT_SUPPORTED?
>
> My application’s persistence.xml defines a JTA datasource that points to a JDBC resource associated w/a JDBC connection pool. If an EJB in the application has a method annotated with @TransactionAttribute(TransactionAttributeType.NotSupported) will it still be non-transactional
MG>Yes for the duration of the annotated method
MG>check out the definition @ MG>
http://docs.oracle.com/javaee/6/api/javax/ejb/TransactionAttributeType.html#NOT_SUPPORTED
MG>The container invokes an enterprise bean method whose transaction attribute NOT_SUPPORTED with an unspecified transaction context.
If a client calls with a transaction context, the container suspends the association of the transaction context with the current thread before invoking the enterprise bean's business method. The container resumes the suspended association when the business method has completed.
MG>
even if the checkbox for “Non-Transactional Connections” is left in its default state of unchecked?
> TIA,
>
> -Noah
>