This is an update to the issue previously reported by Mohit.
We were able to increase the heap size by removing the wrapper.java.initmemory and wrapper.java.maxmemory settings from wrapper.conf and instead used this: wrapper.java.additional.1=-d64 wrapper.java.additional.2=-server wrapper.java.additional.3=-Dcom.sun.management.jmxremote wrapper.java.additional.4=-Xmx16144m wrapper.java.additional.5=-Xms16144m The rest server still seems to be capping itself at 5 concurrent transactions though despite the larger heap. When hit with the full load of the client servers we observed that the both the PeakNumberOfConcurrentTransactions and NumberOfOpenTransactions attributes in the Transactions section of JMX remain exactly at 5. Under lesser load, the client servers rarely time out and the NumberOfOpenTransactions hovers between 0 and 2. Is there a way to explicitly increase the maximum number of concurrent transactions? As a side note, we initially explored the heap size after reading this: “Having a larger heap space will mean that Neo4j can handle larger transactions and more concurrent transactions” on the Neo4j wiki ( http://wiki.neo4j.org/content/Configuration_Settings) Thanks, Brock _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
