Single stack optimistic lock exception?
Single stack optimistic lock exception?
- Subject: Single stack optimistic lock exception?
- From: Ken Anderson <email@hidden>
- Date: Fri, 24 Sep 2010 11:56:02 -0400
All,
I have an odd problem I'm wondering if anyone else has seen before.
I have apps that do high throughput processing of data - many times a second. It is single threaded, and uses a single EOF stack. I'm sure it's single threaded because the requests are coming in via an inbound queue, not any kind of front end.
Every once in a while under significantly high load, I get a few optimistic lock exceptions in a row, on rows that are only being touched by this app. We audit every update, and I can look into the audit tables and verify that nothing else has modified the record except this app.
It's almost like the snapshot has not been recorded properly before the next request is processed, so EOF thinks something else updated the value.
Our locking is implemented on a single column, trans_id, which is updated with every save. The audit table also saves the trans_id that's responsible for moving the record into audit, and all the values match in succession.
Has anyone had anything like this happen? Running 5.4.3 on Linux. and no... no Wonder.
Ken _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden