Agneeswaran, I'm a little confused here, as you are telling you used the same test for the 1.5.0 and for the 1.6, but for the 1.5.0 you didn't use ODBC and for the 1.6 you do. How could this be possible? Have you modified your test to use ODBC on 1.6?
Do you use the same ODBC connection concurrently or do you open new connection for every thread? Regarding core dumps, if you are using bash, try this command prior to starting your program: ulimit -c unlimited With this your program should start generate core dumps on crash. Best Regards, Igor On Tue, Jul 12, 2016 at 4:35 PM, Agneeswaran < [email protected]> wrote: > Hi Igor, > > Yes, this test is executed with ignite 1.5.0 release version without ODBC. > > I could see there is no code dump files generated in our executable path. > > Could you please suggest the configuration which you need for test. > > We are using our client project for testing this scenario. > > Thanks in advance, > > With regards, > Agneeswaran > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6232.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
