[
http://mifosforge.jira.com/browse/MIFOS-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58100#action_58100
]
jbrewster commented on MIFOS-2970:
----------------------------------
Raghav, thanks for running those scenarios, this was very helpful.
Based on that information and conversation with Keith, going to change this to
an improvement and change release target. Seems unlikely actual users will
encounter many lock errors on the same group as a load test does.
[10:16] <jbrewster> keithw_: hi keith, question on issue MIFOS-2970. Can
you help me understand why the LockAcquisitionException only started showing up
on the head? Is 'max_child_count' new to Mifos?
[10:21] <keithw_> jbrewster: max_child_count has always been there. its
is used when generating search_id for customers. since the refactoring we now
have customer creation services that are 'atomic', previously this was not the
case so i believe this wasnt showing before. so when we create new client, we
must update its parents max_child_count to keep search_id creation someway
sane, this used to happen...
[10:21] <keithw_> ...before but (although might not of in places)
[10:22] <keithw_> jbrewster: so if clients are created concurrently under
the same parent, its likely that a 'lock' can occur if a previous transaction
hasn't finished
[10:26] <jbrewster> keithw_: ok, thanks. and in this case under the same
parent means under the same center. (as opposed to group) If a MFI had turned
off centers, then in theory the same issue would occur if concurrent clients
were created in the same group and transactions hadn't finished?
[10:28] <keithw_> jbrewster: in a center->group-> hierarchy, when
creating clients, the group max_child_count is update so lock should happen
there and possibly on center if something is updated there also, in
group->client heirarchy, the same thing is true for groups
[10:35] <jbrewster> keithw_: ok, thanks. I'm ok with making this an
improvement. Instead of closing/creating a new issue I'm going to convert the
existing issue since it's got context. I'll also modify the summary
> LockAcquisitionException - Comes while creating clients
> -------------------------------------------------------
>
> Key: MIFOS-2970
> URL: http://mifosforge.jira.com/browse/MIFOS-2970
> Project: mifos
> Issue Type: Bug
> Reporter: Raghavendra Bhandari
> Assignee: Raghavendra Bhandari
> Priority: Major
> Fix For: Shamim D
>
> Attachments: ClientCreationBug.txt,
> ClientCreationBug_Head_Master1342.txt
>
>
> Hello,
> While creating the clients using Jmeter, i got the exception called
> org.hibernate.exception.LockAcquisitionException.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
