Concurrency problem

RT Developers
1

Hello

Not sure if there’s any way of getting any help on this or not, but I’m
stuck with an old version of RT
(either 2.0.12 or 2.0.15 - likely a mix) so the structure of some of the
code and supporting libraries
may be way too out of date for any help here…

We’re experiencing concurrency issues - specifically when 2 people
’take’ a ticket in the same short window
(1-3 seconds, depending on load) they both seem to have taken it.
Both names are written
to the ticket history as having ‘taken’ the ticket, and neither sees a
message indicating that they do not, in fact,
own the ticket. Only after some work has been done and a user goes to
save the work do they see a message
that they do not own the ticket.

I’ve downloaded the list archives from 2000-now looking for the word
’concurrency’ or ‘concurrent’ and
have only found those mentioned a couple of times, and those mails
aren’t anything related to my issue.

This is running on a standard LAMP stack, but I don’t think the issue is
related to mysql specifically.

Has anyone else noticed this issue?

Thanks…

Michael Kimsal

2

This is running on a standard LAMP stack, but I don’t think the issue is
related to mysql specifically.

Has anyone else noticed this issue?

I used to see this, too. And while you’re in some sense right in
that it’s not specifically due to MySQL, it’s sort of due to the
MySQL-based design: since there never was any way of enforcing
transactional integrity in the back end, there couldn’t really have
been a way to avoid this race condition. That said, I think later
releases have somewhat improved on the matter (certainly it doesn’t
happen to us as often as it used to do).

A

Andrew Sullivan | ajs@crankycanuck.ca
The fact that technology doesn’t work is no bar to success in the marketplace.
–Philip Greenspun