[
https://issues.apache.org/jira/browse/GERONIMO-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed GERONIMO-6051.
-----------------------------------
Resolution: Won't Fix
Closing old outdated issues.
Note that the Apache Geronimo Application Server itself was declared EOL in
2017 and we do not maintain the server parts anymore.
We still do actively maintain many of the Java EE / Jakarta EE which saw the
light during creation of the Apache Geronimo Aplication Server.
If you feel that this ticket still affects one of those components then please
feel free to reopen the ticket.
thanks, your Apache Geronimo team!
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
