Timer EJB throws javax.ejb.EJBAccessException: User <anonymous> has insufficient permission to access EJB type
(Doc ID 2217725.1)
Last updated on JUNE 14, 2024
Applies to:
Oracle WebLogic Server - Version 12.2.1.1.0 and laterInformation in this document applies to any platform.
Symptoms
Deploying a EJB with Timer Annotation and setting the global Root Level Policy for EJB to Specific Role, the timer stops working and throws the below exception.
Setting option to "Allow access to everyone" works fine.
When using custom roles and policies and setting permission rule for all EJBs and Timer EJB, this problem occurs.
TimerEJB is also checked for permission. As TimerEJB is run by anonymous, fails to check permission.
Timeout callback should not be checked permission because it does not have client security context
Changes
When using custom roles and policies and setting permission rule for all EJBs and Timer EJB, this problem occurs.
TimerEJB is also checked for permission. As TimerEJB is run by anonymous, fails to check permission.
Timeout callback should not be checked permission because it does not have client security context
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |