Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4
11.6.0, 11.5.1 HF5, 11.4.1 HF6, 11.4.0 HF8
Opened: May 06, 2014
Related AskF5 Article: K16791
On the EAM Client side handler while processing TMEVT_INGRESS, ObAccessException is sent from the Oracle Access Manager (OAM).
EAM process cores and restarts. This exception is thrown in very rare instances, and in those cases, the unhandled exception causes the EAM plugin to core. The EAM process is restarted, and then handles user requests.
The exact conditions required to reproduce the error are unknown. However, in rare instances, the OAM SDK throws the ObAccessException while checking whether the requested resource is protected by accessgate.
Additional exception processing (for ObAccessException from the Oracle Access Manager (OAM)) was added to the EAM module. The module now handles this exception by displaying an error.