Technology Stack - EBS (MOSC)

MOSC Banner

Disadvantages of having more oacore process and how it impacts the Garbage collection in EBS R12.1.

edited May 11, 2020 4:12PM in Technology Stack - EBS (MOSC) 8 commentsAnswered

we are running EBS R12.1.3 in AIX platform and we configured 20 OC4J oacore process with the java min and max heap size XmxXn 2048M and the server is having enough memory and cpu's to handle tisane we have the higher number of oacores and the Garbage collection takes longer time to release old unused connections and release the related memory.. so we regularly bounce the oacore process every nights to reduce the GC time and also at the same time reduce the OOM errors.

But still we see Java I/O exception  and servlets broken as below

  1. java.io.IOException: Broken pipe

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center