Property for MAX_HEAP is always invalid
Opened this issue · 1 comments
FrankR85 commented
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 commented
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?