Conflicts in the region are not reported back to the client
Bug #1353573 reported by
Sean Broeder
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Trafodion |
Fix Released
|
High
|
Sean Broeder | ||
Bug Description
When a client calls endtransaction a conflict check is performed in the region to see if other transactions have updated the same rows as the current transaction and committed earlier. When this check fails because a conflict is detected an error must be returned to the client, but it is not.
This is currently under investigation in the DTM and will be fixed urgently.
| Changed in trafodion: | |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| Sean Broeder (sean-broeder) wrote | #1 |
| Changed in trafodion: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Fixed and merged into master 8/8/2014
Change-Id: I745739e5939d80