My Oracle Support Banner

WLS12.1.1 : Fails To Identify Invalid EJB Transaction-attribute (Doc ID 1619299.1)

Last updated on OCTOBER 01, 2020

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


With an EJB Timer deployed and an a transaction-attribute of "Never", which is not supported for EJB Timers. Per the API:

"For an enterprise bean's timeout callback methods, only the REQUIRED, REQUIRES_NEW and NOT_SUPPORTED values may be used. "

However, updating the transaction attribute to Never still allowed the deployment to succeed. This deployment should have failed.
As a workaround, one can stop all servers in domain, delete all cached files, start the servers, and then redeploy the Timer with the transaction attribute set to Never.  Then deployment fails, as expected.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.