[
https://issues.apache.org/jira/browse/GERONIMO-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florent Guillaume updated GERONIMO-6051:
----------------------------------------
Description:
When a transaction is in timeout, the application can only know about it when
calling {{commit()}} and getting a {{RollbackException("Unable to commit:
Transaction timeout")}}.
Wouldn't it make sense to also make {{TransactionImpl.getStatus()}} do the
{{TransactionTimer.getCurrentTime() > timeout}} check and switch the status to
{{STATUS_MARKED_ROLLBACK}} when it's true? This way the application would know
that there's no way that the transaction can actually commit successfully.
was:
When a transaction is in timeout, the application can only know about it when
calling {{commit()}}.
Wouldn't it make sense to make {{TransactionImpl.getStatus()}} do the
{{TransactionTimer.getCurrentTime() > timeout}} check and switch the status to
{{STATUS_MARKED_ROLLBACK}} when it's true?
> Transaction timeout detection
> -----------------------------
>
> Key: GERONIMO-6051
> URL: https://issues.apache.org/jira/browse/GERONIMO-6051
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: transaction manager
> Affects Versions: 3.0.1
> Reporter: Florent Guillaume
> Priority: Minor
>
> When a transaction is in timeout, the application can only know about it when
> calling {{commit()}} and getting a {{RollbackException("Unable to commit:
> Transaction timeout")}}.
> Wouldn't it make sense to also make {{TransactionImpl.getStatus()}} do the
> {{TransactionTimer.getCurrentTime() > timeout}} check and switch the status
> to {{STATUS_MARKED_ROLLBACK}} when it's true? This way the application would
> know that there's no way that the transaction can actually commit
> successfully.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
