Dave Wolf wrote:
> How do you rollback without tx logging? Like for a hueristic rollback?
I don't understand your question. If the tx manager is
up and running, rollback is driven through the XA protocol.
If the tx manager crashes the state of the tx is lost which
can lead to tx timeout in the resource manager, and therefore
to heuristic decisions. Heuristic rollback would be one such
decision. So, logging impacts recovery capabilities of the tx
manager and lack thereof can lead to additional heuristic
decisions but I can't see how normal rollback processing would
be impacted by the absence of logging.
Note that I am talking about logging in the tx manager and
not logging in the resource manager. Of course, the resource
manager does its logging all the time, and discards its log
file in the case of a rollback. This is a functionality of
the database (or whatever) and is not implemented in the app
server. But this is not the logging functionality that I was
referring to in my previous post. In addition to the resource
manager's logging, the tx manager needs to log its internal
status *during* the 2pc, i.e. the participating resources, the
XIDs, the responses of the resources that it received so far
etc. in order to be able to recreate connections to the resource
managers after a system failure and pick up the 2pc protocol
where it left off. Does this clarify my comments?
> Dave Wolf
> Internet Applications Division
>
> p.s. Kinda funny we use IBM's engine and IBM doesnt?
WebSphere Enterprise ships with Encina in the box. WebSphere
Advanced is based on a port of Encina to Java to minimize
platform dependencies and to offer a pure Java environment to
people who need this. This comes at the expense of tx logging
for the reasons that I mentioned in my previous post.
Regards
Rainer
-----------------------------------------------------------------------------
Rainer Kerth, IBM WebSphere Architecture, [EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
