hold capture fails on unique index constraint
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Evergreen 2.8.2 introduced a unique index on action.hold_request for current_copy (see bug 902255). We are seeing occasional errors in the logs where the application layer is trying to insert a duplicate row. Here is the client-side error message:
Tue Sep 27 2016 11:52:16 GMT-0400 (Eastern Daylight Time)
Check In Failed (in circ.util.checkin) (3):
{
"ilsevent":"2001", "textcode"
"debug"
2016-09-
/usr/local/
"desc":"The attempt to write to the DB failed",
"stacktrace"
/usr/local/
"servertime":"Tue Sep 27 11:51:49 2016",
"payload":
{
"__c":"ahr",
"__p":
[
null,
null,
"now",
14709465,
"t",
null,
null,
null,
null,
"C",
null,
15730851,
"<phone number redacted>",
null,
null,
170,
"2016-
170,
"2016-
369968,
0,
170,
14709465,
2121201,
null,
null,
null,
null,
null,
null,
"f",
null,
null,
null,
null,
null,
"t",
null,
null,
null,
"f"
]
}
,
"pid":27220,
"message"
"route_to":" "
}
Attaching scrubbed-
I see this often as well. Have not yet tried to find the source of the problem. FWIW, I was not able to reproduce when testing bug #1596595.