--- Comment #1 from Kyle M Hall <> ---
Created attachment 72481
Bug 20342: Fix table locking issue, progress bar not updating, and allow use of
plack for Stage MARC Import

Have you ever seen this error?
DBD::mysql::st execute failed: Deadlock found when trying to get lock; try
restarting transaction [for Statement "INSERT INTO import_record_matches
(import_record_id, candidate_match_id, score),

Have you ever noticed your progress bar during stage for import jumps from 0%
to 100% with no updates in between?

Would you like to work under plack?

If you answered yes to any of the following questions, this bug is for you!

During uploads of large records using matching rules, we were getting 'Failed
to submit form' popups on the marc record importer.

First, I noticed that the parent process of wasn't
returning the job id via ajax until the child process had completed. This works
fine for smaller files as they process fast. For large files ( and in
particular when using matching rules ) the process takes *much* longer.

It appears that $.ajax will resubmit the form if it doesn't get a response back
in a given time ( I would estimate that to be about 30 seconds or so ). This
causes a *second* instance of to be run. So now we have
two processes both running transactions on the same table for the same batch
id. I believe this is what is causing the Deadlock.

So, the crux of the matter is that for whatever reason, the parent process will
not output until the child process has gone away. Hours of research entailed.
The final answer is that the child process must be detached from the parent
process. I tried doing this via setsid() but it did not help. Finally, I found
that using Net::Server::Daemonize did!

After I had my solution, I decided to see if and could now be run under plack, and it appears that
they can!

Test Plan:
1) Apply this patch
2) Update /etc/koha/apache-shared-intranet-plack.conf manually, comment
   out the lines for and
3) Restart apache, plack and memcached
4) Stage a large record in, use a matching rule
5) Note it works!

You are receiving this mail because:
You are watching all bug changes.
Koha-bugs mailing list
website :
git :
bugs :

Reply via email to