Pretty Tough to locate that information
Thank God for Frank Zammetti and Borland!

Many Thanks,
Martin --
--------------------------------------------------------------------------- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--------------------------------------------------------------------------- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
----- Original Message ----- 
From: "Frank W. Zammetti" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <user@struts.apache.org>
Sent: Sunday, January 07, 2007 10:42 AM
Subject: Re: Heuristic completions


> Martin Gainty wrote:
>> Good Afternoon All
>> 
>> I am seeking a definition and any information on the term 'Heurisitic 
>> completion'
> 
> Come on Martin, everybody knows what heuristic completion is:
> 
> Heuristic completion is when a transaction attempts to complete, and one 
> of its participating Resources makes a heuristic decision during the 
> completion stage. A heuristic decision is a unilateral decision made by 
> one or more Resources to commit or rollback updates--without regard for 
> the outcome determined by the ITS Transaction Service.
> 
> Heuristic decisions typically only occur during unusual circumstances 
> that prevent normal processing--such as a network failure, or if the 
> Coordinator does not complete the two-phase commit process in a timely 
> manner. When a heuristic decision is made, there is a risk that the 
> decision may differ from the outcome determined by the ITS Transaction
> Service, resulting in a loss of data integrity.
> 
> (Just kidding, I had no idea what it was, I cheated: 
> http://info.borland.com/techpubs/books/its/its10/programmer/itspg08.htm#1079980)
> 
> Frank
> 
> 
> -- 
> Frank W. Zammetti
> Founder and Chief Software Architect
> Omnytex Technologies
> http://www.omnytex.com
> AIM/Yahoo: fzammetti
> MSN: [EMAIL PROTECTED]
> Author of "Practical Ajax Projects With Java Technology"
>  (2006, Apress, ISBN 1-59059-695-1)
> Java Web Parts - http://javawebparts.sourceforge.net
>  Supplying the wheel, so you don't have to reinvent it!
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

Reply via email to