Kbase P123328: Transaction backout messages in database log after a successful call on a state-reset AppServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/11/2009 |
|
Status: Verified
SYMPTOM(s):
Transaction backout messages in database log after a successful call on a state-reset AppServer
Getting errors 2252 and 2253 on AppServer when an AppServer disconnects
Begin transaction backout. (2252)
Normal AppServer session ends
Only record activity is Temp-table activity
Transaction backout completed. (2253)
Doesn't happen when there is database activity in the same AppServer Session
FACT(s) (Environment):
State-Reset Appserver
OpenEdge 10.1A
CAUSE:
Bug# OE00147739
CAUSE:
The problem occurs when a CREATE <temp-table> statement starts a transaction in the temp-table db and a flag is mistakenly tripped marking this as a database database transaction.
When passing the temp-table as a parameter, a check is performed to ensure that there is no transaction active and, under these specific circumstances, mistakes the open pseudo-transaction for a database transaction.
Later, when wrapping up the transaction, it is determined that there is truly no transaction active so the transaction is undone. Nothing is actually undone in this case but the begin and end notes are added to the db log file.
FIX:
To workaround this behavior surround the code that interacts with the temp-table with a TRANSACTION block