Monitoring tool for capturing detailed information of completed and in-flight transactions
JavaScript Java HTML Shell
Latest commit 8435a83 Nov 21, 2016 @zhfeng zhfeng committed on GitHub Merge pull request #82 from diegourban/master
NTA-38 fixing Visualize Transaction link
Permalink
Failed to load latest commit information.
core
demo
etc
nta-dist
nta-remote-dist
plugins
scripts Added a rebase script Sep 16, 2016
tools Added a version of maven Sep 13, 2016
webapp
.gitignore Added a version of maven Sep 13, 2016
README-jts.md NTA-49 rename the NTA artefact Feb 21, 2014
README.md Indicated how to get help Jul 28, 2016
build.sh Added a version of maven Sep 13, 2016
pom.xml NTA-70:Move all version numbers into root pom Apr 20, 2016

README.md

Narayana Transaction Analyser

The Narayana Transaction Analyser is a tool for helping to diagnose issues with JTA and JTS transactions in WildFly and JBoss EAP 6. Once deployed, the tool provides a list of all transactions ran within the application server. Detailed information is available for each transaction; such as what participants where involved and how they behaved. This makes it easier to find out what went wrong in the case of a transaction rollback.

The Transaction Analyser also supports distributed transactions that use JTS. Here the tool will present a diagram of all the servers involved, including which participants were enlisted with each application server and how they behaved. The distributed case is covered in README-jts.md. This document just covers the single application server case.

Under normal circumstances your application is unlikely to see transaction related issues. For this reason, the tool ships with a demo application allowing you to trigger failing transactions on-demand. You can then use the tool to see how these issues would be reported.

Getting help

If you have any questions about this project, please ask them on the Narayana forums: https://developer.jboss.org/en/jbosstm/content?filterID=contentstatus%5bpublished%5d~objecttype~objecttype%5bthread%5d

If you have identified an issue, please do discuss it on the forum and then raise an issue over here: https://issues.jboss.org/browse/NTA

Building from source

If you have a binary release of this tool, you can skip to the 'Deploy to WildFly' and 'Running the Demo Application' sections.

To build the Transaction Analyser from source you need Maven 3.0.0+ installed and available on your path. Then run:

mvn clean install

Download and Configure WildFly

Currently the Transaction Analyser can work with the WildFly 10.0.0.Final:

wget http://download.jboss.org/wildfly/10.0.0.Final/wildfly-10.0.0.Final.zip
unzip wildfly-10.0.0.Final.zip
export WILDFLY_HOME=/path/to/wildfly-10.0.0.Final.zip

Run Wildfly

cd $WILDFLY_HOME/bin
./standalone.sh -c standalone-full.xml

Deploy to WildFly

To run the Transaction Analyzer you just need to deploy the ear file to WildFly and visit the console. To do this:

cp nta-dist/target/nta-1.0.0.Alpha3-SNAPSHOT.ear $WILDFLY_HOME/standalone/deployments

Then visit: http://localhost:8080/nta/. By default the Transaction Analyser is disabled. To enable it click on the 'start' button at the top-right of the console's home page. Similarly, you can stop it by clicking the 'stop' button.

Running the Demo Application

The demo application provides a simple way to play with this tool if you don't have an application with failing transactions to hand. To deploy it:

cp demo/target/nta-demo-1.0.0.Alpha3-SNAPSHOT.war $WILDFLY_HOME/standalone/deployments

The demo is now available at http://localhost:8080/txdemo. To use the demo, simply click on the button for the scenario you want to run. When the scenario completes you will be notified of the outcome from the transaction. For most scenarios you will get an error message returned. This is to be expected as most scenarios result in a failing transaction. After running a scenario, go to the Transaction Analyser console and look at the details of the latest transaction.

NOTE: if you don't see any transactions in the Transaction Analyser, you may have forgotten to hit 'start' to enable analysis.