[
https://issues.apache.org/jira/browse/GERONIMO-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007821#comment-13007821
]
David Jencks commented on GERONIMO-4184:
----------------------------------------
The no-arg constructor is only there for people who don't care about recovery
and can't be bothered to set up the tm properly.
I guess if we're going to do anything here we should figure out a way to store
the baseid and counter range in the tx log (in the log object, not necessarily
in the log files) and read them in as part of recovery. Then if there's a
recorded baseid we can use it.
> In-doubt transaction Id's could be reused during server startup
> ---------------------------------------------------------------
>
> Key: GERONIMO-4184
> URL: https://issues.apache.org/jira/browse/GERONIMO-4184
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: transaction manager
> Affects Versions: 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.4
> Reporter: Kevan Miller
> Fix For: Wish List
>
> Attachments: GERONIM-4184.patch
>
>
> During server restart, we may reuse an Xid for a transaction which is
> in-doubt. Potentially confusing a resource manager. We need to insure this
> does not occur. Simple way is to remember the largest Xid in tran log and
> start with a larger number.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
