Bug 1459824 - Bug 1406866 - [GSS](6.4.15 patch) BZ1435549 - Exception coming from a transaction resource has to be provided to client when transaction failure occurs on server
Summary: Bug 1406866 - [GSS](6.4.15 patch) BZ1435549 - Exception coming from a transac...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager
Version: 6.4.15
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: One-off release
Assignee: jboss-set
QA Contact: Ondrej Chaloupka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-08 09:44 UTC by Francesco Marchioni
Modified: 2020-12-14 08:50 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-09-12 07:40:44 UTC
Type: Support Patch
Embargoed:


Attachments (Terms of Use)
Test case to reproduce the issue (229.35 KB, application/zip)
2017-06-08 16:56 UTC, Francesco Marchioni
no flags Details
On-Off Patch (3.26 MB, application/zip)
2017-06-09 07:22 UTC, Francesco Marchioni
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1441890 0 unspecified CLOSED [GSS](6.4.z) Suppressed exceptions in log formatting 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBEAP-10011 0 Critical Closed (7.0.z) Exception coming from a transaction resource has to be provided to client when transaction failure occurs on ser... 2018-09-12 07:38:47 UTC
Red Hat Issue Tracker JBTM-2870 0 Major Closed Provide way of getting suppressed exceptions out of SubordinateTransaction 2018-09-12 07:38:47 UTC

Description Francesco Marchioni 2017-06-08 09:44:31 UTC
Description of problem:
This Bugzilla has been created to request a CP15 On-Off Patch for the https://bugzilla.redhat.com/show_bug.cgi?id=1435549

Version-Release number of selected component (if applicable):
EAP 6.4.15

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Francesco Marchioni 2017-06-08 16:56:34 UTC
Created attachment 1286192 [details]
Test case to reproduce the issue

Comment 2 Francesco Marchioni 2017-06-09 07:22:58 UTC
Created attachment 1286317 [details]
On-Off Patch

Comment 3 Francesco Marchioni 2017-06-09 07:24:44 UTC
Patch tested with success with the reproducer. Here is the expected Suppressed's exception cause (JMS Prepare failed in callee) from the logs:

09:09:47,811 ERROR [stderr] (http-127.0.0.1:8080-5) 		Suppressed: javax.transaction.xa.XAException
09:09:47,811 ERROR [stderr] (http-127.0.0.1:8080-5) 			at org.hornetq.ra.HornetQRAXAResource.prepare(HornetQRAXAResource.java:135)
09:09:47,811 ERROR [stderr] (http-127.0.0.1:8080-5) 			at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.prepare(XAResourceWrapperImpl.java:177)
09:09:47,811 ERROR [stderr] (http-127.0.0.1:8080-5) 			at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:219)
09:09:47,811 ERROR [stderr] (http-127.0.0.1:8080-5) 			at com.arjuna.ats.arjuna.coordinator.BasicAction.doPrepare(BasicAction.java:2545)
09:09:47,811 ERROR [stderr] (http-127.0.0.1:8080-5) 			at com.arjuna.ats.arjuna.coordinator.BasicAction.doPrepare(BasicAction.java:2512)
09:09:47,811 ERROR [stderr] (http-127.0.0.1:8080-5) 			at com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(BasicAction.java:2083)
09:09:47,811 ERROR [stderr] (http-127.0.0.1:8080-5) 			at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1494)
09:09:47,812 ERROR [stderr] (http-127.0.0.1:8080-5) 			at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.SubordinateAtomicAction.doOnePhaseCommit(SubordinateAtomicAction.java:240)
09:09:47,812 ERROR [stderr] (http-127.0.0.1:8080-5) 			at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple.doOnePhaseCommit(TransactionImple.java:283)
09:09:47,812 ERROR [stderr] (http-127.0.0.1:8080-5) 			at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionCommitTask.manageTransaction(XidTransactionCommitTask.java:84)
09:09:47,812 ERROR [stderr] (http-127.0.0.1:8080-5) 			at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionManagementTask.run(XidTransactionManagementTask.java:78)
09:09:47,812 ERROR [stderr] (http-127.0.0.1:8080-5) 			at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
09:09:47,812 ERROR [stderr] (http-127.0.0.1:8080-5) 			at java.util.concurrent.FutureTask.run(FutureTask.java:266)
09:09:47,812 ERROR [stderr] (http-127.0.0.1:8080-5) 			at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
09:09:47,812 ERROR [stderr] (http-127.0.0.1:8080-5) 			at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
09:09:47,812 ERROR [stderr] (http-127.0.0.1:8080-5) 			at java.lang.Thread.run(Thread.java:745)
09:09:47,813 ERROR [stderr] (http-127.0.0.1:8080-5) 			at org.jboss.threads.JBossThread.run(JBossThread.java:122)
09:09:47,813 ERROR [stderr] (http-127.0.0.1:8080-5) 		Caused by: java.lang.Throwable: JMS Prepare failed in callee
09:09:47,813 ERROR [stderr] (http-127.0.0.1:8080-5) 			at org.hornetq.ra.HornetQRAXAResource.prepare(HornetQRAXAResource.java:136)
09:09:47,813 ERROR [stderr] (http-127.0.0.1:8080-5) 			... 16 more

Comment 4 tom.jenkinson 2018-08-28 08:40:52 UTC
Hi Francesco, is this one out of date or can it be merged?

Comment 5 Francesco Marchioni 2018-09-11 09:21:41 UTC
Tom, I've verified in the matching case from the Portal (01596228). This fix has been provided as part of the EAP 6.4.17 release (2017-09-05) so we can close this bugzilla.


Note You need to log in before you can comment on or make changes to this bug.