Hi,
I have deployed mifos-x on my centos local machine. Using jmeter when i
fire concurrent users (10 users), I am seeing failure with logs as shown
below.
If i hit the https://demo.openmf.org server with jmeter I do not get that
deadlock issue.
Is I am my missing some setting for tomcat or mysq
Hi everyone,
This meeting should be attended by users and developers alike who want to
learn where the product is headed in 2014 and how you can contribute to
that development effort as well.
We'll be going over the community process and the current 2014 roadmap with
a focus on the first two quar
Hi Neeraj,
That is great to know that you trying for load testing.
One quick things look at is max_connection value of mysql.
Also refer https://mifosforge.jira.com/browse/MIFOSX-949, may help you
understand issue better.
few more question, when you hit demo server how did you know that there
we
Hi Nayan,
Thanks for the reply.
max_connection of mysql is currently 151 set.
Event with concurrent 2 users, 1 transaction get failed with mysql deadlock.
In the jmeter response I can see the json response of success cases and
exception log with error 500 for failure cases.
I am posting on mif
Hi Neeraj,
We have logged similar issue in JIRA
https://mifosforge.jira.com/browse/MIFOSX-968.
But not at this volume, this was for some where around 1000+ concurrent
users and for collection sheet and each collection sheet was equivalent to
40 repayments so concurrency was 40k repayments.
Try l
Thank you to all who attend today's product roadmap webinar. Apologies for
the confusion in time due to my scheduling in both PST and GMT creating a
conflict.
For those who weren't able to attend, we've recorded a screencast and
uploaded the presentation
You can find everything at this link -
htt
Hi Nayan,
We are evaluating the mifos-x for performance.
The mysql deadlock logs are here which I got from show engine innodb status;
LATEST DETECTED DEADLOCK
2014-03-14 10:59:41 7ffcdf10f700
*** (1) TRANSACTION:
TRANSACTION 27230, ACTIVE 2 sec
