Which Java Transaction API (JTA) attribute needs a larger value?

You are troubleshooting why transactions are not being committed. After investigation, you realize
that these transactions have enough time during the first phase of the two –phase commit, but not
enough time during the second phase. Therefore, rather than committing, they are timing out and
are being rolled back.
Which Java Transaction API (JTA) attribute needs a larger value?

You are troubleshooting why transactions are not being committed. After investigation, you realize
that these transactions have enough time during the first phase of the two –phase commit, but not
enough time during the second phase. Therefore, rather than committing, they are timing out and
are being rolled back.
Which Java Transaction API (JTA) attribute needs a larger value?

A.
Timeoutseconds

B.
Abandon Timeout seconds

C.
Before completion Iteration Limit

D.
CheckpointIntervalseconds

E.
Unregister Resource Grace period

Show Hint

Leave a Reply 4

Your email address will not be published. Required fields are marked *

Thangabali

Thangabali

Ans: B

Reply

siva

siva

“B” is correct answer.

Abandon Timeout Seconds

The transaction abandon timeout in seconds. During the second phase of the two-phase commit process, the transaction manager will continue to try to complete the transaction until all resource managers indicate that the transaction is completed. Using the AbandonTimeoutSeconds attribute, you can set the maximum time that a transaction manager will persist in attempting to complete a transaction during the second phase of the transaction. After the abandon transaction timer expires, no further attempt is made to resolve the transaction. If the transaction is in a prepared state before being abandoned, the transaction manager will roll back the transaction to release any locks held on behalf of the abandoned transaction.

MBean: weblogic.management.
configuration.JTAMBean

Attribute: AbandonTimeoutSeconds

Reply

nebz

nebz

Agree : Answer is B

Reply