Java Heap Space Issue
Question:
Answer:
Investigation:
Flux has put fixes into the Datahub v.4. Now asking user to monitor it until 6th Feb
The memory already at 8194. This is not the issue.
Ask user to help increase the tomcat memory to 4092 as below:
Over weekend we had the issue in production, when we observed the logs we only found the java heap space issue - Datahub V4
Last time flux product team has enabled the logs to debug this issue more and those logs are still enabled. Could you please help assign some one to check this issue on priority.
When the Java Heap Space issue happens, it takes down Oracle SOA, which is complete integration outage, that’s P1 level issue, however, because restart Flux DH services will resolve the problem, so there is a workaround, so I’m also considering the issue as P2.
SOA also need to be reviewed, because it should not be this easily take down by a downstream connection.
Answer:
Investigation:
Replaced the tomcat configuration file server.xml file on the value MaxHeaderSize Parameter Tuning - reduce it from 200 m to 10 m.
Restart tomcat.
Flux has put fixes into the Datahub v.4. Now asking user to monitor it until 6th Feb
The memory already at 8194. This is not the issue.
Sending log files to Flux to investigate further.
Ask user to help increase the tomcat memory to 4092 as below:
DataImage84.png
| Files | ||
|---|---|---|
|
|
DataImage84.png
185 KB
|