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

Property for MAX_HEAP is always invalid #281

Open
FrankR85 opened this issue Nov 13, 2020 · 1 comment
Open

Property for MAX_HEAP is always invalid #281

FrankR85 opened this issue Nov 13, 2020 · 1 comment
Assignees

Comments

@FrankR85
Copy link

Expected behavior: dbms.memory.heap.max_size=31g in neo4j.conf sets the maximum heap size.

Actual behavior:

FROM neo4j:4.1.1
COPY neo4j.conf /var/lib/neo4j/conf/neo4j.conf

results in an error when starting the image:

Starting Neo4j.
Invalid maximum heap size: -Xmx31g
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

The same situation is with initial heap size. No matter what exact value is given.

@jennyowen
Copy link
Member

Sorry for the delay in replying. I tried reproducing this from your code but I didn't get the error.
I was using a conf file that only contains the line dbms.memory.heap.max_size=10g. If you try the same does it still give you an error about max heap size?

@jennyowen jennyowen self-assigned this Dec 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants