[jbossts-issues] [JBoss JIRA] (JBTM-1809) At trace logging to facilitate discovery of the transaction hierarchy

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Fri Sep 27 06:17:03 EDT 2013


    [ https://issues.jboss.org/browse/JBTM-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12807859#comment-12807859 ] 

Tom Jenkinson commented on JBTM-1809:
-------------------------------------

Did this get resolved? I saw some commits on the 4.17 branch
                
> At trace logging to facilitate discovery of the transaction hierarchy
> ---------------------------------------------------------------------
>
>                 Key: JBTM-1809
>                 URL: https://issues.jboss.org/browse/JBTM-1809
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JTS
>    Affects Versions: 5.0.0.M3
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Optional
>             Fix For: 4.17.11, 5.0.0.M4
>
>
> In a distributed JTS transaction there is insufficient information in the logs to facilitate the construction of the transaction hierarchy.
> For example when a transaction propagates between 3 servers the logs on server 3 do not indicate which of the two other servers has the parent transaction. This feature is required by the [https://community.jboss.org/wiki/TransactionMonitoringAndVisualization] tool.
> A possible solution is to print out the TM node identifier and the CORBA request id in the CORBA Client and Server Request Interceptors (in methods send_request and receive_request_service_contexts respectively).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbossts-issues mailing list