Thanks Adrian Crum, Scott.
Yes, we are refactoring the GlAccountOrganization related services.
With regards,
Pradeep Kumar
With regards,
S K Pradeep Kumar,
9035009495
On Mon, May 19, 2014 at 6:44 PM, Scott Gray scott.g...@hotwaxmedia.comwrote:
GlAccountOrganization looks like it could be
GlAccountOrganization looks like it could be contentious for locks due to the
postedBalance field (lots of separate long running transactions trying to
update multiple rows at the same time). The service updating it probably needs
refactoring so that the update is moved to a smaller
Deadlock issues are hard to reproduce because they are usually timing
dependent. If your issue is easily reproducible, then most likely it is
caused by an action (SECA) trying to change data that is being iterated
over by another action (the service invoking the SECA).
Look through the stack
Hi All,
What might be the possible reason for this issue :
This issue starts only when we have the separate servers for Database and
Application. but this issue is not coming on the single server.
We have deployed the application on Amazon EC2 servers.
Application is deployed on : EC2 Medium
