Last Modified: Oct 06, 2020
See more info
Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1
11.5.0, 11.4.1 HF9
Opened: Oct 28, 2013
What happened was, on requesting a resource, EAM will verify if a requested resource is protected by OAM server through the Oracle ASDK API, and an OAM exception occurred (Error 310 )due to internal server issues. This error was not caught and handled properly in EAMTEST. Later, when another Oracle ASDK API is called for checking if the resource is protected again, it may throw another exception, which causes eam plugin to be terminated.
eamtest tool cored
Internal server issues or connectivity issues caused OAM SDK to throw an exception and this was not handled properly in eamtest tool.
no workaround for eamtest to complete successfully.
If APM attempts to verify whether a resource is protected when a connectivity failure to the OAM server occurs, APM handles the failure gracefully.