1Z0-133 · Question #104
You are troubleshooting Java Transaction API (JTA) transactions. The WebLogic Server extension to JTA provides which optional transaction attribute to make troubleshooting easier?
The correct answer is A. a name. https://docs.oracle.com/middleware/11119/wls/WLJTA/trbtrx.htm
Question
You are troubleshooting Java Transaction API (JTA) transactions. The WebLogic Server extension to JTA provides which optional transaction attribute to make troubleshooting easier?
Options
- Aa name
- Ban ID
- Cthe status of "marked for rollback"
- Da status
How the community answered
(43 responses)- A77% (33)
- B5% (2)
- C12% (5)
- D7% (3)
Explanation
https://docs.oracle.com/middleware/11119/wls/WLJTA/trbtrx.htm
Topics
Community Discussion
5The correct answer is A, a name. Oracle's WebLogic Server JTA extension lets you assign a human-readable name to a transaction via the UserTransaction getName and setName hooks, which is something the vanilla JTA spec does not require. When you are staring at a thread dump or a JTA log at 2am trying to match a stuck transaction to a business operation, that name cuts your triage time dramatically compared to hunting down an opaque XID. Options B and D describe things the standard JTA already tracks through getStatus and the transaction manager internals, and C is a transaction state, not an attribute you assign to aid troubleshooting.
Solid breakdown, and the exam trap I fell into the first time was misreading a question that buried the word "WebLogic-specific" in the stem, which made B look right until I remembered that getStatus is plain JTA and the whole point of the extension question is what Oracle layers on top of the spec.
So the WebLogic JTA extension lets you give a transaction a name for easier debugging, right, but how does that name actually show up in the logs?
The name you set via setTransactionName shows up in the server logs tied to that transaction's entries, but only if you have the JTA debug flags actually enabled in your domain config, otherwise you will never see it no matter what you name the thing.
I went back and forth on this one but I am telling you it is B, because the whole point of a WebLogic extension to JTA is giving you something concrete to grab onto in your logs, and an ID is exactly that, it lets you trace a specific transaction through the noise when everything is blowing up at 2am.