Receivables AutoReconciliation Execution Report Fails with Error 'JVMCI161: FATAL ERROR in native method: Wrong method ID used to invoke a Java method' (Doc ID 2104761.1)

Last updated on AUGUST 25, 2017

Applies to:

Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

E-Business Suite 12.1.3, Receivables GL Posting Report


The AutoReconciliation Execution Report end in error when the output is larger than 2GB.

For example:

CEXINERR module: AutoReconciliation Execution Report
..
emsg:was terminated by signal 6
Enter Password:
JVMCI161: FATAL ERROR in native method: Wrong method ID used to invoke a Java method
at oracle.reports.engine.EngineImpl.CRunReport(Native Method)
at oracle.reports.engine.EngineImpl.run(EngineImpl.java:441)
at oracle.reports.server.JobManager.runJobInEngine(JobManager.java:975)
at oracle.reports.server.ExecAsynchJobThread.run(ExecAsynchJobThread.java:54)

Report Builder: Release 10.1.2.3.0 - Production on Wed Jan 13 20:14:11 2016
...
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /ora_apps/poa/apps/conc/log/javacore1822736.1452737923.txt
JVMDG215: Dump Handler has Processed Error Signal 6.

BUSINESS IMPACT
-----------------------
Users cannot run the report when the output is greater than 2GB.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms