[
https://issues.apache.org/jira/browse/GERONIMO-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007817#comment-13007817
]
Vamsavardhana Reddy commented on GERONIMO-4184:
-----------------------------------------------
Thanks David. The one doubt I had is if introducing two random bytes along with
tmId would break anything. Your comment has clarified that.
Essentially the random bytes introduced by fix for GERONIMO-4393 will result in
a different tmId each time the server is started and break transaction
recovery. (Geronimo server may be immune to this as we use the XidFactoryImpl
constructor with tmId as parameter.) How can we make sure that even the
generated tmId would be the same for a server instance with subsequent restarts?
> 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
