Whats 2-phase commit for

hi guys
i am curious, why JTA invent the 2-phase commit?
whats it stand for? how we use it.
thanks alot

http://www.webopedia.com/TERM/T/two_phase_commit.html
http://www.sei.cmu.edu/str/descriptions/dtpc.html
or just google it.

Similar Messages

2 phase commit for entity bean

Hi all,
Does the 2-phase commit capability in WL6.X applies to entity bean?
Thanks,
Rick

Two phase commit is the mechanism that allows transactions to the managed
across different servers and databases.
yes, definitely I does apply for entity beans
"Rick Lee" <[email protected]> wrote in message
news:[email protected]..
>
Hi all,
Does the 2-phase commit capability in WL6.X applies to entity bean?
Thanks,
Rick

2 Phase Commit for ESB based Appliation

If I wrote an application that needed two phase commit and I used Oracle ESB as the mechanism to link two different parts of the application together, would I have that capability?

ESB supports global transactions such that if any XA endpoint fails, the others are rolled back. See the transaction/exception handling lesson on otn.oracle.com/goto/esb for details of how it works.

Tuxedo 12c - Do mainframe adapters support two-phase commit?

With Oracle Tuxedo 12c, do the Tuxedo mainframe adapters support two-phase commit? I see there is support for two-phase commit with Tuxedo COBRA, for relational databases. My customer has a requirement to integrate with their mainframe systems and require two-phase commit (for rollback functionality) with the Tuxedo mainframe adapters.

Hi,
The Tuxedo Mainframe Adapter for SNA supports two phase commit protocol, or in IBM mainframe parlance syncpoint level 2.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

ADF Service Interface: two-phase commit issue for multiple data sources

In FusionApps, For a service interface we had to use two DataSource resources (in the ejb-jar.xml),
one is ApplicationServiceDBDS for SI and the other one is ApplicationDBDS(I don’t know the exact reason why this is needed, but when running the webservice, Framework was throwing an error asking for this) After adding these two, now(while running the webservice) we’re caught up with an error saying that unable to participate in two phase commit. I think this is because we added two dataSources, if we just use one dataSource everything is working fine.
Error message from app server:
"JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source=ApplicationDB"
we have made the changes to ApplicationDB as said in the error message, but then the server is failing to start because of this.

Hi,
this is what the doc says - though not about two phase commit but transaction sharing:
"At runtime, the calling client and the ADF service may or may not participate in the same transaction, depending on the protocol used to invoke the service (either SOAP or RMI). Only the RMI protocol and a Java Transaction API (JTA) managed transaction support the option to call the service in the same transaction as the calling client."
When your application accesses a remote ADF Business Components service, each remote call is stateless, and the remote service will not participate in the same transaction as the business component that uses a service-enabled application module's service interface.
In the majority of the cases, calls to remote services will be informational in nature and will not make changes to remote objects. However, if you must use a remote service to make changes, then keep these points in mind:
An exception thrown by the remote service will cause the local transaction to fail.
If you successfully call a remote service that results in modifying data, and then subsequently your local transaction fails for any reason, then it is the responsibility of your error handling code to perform a compensating transaction against the remote service to "undo" the previous change made."
http://docs.oracle.com/cd/E23943_01/web.1111/b31974/bcextservices.htm
Frank

How to enable 2 phase commit in oracle11g(for distributed oracle databases)

Hi All,
We have three oracle servers(11g) and we need to update the data from one server to remaining servers. Want to know, is "two phase commit" automaticly enabled/installed in 11g or we need to enable it. If we need to enable it then what are the all steps required for the same.
Thanks & Regards
Ravi

It is always very nice to see people think they are so unique their question has not already been answered in the documentation.
Yes, two phase commit is enabled.
No, depending on what you want, automatically updating records from one server to other servers is likely a very bad idea, as Oracle has documented facilities for that.
You have amongst others
- Materialized views
- Oracle Streams
Those solutions definitely scale much better as your approach, as they are asynchronous. In your approach the master server will slow down as a result of updating slaves.
In distributed databases 'push' approaches are to be avoided and 'pull' approaches to be preferred. Which is exactly what materialized views and Streams do.
Sybrand Bakker
Senior Oracle DBA

What is two phase commit in Forms?

Hi
Could any one tell me,
what is two phase commit in Forms?
Cyp

Hi,
two phase commit is a database feature that ensures data consistency.
"Oracle's two-phase commit mechanism guarantees that, a distributed transaction will either commit on all involved nodes or roll back on all involved nodes."
Frank

Query for 2 PHASE COMMIT

Hi,
I need to understand concept of 2 phase commit.plz tell me..
INSERT INTO EMP_BKP(EMPNO) VALUES(777);
CREATE TABLE empbkp2 AS SELECT * FROM emp;
ROLLBACK;
SELECT * FROM EMP_BKP;
o/p:
empno
777
due to create stmnt it was autocommit so i got result..
INSERT INTO EMP_BKP(EMPNO) VALUES(777);
CREATE TABLE HJHJH AS SELECT * FROM JKJL; -- table JKJL doesn't exists
ROLLBACK;
SELECT * FROM EMP_BKP;
o/p:
empno
777
got error in create stmnt then too got o/p..
how it worked as create command failed.?

PC wrote:
Hi,
I need to understand concept of 2 phase commit.plz tell me..
INSERT INTO EMP_BKP(EMPNO) VALUES(777);
CREATE TABLE empbkp2 AS SELECT * FROM emp;
ROLLBACK;
SELECT * FROM EMP_BKP;
o/p:
empno
777
due to create stmnt it was autocommit so i got result..
INSERT INTO EMP_BKP(EMPNO) VALUES(777);
CREATE TABLE HJHJH AS SELECT * FROM JKJL; -- table JKJL doesn't exists
ROLLBACK;
SELECT * FROM EMP_BKP;
o/p:
empno
777
got error in create stmnt then too got o/p..
how it worked as create command failed.?CREATE TABLE is DDL & every DDL does COMMIT before it starts & COMMIT after it ends.
You can only ROLLBACK DML & not DDL

Two-phase commit

Hi, all.
Does WeblogicServer 5.1sp10 support two-phase commit?
I'm going to use Informix and Oracle.
But I'm not sure that WLS 5.1 support it.
For example,when new record is inserted in Informix,
it must be inserted in oracle.
and update,delete processes must be treated as two-phase commit.
If it support two-phase commit, let me know what i do for using
two-phase commit.
thanks..

Robert wrote:
Hi, all.
Does WeblogicServer 5.1sp10 support two-phase commit?No, you need WLS 6.x
-- Rob
>
I'm going to use Informix and Oracle.
But I'm not sure that WLS 5.1 support it.
For example,when new record is inserted in Informix,
it must be inserted in oracle.
and update,delete processes must be treated as two-phase commit.
If it support two-phase commit, let me know what i do for using
two-phase commit.
thanks..

Weblogic Two Phase commit

Dears,
we are facing slowness problem while migration application from weblogic 7 to weblogic 11g.
Our Application use EJB 2.1 CMP and oracle database
In web-logic 7 we use global transaction and emulate two phase commit .Our application works fine
If we set global transaction as last logging resource or Emulate two phase commit in weblogic 11g we found so much slowness in the application.
Kindly help me in this regard

Hi,
          Jolt is just a Java client API for Tuxedo services. Typically, Jolt is
          used by a client to invoke a Tuxedo service. From what I could gather
          from your post, you are probably doing some JDBC work and then calling
          out to a Tuxedo service and want the work done with the JDBC/XA driver
          and the database work done by the Tuxedo service to be comitted/aborted
          transactionally? Is this correct?
          If so, then you probably want to look at the JET API (essentially Jolt
          without the need for a JSL/JSH) for invoking Tuxedo services directly
          (instead of through the JSH) from a WLE Java Server. It should be fully
          capable of doing what I have described above.
          Hope this helps,
          Robert
          Hwa Min Tan wrote:
          > I have read that the WLE 5.1 supports the Open XA standard for
          > two-phase (distributed) commits.
          > However, I have been unable to find any documentation / code
          > samples that demonstrates that JOLT is also able to perform
          > two-phase commits, even though its architecture is
          > inherently Tuxedo.
          > We'd like to use two-phase commit on two separate databases
          > (one connected by Jolt and another using the WLE JDBC/XA driver.
          >
          > Does Jolt support two-phase commit and the Open XA standard?
          >
          > Many thanks for your help,
          >
          > Hwa Min

2 Phase Commit Global Transaction resolution question.

Hi All,
I hope this is the right place to ask this question.
I'm trying to figure out what generally happens after the JTA AbandonTimeout occurs.
Here is the scenario.
1. Transaction Manager sends Commit to Resource Managers 1 and 2.
2. Resource Manager 1 receives and processes commit. Resource Manager 2 doesn't receive commit.
3. Resource Manager 1 returns acknowledgement.
4. Transaction Manager times out and starts recovery process.
5. Resource Manager 2 session times out and is set to in-doubt.
6. Transaction Manager can never reconnect to Resource Manager 2, and the AbandonTimeout is reached.
7. Transaction Manager abandons RM2 transaction.
8. Does Transaction manager return an error for global transaction?
I'm guessing the application the Transaction Manager is working for has its own timeouts which would most likely be a smaller value than the abandon timeout. So the transaction would most likely timeout. I'm just trying to make sure that the Global Transaction is not sent back as complete at a later time if the abandon timeout is reached.
Any Thoughts?
Thanks,
Matt

Petr-
In article <avflf9$ccu$[email protected]>, Petr Bulanek wrote:
Hi Marc,
Well, what does it really mean that \'Kodo will not respect the
semantics of the 2-phase-commit protocol\'?Are you saying that Kodo may commit my changes even if the other datastore
decides to roll the transaction back at the last moment?
That if Kodo has difficulties to commit, it would not roolback the global
transaction and as a result the other datastores will commit?You are correct: we currently do not do anything special for 2 phase
commit at all.
I mean, this is quite important and would like to know exactly what to
expect so I can work around it.
Thank you,
Petr
P.S.
I \'think\' I saw the plan to fix this in 2.5.x. What is the planned
release date?It is in the milestone for 2.5. We can't make any committments on its
release date, but it will hopefully be out within 2 months.
Marc Prud\'hommeaux wrote:
Petr-
You can integrate Kodo\'s JDO transactions into the Application Server\'s
global transaction (which might also commit multiple other
transactions). The only issue is that Kodo will not respect the
semantics of the 2-phase-commit protocol.
We expect to have this issue resolved soon.
In article <avdri3$f2o$[email protected]>, Petr Bulanek wrote:
I have noticed that there is open bug (211) that refers to 2 phase commit
and I just curious what the exact problem is.
Does that imply that the current version (2.4) does not allow 2 phase
commit?
Let\'s say I need to integrate JDO into global transaction (managed by App
server) and I may need during that transaction update multiple databases.
It could be implemented via JDO (multiple PMFs) or it could be a
combination of JDO and JDBC/EJB happening during the same transaction.
Am I likely to hit a problem if I do that?
Thank you,
Petr
Marc Prud\'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

2 phase commit in 9ias

I have a need to update 2 databases within a transaction, so I need to perform a 2 phase commit operation. I was wondering if
oracle 9ias v1.0.2.2.1 Solaris supports this type of operation. I can not seem to find it in the documentations.
thanks in advance.
Michael

Michael -- A true two phase commit is supported in Oracle9iAS v902 onwards. For v1022x what you get are two separate single phase commits. Please have a look at the Oracle9iAS J2EE Services Guide under transactions for more information.
Thanks -- Jeff

2 Phase Commit aka XA

I have noticed that there is open bug (211) that refers to 2 phase commit
and I just curious what the exact problem is.
Does that imply that the current version (2.4) does not allow 2 phase
commit?
Let's say I need to integrate JDO into global transaction (managed by App
server) and I may need during that transaction update multiple databases.
It could be implemented via JDO (multiple PMFs) or it could be a
combination of JDO and JDBC/EJB happening during the same transaction.
Am I likely to hit a problem if I do that?
Thank you,
Petr

Petr-
In article <avflf9$ccu$[email protected]>, Petr Bulanek wrote:
Hi Marc,
Well, what does it really mean that \'Kodo will not respect the
semantics of the 2-phase-commit protocol\'?Are you saying that Kodo may commit my changes even if the other datastore
decides to roll the transaction back at the last moment?
That if Kodo has difficulties to commit, it would not roolback the global
transaction and as a result the other datastores will commit?You are correct: we currently do not do anything special for 2 phase
commit at all.
I mean, this is quite important and would like to know exactly what to
expect so I can work around it.
Thank you,
Petr
P.S.
I \'think\' I saw the plan to fix this in 2.5.x. What is the planned
release date?It is in the milestone for 2.5. We can't make any committments on its
release date, but it will hopefully be out within 2 months.
Marc Prud\'hommeaux wrote:
Petr-
You can integrate Kodo\'s JDO transactions into the Application Server\'s
global transaction (which might also commit multiple other
transactions). The only issue is that Kodo will not respect the
semantics of the 2-phase-commit protocol.
We expect to have this issue resolved soon.
In article <avdri3$f2o$[email protected]>, Petr Bulanek wrote:
I have noticed that there is open bug (211) that refers to 2 phase commit
and I just curious what the exact problem is.
Does that imply that the current version (2.4) does not allow 2 phase
commit?
Let\'s say I need to integrate JDO into global transaction (managed by App
server) and I may need during that transaction update multiple databases.
It could be implemented via JDO (multiple PMFs) or it could be a
combination of JDO and JDBC/EJB happening during the same transaction.
Am I likely to hit a problem if I do that?
Thank you,
Petr
Marc Prud\'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

MDB (2-phase commit) behavior during abnormal JMS termination

Hello to everyone!
I plan to test the following scenario tomorrow (sort of a bug replication in our system).
Anyway, wanted to know in advance the expected behavior (just in case one of you already know
or have an experience related to this test). Thank you in advance.
Scenario:
I want to test/know the behavior of a 2-phase commit (2PC) MDB when JMS server abnormally exits
(say the process was killed).
Test flow:
start app server --> deploy 2pc-mdb --> send dummy data --> kill jms process --> restart jms process
1. will the connection be closed properly?
2. when jms server restarts, will the value of active consumer(count) doubled?
note: i think after mdb deployment, corresponding destination consumer count is 1.
the problem that occurred in our system was that the consumer count doubled after server restarted.
it seem like the previous connection was not closed when the jms server abnormally terminated.
any inputs will be greatly appreciated.
thanks and best regards.

You have to use TxDataSource for container managed tx or if you are using JTA (in
addition to ofcourse doing 2PC).
S
"Dale Olzer" <[email protected]> wrote:
>
Using weblogic 6.1 SP 4
I have a simple container managed Message Driven Bean. Using a destination
type
javax.jms.Queue.
When the onMessage method finishes the Message is still Pending on the
queue.
see the ejb-jar.xml below
<ejb-jar>
<enterprise-beans>
<message-driven>
<display-name>IvrMessageBean</display-name>
<ejb-name>IvrMsgBean</ejb-name>
<ejb-class>com.edocs.ps.ivr.IvrMsgBean</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
I noticed when I set a JDBC TX DataSource to 2 Phase Commit, the JMS
transaction
started commitig and nothing was left pending in the Queue.
Does 2PC have to be set in a DataSource for Container Managed MDB's to
work?

What are the announcements for renting VPS?

What are the announcements for renting VPS? For details, understand VPS and make the choice of rental; for Taiwan VPS and Hong Kong VPS, without records, unlimited contents, wider range, and more efficient experience. Your server will show its excellence with the advantages.
Most station agents become less inclined to virtual hosting, for national space, domain name records are needed, which waste the time; for overseas hosting such as Korea hosting, US hosting, no records, but slower speed than national space; therefore, more and more station agents prefer servers, but because the price of servers are too high, they turn their focus on VPS.
The following are the announcements:
1.Open remote desktop lander:
Start-run-mstsc or start-procedure-nearby-remote desktop connect
2.Several conditions for account halt:
First, client side login cause account halt
Second, certain account quits the remote control in midway when it runs routine
Third, certain routine is restricted by synchronous operation of system administrator.
3. Not install the third party firewall
If you need firewall, please use windows firewall, the third party firewall in VPS will cause system collapse and data loss, the system automatically obtains the newest windows patches and install itself, which do not require human operation. Installing system patches in VPS sometimes will heavily lead to VPS collapse and data loss.
Do not modify remote desktop port.
Because of the specialty of VPS system, default remote desktop port is 3389, do not modify randomly, or the remote connection will be out of work.
4. Except some special conditions that user registration is needed for certain procedure, when the remote connection has been close down, do not forget logout user to save memory resource, and prevent the loading connection next time, if it happens, reboot VPS.
5. VPS has been set with relative security when it was paid, with high security. It suggests that do not open firewall randomly, if you open it by your own, the following ports should be opened: 21(FTP), 3389(remote connection), 80(website http), 3306(MySQL), 1433(SQL Server). Timely check whether there is suspicious account or system log, download 360 safety guard to avoid these files and process.
6. Try not to modify registry hand-actuated, ensure the reboot of VPS. Modify remote ports please add the modified port in firewall first, and then reboot.
7.Modify IIS installation files, backup these files, and then modify them with the software that can keep the file layout, prevent these files from destroying IIS.
8.Website service of VPS and FTP service of IIS are default to open hand-actuated, set Web Publishing Service as automatically if you are station agent. If you often use FTP service of IIS, please set FTP Publishing Service as automatically, i.e. reboot it automatically. If you use serv-u, tick all the system service terms. In the terms of security and resource consumption , it suggests that those users who seldom use FTP do not set it as automatically.

Hi there
"So for ALL the apps, the annual monthly fee is £46.88, but you can rent occasionally for £70.32 pm.... ?" Correct
£17.58 single app plan requires an annual commit - it's £27.34 for the month-to-month plan without annual commit.
Thanks
Bev

Whats 2-phase commit for

Similar Messages

Maybe you are looking for