Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Atomic transaction


Related Topics

In the News (Sun 15 Nov 09)

  
  Atomic transaction - Wikipedia, the free encyclopedia
In computing, an atomic transaction is a database transaction or a hardware transaction which either completely occurs, or completely fails to occur.
Atomicity is an important component in avoiding race hazards.
Typically, atomicity is implemented by providing some mechanism to indicate which transactions have been started and finished, or by keeping a copy of the data before any changes were made.
en.wikipedia.org /wiki/Atomic_transaction   (492 words)

  
 Multi-master bus system performing atomic transactions and method of operating same - Patent 6189061
wherein the arbiter comprises logic for increasing a priority of the master of the atomic transaction due to a signal from the memory controller until the arbitration for the transaction subsequent to the atomic transaction.
If the transaction type of the actual slave is normal operation, or is the closing or finalizing transaction of an atomic transaction, then memory controller 26 provides a signal encoding "no atomic request", e.g.
an atomic transaction, bus 12 is granted subsequently to the initiating master for performing a closing transaction by the initiating master on bus 12.
www.freepatentsonline.com /6189061.html   (3130 words)

  
 Database transaction - Wikipedia, the free encyclopedia
A database transaction is a unit of interaction with a database management system or similar system that is treated in a coherent and reliable way independent of other transactions that must be either entirely completed or aborted.
In database products the ability to handle transactions allows the user to ensure that integrity of a database is maintained.
When this happens it is usually important to be sure that the database is not left with only some of the queries carried out.
en.wikipedia.org /wiki/Database_transaction   (349 words)

  
 Design of a dynamic configurable transaction framework
Transactions relieve application programmers of the burden of considering the effects of concurrent access to objects or various kinds of failures during execution.
Atomic transactions have proven to be useful for preserving the consistency in many applications like airline reservation systems, banking systems, office automation systems, database systems and operating systems.
Since the atomic transaction framework should be applicable in a large and complex information system, the flexibility and the extensibility of the framework is in fact a crucial issue.
wwwhome.cs.utwente.nl /~bedir/papers/oopslaws/wstrans.html   (4172 words)

  
 Tour Web Services Atomic Transaction operations
Abstractly, a classic transaction is just a grouping of recoverable actions, the guaranteed outcome of which is that either all the actions are taken, or none of them are taken (see Figure 1).
If the transaction is not known by the coordinator (in other words, is before any record is on the coordinator's log), then the recovery rule is to Undo any actions (our databases use their Undo records).
A useful transactional protocol requires that all the recovery cases for failure be covered in some way, either in the protocol or in the participants, and be enabled by the protocol.
www-128.ibm.com /developerworks/webservices/library/ws-introwsat   (4941 words)

  
 Esperpento
Both actions and compensating actions are likely to use atomic transactions in their internal implementations, but that is a detail at a lower level of granularity than the high-level business process.
An atomic transaction is an aggregate set of operations that either complete or fail in unison, usually in timeframes approaching a few milliseconds.
Atomic transactions exist to provide a solution to a common business problem: how to ensure the ACID properties (most notably atomicity) across multiple stores or resources that are used inside a single unit of work.
blogs.msdn.com /esperpento/default.aspx   (2550 words)

  
 ONJava.com -- Atomic File Transactions, Part 1
Atomicity is crucial for writing correct software in many applications; for example, a bank's software may implement a transfer from account A to account B as a withdrawal from A followed by a deposit to B. If the first action happens, then the second had better happen as well.
In standard parlance, a transaction is a sequence of operations with four properties, called the ACID properties, for Atomicity, Consistency, Isolation, and Durability.
Atomicity means that a transaction can end in only one of two ways: either successfully, in which case all its effects take place, or unsuccessfully, in which case it has no effect -- for all intents and purposes, the transaction never happened.
www.onjava.com /pub/a/onjava/2001/11/07/atomic.html   (1126 words)

  
 Web Services Transaction (WS-Transaction) (Global XML Web Services Specifications)
An atomic transaction (AT) is used to coordinate activities having a short duration and executed within limited trust domains.
It is relatively inexpensive to abort and retry an atomic transaction.
In contrast to atomic transactions, the participant list is dynamic and a participant may exit the protocol at any time before voting on the outcome.
msdn.microsoft.com /library/en-us/dnglobspec/html/ws-transaction.asp?frame=true   (8252 words)

  
 Web Services Transaction (WS-Transaction)
Atomic Transaction defines protocols that govern the outcome of atomic transactions.  It is expected that existing transaction processing systems wrap their proprietary mechanisms and interoperate across different vendor implementations. 
The relationship of Atomic Transaction and WS-Coordination are described in Section 2.  The coordination protocols for atomic transactions are described in Section 3.
The problem of deciding that all the actions requested as part of a transaction have completed is not part of this specification.  Instead, it is the responsibility of the application to determine this prior to attempting to commit or rollback the transaction.
dev2dev.bea.com /pub/a/2004/01/ws-transaction.html   (6051 words)

  
 XML.com: XML Transactions for Web Services, Part 2
The success of the atomic whole is normally referred to as a "Commit" operation, while the failure of any single activity results in a "Rollback" of the set of activities which constitutes the AT.
If transactions are not isolated, other database operations and transactions may alter the database during the execution of one transaction, thus producing inconsistent or inaccurate results.
When we try to keep a transaction isolated, we have to temporarily lock some of the database resources, which means these resources will not be available to other applications during the execution of the transaction.
webservices.xml.com /lpt/a/ws/2003/04/29/transactions.html   (4211 words)

  
 Kandula - Apache Kandula - Architecture Guide   (Site not responding. Last check: 2007-11-04)
When the local transaction is committed or rolled back the class simply calls the corresponding methods of the WSAtomicTransactionCoordinatorImpl (the super class) inside its XAResource implementation to extend the scope of the two phase commit protocol carried out on local resources to participants of the atomic transaction.
As a result even when the atomic transaction is terminated first, two-phase commit protocol is still carried out by the local transaction manager rather than the atomic transaction coordinator: i.e.
A thread's transaction context is either null or refers to a specific atomic transaction.
ws.apache.org /kandula/architecture-guide.html   (1437 words)

  
 22C:116, Lecture 30, Fall 2002
The two phase model of an atomic transaction discussed at the end of the last lecture ensures that, if there is a deadlock, the transactions involved will be blocked prior to any changes they might intend to make.
If the atomic transaction support is properly integrated into a trusted protocol implementation (typically at the session level, because the transaction itself is a kind of session), the issue of trust is resolved.
Write(X, D, ID) registers the intent of this transaction to write the value D on X. This write is not carried out immediately; rather, X is locked and the value D is set aside until all the changes required by this transaction have been accumulated.
www.cs.uiowa.edu /~jones/opsys/notes/30.html   (2032 words)

  
 Web services transactions: past, present and future
Atomic transactions are a well-known technique for guaranteeing consistency in the presence of failures [OTS].
Long-lived atomic transactions (as typically occur in business-to-business interactions) may reduce the concurrency in the system to an unacceptable level by holding on to resources (e.g., locks) for a long time; further, if such an atomic transaction rolls back, much valuable work already performed could be undone.
Atomic Transaction can be used as a bridge between proprietary transaction service implementations such as MSDTC [Microsoft DTC] and implementations based on standards such as [OTS], something which until recently has been extremely difficult to accomplish.
www.idealliance.org /papers/dx_xml03/papers/05-02-02/05-02-02.html   (4363 words)

  
 [No title]
In fact, the way the Participants address the consistency of their part of the transaction is correctly put out of the scope of the protocol.
This same understanding was also reflected at an early stage of BTP work when the TC adopted the atomic transactions as the core of BTP in the first phase of the TC’s work, and Cohesion was considered for a later time.
Participant Timeout We share a view of other TC members that autonomous parties in a transaction should be able to indicate participation in transaction for certain time and automatically withdraw from it after this time limit.
www.oasis-open.org /archives/business-transaction/200110/doc00004.doc   (2508 words)

  
 Transactions in BizTalk Server 2004 Orchestrations
Most developers understand the classical 'ACID' concept of a transaction as an atomic unit of work that, when performed, moves the system from one consistent state to a new, consistent and durable state, and which is isolated from other transactions.
It is an obvious step to speculate further that there may be a tie-up between the notion of batched atomic Orchestration transactions and the DTC transactions provided by the a Receive adapter with a batch of messages.
This article explains some of the features of transactions, and also speculates about the exact behaviour of 'batched' atomic transactions - a subject that is currently very opaque due to a lack of documentation.
geekswithblogs.net /cyoung/articles/BTSTransactions.aspx   (2909 words)

  
 Web Services Transactions specifications
The framework enables existing transaction processing, workflow, and other systems for coordination to hide their proprietary protocols and to operate in a heterogeneous environment.
This specification provides the definition of the atomic transaction coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification.
Explore how transactions work in one common and classic form to preserve data integrity, and apply that classical transaction description to the operations of the Web Services Atomic Transactions (WS-AT) and Web Services Coordination (WS-C) specifications in the article "Tour Web Services Atomic Transaction operations" (developerWorks, September 2004).
www-128.ibm.com /developerworks/library/specification/ws-tx   (576 words)

  
 alphaWorks : Web Services Atomic Transaction for WebSphere Application Server : Overview
A transaction is a set of operations that must be executed as a single unit, often called a logical unit of work.
JTA transactions are interpreted by the WS-AT for WAS run-time environment into CoordinationContexts such that a WS-AT representation of the current JTA transaction is made to flow upon Web service application requests.
If a JTA transaction is active on the thread when a Web Service Application request is made, the transaction is propagated across on the SOAP/HTTP request and established in the target's environment.
www.alphaworks.ibm.com /tech/wsat   (568 words)

  
 Commonality - BTS 2004 Atomic Scopes in Orchestrations and DTC Transactions
One interesting bit to remember about the use of atomic scopes in orchestrations is their relation with MSDTC (Distributed Transaction Coordinator) transactions.
What is not very obvious is that atomic transaction scopes in BizTalk 2004 do not imply DTC transactions; not necessarily, at least.
However, a atomic scope might lead to the generation of a DTC transaction if, from within the scope, you make a direct call to a COM+ component that requires a transaction.
www.winterdom.com /weblog/PermaLink,guid,450.aspx   (373 words)

  
 Atomic Transaction Approach   (Site not responding. Last check: 2007-11-04)
A fourth way to deal with shared files in a distributed system is to use atomic transactions.
The key property of this method is that the system guarantees that all the calls contained within the transaction will be carried out in order, without any interference from other, concurrent transactions.
If two or more transactions start up at the same time, the system ensures that the final result is the same as if they were all run in some (undefined) sequential order.
www.csse.monash.edu.au /courseware/cse5501/mdcs-l-04/sld021.htm   (136 words)

  
 22C:116, Notes, Nov. 8, 1995
The two phase model of an atomic transaction discussed at the end of the last lecture ensures that, if there is a deadlock, the transactions involved will be blocked prior to any changes they might intend to make, and as a result, they can be safely aborted.
Furthermore, locks are transient; if the server fails, all transactions are aborted and all locks released; this is most easily assured if locks are stored in transient memory and not out on disk with the permanent data.
In a distributed system, it is never reasonable to detect deadlocks by building a graph model of the system in some particular machine's memory and then run an algorithm to detect cycles in the graph.
www.cs.uiowa.edu /~jones/opsys/fall95/notes/1108.html   (1896 words)

  
 DTC Transaction in an Orchestration   (Site not responding. Last check: 2007-11-04)
Most people get confused when you start talking about Transactions from within an Orchestration.  They see the Scope Shape, set it to Atomic and then think that every action in the shape is within a Transaction.  I wish it was this easy, but there are a few more steps you need to take.
The Transaction Attributes is specified that states a Transaction is required for this Component.  This is the start of the class and within each method, you can now tell COM+ whether or not you want to Commit or Rollback the transaction.  This done with the following:
If you use a component in an Atomic Transaction, the isolation level for the orchestration must be compatible with the isolation level of the component.
dallas.sark.com /SarkBlog/mholdorf/archive/2004/10/12/430.aspx   (647 words)

  
 An Engineering Approach to Atomic Transaction Verification: Use of a Simple Object Model to Achieve Semantics-based ...   (Site not responding. Last check: 2007-11-04)
We discuss the design and implementation of a verification tool that can reason about the semantics of atomic database operations.
To bridge the gap between language design and automated reasoning, we make use of a simple model of objects that imitates the type-tagged memory structure of an implementation.
An Engineering Approach to Atomic Transaction Verification: Use of a Simple Object Model to Achieve Semantics-based Reasoning at Compile-time.
citeseer.ist.psu.edu /522304.html   (378 words)

  
 alphaWorks : Web Services Atomic Transaction for WebSphere Application Server : Reviews
Completing a review does not require your personal information, and you will not be contacted regarding your review.
Describe the most important capability that is MISSING in Web Services Atomic Transaction for WebSphere Application Server and should be added.
Describe something NEW you would most wish to see in a future version of Web Services Atomic Transaction for WebSphere Application Server.
www.alphaworks.ibm.com /tech/wsat/evaluation   (441 words)

  
 [No title]   (Site not responding. Last check: 2007-11-04)
Isolation: The effects of the operations are not shared outside the transaction until it completes successfully.
With this nesting Business Transactions can be handled as if they were Atomic Transactions.
This allows a parent to: select which children are included in the overall outcome.
n.ethz.ch /student/jodaniel/37-310/slides/wsTransaction_Clemens.ppt   (992 words)

  
 Specification of the Web Services Atomic Transaction Protocol   (Site not responding. Last check: 2007-11-04)
Specification of the Web Services Atomic Transaction Protocol
The Web Services Atomic Transaction protocol is a proposed protocol standard.
This page contains links to a formal TLA+ specification of the protocol and associated documents.
research.microsoft.com /users/lamport/tla/ws-at.html   (126 words)

  
 IBM showcases Web Services Atomic Transaction for WebSphere Application Server   (Site not responding. Last check: 2007-11-04)
IBM showcases Web Services Atomic Transaction for WebSphere Application Server
Before we all dive into a week of MS-only and "SOA and Indigo rules" mood, here is something to get your hands on now.
Will WSE vX.Y will also support this or do we have to wait for Indigo maturing...?
weblogs.asp.net /cweyer/archive/2003/10/25/33464.aspx   (262 words)

  
 webservices.xml.com: XML Transactions for Web Services, Part 2
webservices.xml.com: XML Transactions for Web Services, Part 2
Altova XML Suite - Design, test, and deploy Web services without manual coding.
Learn XML development with Stylus Studio XML IDE
webservices.xml.com /pub/a/ws/2003/04/29/transactions.html   (2116 words)

  
 Atomic transaction   (Site not responding. Last check: 2007-11-04)
The Atomic transactiononline and Atomic transactionWebsite List: Find the Best Sites For atomic transaction With Starware
Starware search is an excellent resource for quality sites on atomic transaction and much more!
Read about atomic transaction in the free online encyclopedia and dictionary.
www.lookfinance.com /atomic-transaction.html   (158 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.