Last updated on MAY 24, 2017
Applies to:Oracle WebLogic Server - Version 18.104.22.168 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:
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms