Ondra Chaloupka created JBTM-2883:
Summary: Narayana should not hide exception traces even for internal or
protocol errors in WS txn
Project: JBoss Transaction Manager
Issue Type: Enhancement
Affects Versions: 5.5.6.Final
Reporter: Ondra Chaloupka
Assignee: Ondra Chaloupka
Narayana hides stacktraces of exception when some internal error (e.g. protocol,
communication...) happens in XTS. This particular problem reveales in case of customer
where .NET application
communicates with JBoss EAP over WS and WS-AT should be used. .NET (probably) uses
non-standard header/message that caused Narayana response being null.
The original error info was only
17:43:33,846 ERROR [org.jboss.jbossts.txbridge] (http-/0.0.0.0:8543-1)
com.arjuna.wst.SystemException: java.lang.NullPointerException17:43:33,852 TRACE
(http-/0.0.0.0:8543-1) Outbound Message
which is quite not much to start tracking reason behind the problem.
There should be shown stacktrace in log to get more detailed information for investigation
to start. E.g. it should be something like
The goal of this enhancement is to provide such logging on places where exception
stacktrace is currently thrown away (not written to log).
This message was sent by Atlassian JIRA