Hi all,
I have large daily log file(s) that hold the times for requests and responses on different system requests. What I want to do is work out average transaction times for the day (one log = one day).
The problem I'm having is figuring out how to skip rows, i've sorted the output by uniq... (2 Replies)
We are getting below error when processing a transaction through ESB.
I work for SOA admin and checked the JCA connection is working fine also code also working fine in other envs.
An unhandled exception has been thrown in the ESB system. The exception reported is:... (1 Reply)
HI,
Can anyone explain me the concept behind ZFS transactional semantics (either a transaction is entirely commited or it is not)? so data and disk failures are reduced. (5 Replies)
Can some one help me related to .sql file issue.
I have a .sqlfile and tried to read the file thru unix. In the .sqlfile I have error rows as well and when error comes I dont want to proceed further and need to roll back all the transactions.
sample .sql file below
insert into
test... (2 Replies)
Hi ,
I have a situation where I have to Process files ( move , edit or rename ) in a folder ..... This folder is a FTP folder and Files keep coming in when they are available ... So I should perform my actions on those which which completed transaction .. .
Is there a way to identify a... (3 Replies)
How do I determine the resources needed based on volume of transactions. By resources I mean, the cores, memory etc. Is there a way to arrive at that value? (1 Reply)
Discussion started by: ggayathri
1 Replies
LEARN ABOUT DEBIAN
af_abort
af_transact(3) Attribute Filesystem (AtFS) af_transact(3)NAME
af_transaction, af_commit, af_abort - a simple transaction mechanism for AtFS
SYNOPSIS
#include <atfs.h>
int af_transaction (void)
int af_commit (void)
int af_abort (void)
DESCRIPTION
These functions implement a simple transaction mechanism for AtFS. A transaction starts with calling af_transaction. All changes to exist-
ing ASOs performed hereafter have no immediate permanent effect. They rather get into effect, when the transaction is ended. Calling
af_commit ends the transactions and causes all changes to be saved to disk. af_abort aborts the transaction without saving the changes.
These will then be discarded.
Only modification of the state of existing source ASOs will be deferred. Creation or deletion of ASOs have immediate effect, regardless if
a transaction is in effect or not. Additionally, all operations on derived ASOs (all operations on the derived object cache) are not
affected by the transaction.
All archive files that are to be changed when the transaction is finished are locked until the end of the transaction. The lock prevents
all other applications to perform any modifications on the archive file. You should make sure, that ending a transaction should never be
dependent on the successful termination of another application (deadlock danger).
DIAGNOSTICS
Upon error, -1 is returned and af_errno is set to the corresponding error number.
BUGS
Changes to the contents of busy versions have immediate effect.
AtFS-1.71 Fri Jun 25 14:33:21 1993 af_transact(3)