Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/exist/xmlrpc: An unknown error occurred: GC overhead limit exceeded - Errors observed for ExistDB and Exist DB is getting corrupted on regular basis #2754

Open
sbhusala opened this issue May 27, 2019 · 8 comments
Labels
awaiting-response requires additional information from submitter investigate issues being looked at

Comments

@sbhusala
Copy link

What is the problem

/exist/xmlrpc: An unknown error occurred: GC overhead limit exceeded - Errors observed for ExistDB and Exist DB is getting corrupted on regular basis

What did you expect

Describe what you expected to happen. Add for example a reference to a specification.

Describe how to reproduce or add a test

Describe how we can can reproduce the problem.

Context information

Please always add the following information

  • eXist-db version + Git Revision hash e.g. eXist-db 3.0 / acd0c14
  • Java version (e.g. Java8u121)
  • Operating system (Windows 7, Linux, MacOs)
  • 32 or 64 bit
  • How is eXist-db installed? (JAR installer, DMG, WAR file, clone from GitHub)
  • Any custom changes in e.g. conf.xml
    image
@triage-new-issues triage-new-issues bot added the triage issue needs to be investigated label May 27, 2019
@adamretter
Copy link
Member

Hey @sbhusala this is a memory related problem. Many memory issues have been fixed since eXist-db 3.0.0, could you please try 4.7.0?

@dizzzz
Copy link
Member

dizzzz commented May 29, 2019

additionally, you could try to switch on the G1 garbage collector. but v4.7 is for sure the best step.

@duncdrum duncdrum added the awaiting-response requires additional information from submitter label Jun 13, 2019
@triage-new-issues triage-new-issues bot removed the triage issue needs to be investigated label Jun 13, 2019
@adamretter
Copy link
Member

Closing due to inactivity.

@sbhusala
Copy link
Author

Dear All,

We have upgraded to 4.7 eXst db version, however we are still receiving GC overhead limit exceeded error. can you please suggest on next steps ?

@duncdrum duncdrum reopened this Jan 15, 2020
@duncdrum
Copy link
Contributor

duncdrum commented Jan 15, 2020

Is there any steps that you can take to reproduce this? If the error occurs on exist v5 please include new info on java version install method and conf.xml changes etc

Can you share a log file?

@sbhusala
Copy link
Author

Hi Duncan,

Replication of issue cannot be feasible manually , however it might be because of heavy load ? ( suspect).

java :
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

project.version=4.7.0
project.built=201905201236
scm.branch=refs/tags/eXist-4.7.0
scm.revision=64ba5134

@sbhusala
Copy link
Author

exist.log
Attached logs as requeste
d.

@duncdrum duncdrum added the investigate issues being looked at label Jan 15, 2020
@dizzzz
Copy link
Member

dizzzz commented Jan 16, 2020

for me, in some cases enabling the G1C garbage collector helped a lot....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-response requires additional information from submitter investigate issues being looked at
Projects
None yet
Development

No branches or pull requests

4 participants