You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/05/03 09:52:15 UTC
[jira] Created: (GERONIMO-3135) Allow enlisting into tx marked for
rollback only
Allow enlisting into tx marked for rollback only
------------------------------------------------
Key: GERONIMO-3135
URL: https://issues.apache.org/jira/browse/GERONIMO-3135
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: transaction manager
Affects Versions: 2.0-M5
Reporter: David Jencks
Assigned To: David Jencks
Fix For: 2.0-M6
Just because someone has marked a tx rollback only doesn't mean we should try to prevent them from reading more data from datasources to e.g. send back a more informative message to the user.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3135) Allow enlisting into tx marked for
rollback only
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-3135.
----------------------------------
Resolution: Fixed
Rev 539962. This solution has the big disadvantage that it uses a non-spec method on the geronimo TransactionImpl class to register a synchronization, but you can't register a synch on a tx marked for rollback using the jta method.
(actually the spec just says trying must throw a RollbackException, not that it won't succeed. Maybe we can register the synch anyway???)
> Allow enlisting into tx marked for rollback only
> ------------------------------------------------
>
> Key: GERONIMO-3135
> URL: https://issues.apache.org/jira/browse/GERONIMO-3135
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: transaction manager
> Affects Versions: 2.0-M5
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 2.0-M6
>
>
> Just because someone has marked a tx rollback only doesn't mean we should try to prevent them from reading more data from datasources to e.g. send back a more informative message to the user.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3135) Allow enlisting into tx marked for
rollback only
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-3135.
----------------------------------
Resolution: Fixed
Fixed in rev 534746.
> Allow enlisting into tx marked for rollback only
> ------------------------------------------------
>
> Key: GERONIMO-3135
> URL: https://issues.apache.org/jira/browse/GERONIMO-3135
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: transaction manager
> Affects Versions: 2.0-M5
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 2.0-M6
>
>
> Just because someone has marked a tx rollback only doesn't mean we should try to prevent them from reading more data from datasources to e.g. send back a more informative message to the user.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-3135) Allow enlisting into tx marked for
rollback only
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reopened GERONIMO-3135:
------------------------------------
Our connection tracking stuff means we also need to be able to register a synchronization up to the point at which we try to complete the transaction.
> Allow enlisting into tx marked for rollback only
> ------------------------------------------------
>
> Key: GERONIMO-3135
> URL: https://issues.apache.org/jira/browse/GERONIMO-3135
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: transaction manager
> Affects Versions: 2.0-M5
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 2.0-M6
>
>
> Just because someone has marked a tx rollback only doesn't mean we should try to prevent them from reading more data from datasources to e.g. send back a more informative message to the user.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.