My Oracle Support Banner

OPSS - Auditing on OAM Domain Stops with IAU:IAU-5046: Stopping AuditLoader, caught exception: java.lang.NegativeArraySizeException (Doc ID 2379221.1)

Last updated on DECEMBER 22, 2023

Applies to:

Oracle Platform Security for Java - Version 11.1.1.9.0 and later
Information in this document applies to any platform.

Symptoms

After Configure Audit on OAM domain, Audit load stops working, seeing the following error:

<Feb 20, 2018 11:03:09 AM EST> <Warning> <oracle.ods.virtualization> <BEA-000000> <You must use SSL port for this adapter or configure ssladapter with an adapter which uses SSL port.>
<Feb 20, 2018 11:03:09 AM EST> <Error> <Default> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
<Feb 20, 2018 11:03:09 AM EST> <Warning> <oracle.oam.agent-default> <OAMAGENT-00410> <OAM Server can not be accessed, fallback to container policy: fetchConfig failed, will keep trying ...>
<Feb 20, 2018 11:03:11 AM EST> <Error> <Default> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
<Feb 20, 2018 11:03:13 AM EST> <Error> <Default> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
<Feb 20, 2018 11:03:13 AM EST> <Error> <Default> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
<Feb 20, 2018 11:03:13 AM EST> <Warning> <oracle.oam.controller> <OAM-02074> <Error while checking if the resource null is protected or not.>
<Feb 20, 2018 11:03:13 AM EST> <Warning> <oracle.oam.binding> <BEA-000000> <OAM-02073>
<Feb 20, 2018 11:03:14 AM EST> <Error> <Default> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
<Feb 20, 2018 11:03:14 AM EST> <Error> <oracle.security.audit.logger> <BEA-000000> <IAU:IAU-5046: Stopping AuditLoader, caught exception: java.lang.NegativeArraySizeException
at oracle.security.audit.ajl.reader.FileSetLogReader.readRecordFromOneFile(FileSetLogReader.java:303)
at oracle.security.audit.ajl.reader.FileSetLogReader.readNextRecordAsBytes(FileSetLogReader.java:898)
at oracle.security.audit.ajl.reader.FileSetLogReader.read(FileSetLogReader.java:999)
at oracle.security.audit.ajl.loader.AuditLoader$SingleLookaheadBusStopLogReader.gotoNextRecord(AuditLoader.java:373)
at oracle.security.audit.ajl.loader.AuditLoader.readMessages(AuditLoader.java:482)
at oracle.security.audit.service.AuditLoaderManager.readMessages(AuditLoaderManager.java:324)
at oracle.security.audit.service.AuditLoaderManager$Runner.run(AuditLoaderManager.java:410)
>
<Feb 20, 2018 11:03:15 AM EST> <Error> <Default> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
<Feb 20, 2018 11:03:15 AM EST> <Error> <Default> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>
<Feb 20, 2018 11:03:15 AM EST> <Error> <Default> <BEA-000000> <Failed to communicate with any of configured Access Server, ensure that it is up and running.>

 

Another potential OAM diagnostic log error can be:

 

Changes

 

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


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