If you run out of available connections, this means the client never closes them. Can you post your full code?
Il giorno lunedì 26 settembre 2016 08:37:38 UTC+2, Krishna Kant ha scritto: > > I am using 2.2.4 DB version and for orient Graph orientGraphVersion=2.2.8 is > my JAR dependency in code. > > On Monday, 26 September 2016 09:54:13 UTC+5:30, Oleksandr Gubchenko wrote: >> >> Which version are you using? >> >> Il giorno sabato 24 settembre 2016 15:30:10 UTC+2, Krishna Kant ha >> scritto: >>> >>> Hi All, >>> >>> I am setting up Orient DB master-master cluster environment and facing >>> below two issues: >>> 1)Maximum connection reached >>> 2)Concurrent modification exception while writing record. >>> >>> I am using Orient Graph factory with max 20 connection for my 4 client >>> apps. Also all the graph related call is surrounded by try and finally >>> having graph.shutdown(), so where connection is getting leaked? >>> >>> Another issue which I am observing is writing a vertex to class in >>> clustered environment. It hits OConcurrentModificationException and once I >>> try to print the IDs I saw the record got started with #60:0 and while >>> commit during graph.shutdown() it has id as #60:1. I do not have any >>> concurrent thread running. So is DB sync up can modify the record id. >>> >>> Same write record once i tried using single node it worked fine. >>> >> -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
