[JBoss Transactions Development] - TransactionMonitoringAndVisualization
by Libor Krzyžanek
Libor Krzyžanek [https://community.jboss.org/people/lkrzyzanek] modified the document:
"TransactionMonitoringAndVisualization"
To view the document, visit: https://community.jboss.org/docs/DOC-48255
--------------------------------------------------------------
h1. Transaction Monitoring and Visualization
h3. Overview of the Tool
The purpose of this project is to create a tool for monitoring the status of in-flight and complete transactions. The main aims of the tool are to help debug transaction related issues and also to provide insight into the running of the system. Essentially, the tool monitors a running system (or a log from a running system) and produces a detailed list of all transactions. A user may then select a particular transaction to see in more detail, including the participants involved in the transaction, the outcome of the transaction and the participants that influenced the outcome. The tool could be visual, showing a diagrammatic view of a transaction or may be command line based, producing a textual output (or maybe both).
h3. What Problems does this solve?
* Transaction Timeout detection. We frequently get support requests (via the forums or elsewhere) from users who are experiencing intermittent rollbacks of transactions due to timeout. It is not a simple matter for the user to figure out that this is what's happening.
* Transaction Profiling. It may be relatively easy to detect transactions that are taking longer than desired to complete. However, diagnosing which party in the transaction is to blame is non-trivial.
* Loops and Diamonds detection. In a distributed transaction it is possible to introduce a loop or a diamond without realizing. JTS may tolerate this, but distributed JTA and bridged WS-AT to JTA does not. Identifying this scenario is non-trivial and requires detailed internal knowledge of the TM.
* Reasoning about the System Architecture. Producing an architectural diagram of a distributed transaction with many participants and servers is not an easy task. Furthermore it can be error prone and could change based on the application inputs. The difficulty of this task is further compounded if multiple transaction types are involved (WS-AT, WS-BA, REST-AT, etc). This diagram is essential for reasoning about the current architecture and for considering improvements or changes. Also this diagram alone may not be enough without detailed profiling overlayed.
* Analyzing Disk Syncs. One approach to improving the performance of a transaction is to reduce the number of disk syncs. The problem is that it is often difficult to calculate exactly how many you are performing and what delay each adds.
h3. Who is the target audience?
* End users, to diagnose their own issues
* GSS, to diagnose customer issues
* Architects, to analyze their system architecture
* Those new to the field of transactions, learning what's going on.
h3. How does it solve these problems?
The tool analyses the server log and gathers data on every transaction ran. The tool could also support live updates for a server that is still running. The tool assumes that it can gather all its information from log statements. If it can't, we take the view that some logging is missing and then add it. We may also want the tool to support different log levels. For example, it may need a log level of TRACE to acquire full knowledge of the system. This may introduce too much of a performance overhead, so we may want to allow the tool to tollerate the reduced information provided by the less verbose log levels. In this case only basic information would be provided.
h6. Querying feature
The data can be queried to find out specific information. For example, show me all the transactions that rolled back. Given a rolledback transaction, the data should be available to diagnose exactly why it rolledback. Other things you may want to query by:
* *Outcome*. Committed, Rolledback, heuristic, etc
* *Type*. JTA, JTS, WS-AT, REST-AT, etc
* *Duration*. Find all fast or slow transactions
* *Inflight*. Show transactions currently inflight
* *Stuck*. Inflight transactions that have been running for longer than Xms.
* *Recovery*. All transactions that needed to be recovered.
h6. Diagnostics
The tool could also allow 'profiles' to be plugged in. A 'profile' is responsible for identifying common problems that we see users having. Hopefully these would allow issues to be identified earlier before they are passed further up the support chain. For example, we may create a 'profile' that searches over the data looking for loops or diamonds. Another could be responsible for identifying timeouts and maybe hinting at their cause. These 'profiles' would be created based on community demand.
h6. Visualization
In order to help architects reason about the system architecture, the tool could produce a visualization of a transaction of interest. A few diagrams should give you an idea of what the tooling could produce:
https://community.jboss.org/servlet/JiveServlet/showImage/102-48255-2-202... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-48255-2...
Here we can see that a transaction was begun on Server1. It enlisted a DB and JMS queue locally and invoked a remote service on Server2. A second resource (DB2) was enlisted on Server2.
https://community.jboss.org/servlet/JiveServlet/showImage/102-48255-2-202... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-48255-2...
In this example we can see that the transaction rolled back because DB2 voted rollback.
Other possible features:
* *Participant types*. Display if the participant is one or two phase aware for JTA/JTS. Display the completion type (Participant/Coordinator) for WS-BA.
* * Resource types*. Whether it's a database or message queue and maybe include the name and version.
* *Multiple Transaction Types*. Somehow depict the type of transaction (JTS, WS-AT, REST-AT, etc).
* *Display Bridges*. Display when a transaction is bridged from one type to another
* *In flight Transactions*. More useful for long running transactions; display the current status of each participant and update the display in real-time as the status changes.
* *Recovery Status*. Show which resources crashed and the status of those resources already committed or recovered.
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-48255]
Create a new document in JBoss Transactions Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
.png){kind=link}
.png){kind=link}
11 years, 11 months
- 1
- 0
[JBoss Tools Development] - JBoss Tools Development Environment
by Mickael Istria
Mickael Istria [https://community.jboss.org/people/mickael_istria] modified the document:
"JBoss Tools Development Environment"
To view the document, visit: https://community.jboss.org/docs/DOC-18124
--------------------------------------------------------------
*
#Tools_and_technologies Tools and technologies
**
#Java Java
**
#Eclipse_PDERCP Eclipse PDE/RCP
**
#Git_and_EGit Git and EGit
**
#m2e m2e
**
#Tips_for_productivity_and_quality Tips for productivity and quality
***
#Install_Code_Recommanders Install Code Recommanders
***
#Static_analysis Static analysis
****
#Enable_all_JDT_warnings Enable all JDT warnings
****
#Install_Findbugs_for_Eclipse Install Findbugs for Eclipse
****
#Install_PMD_for_Eclipse Install PMD for Eclipse
***
#Coverage Coverage
*
#Get_source Get source
**
#To_work_on_a_specific_component To work on a specific component
*
#Set_up_a_target_platform Set up a target platform
*
#Run_JBoss_Tools_and_Tests_from_your_IDE Run JBoss Tools and Tests from your IDE
This article explains the different steps to set up a 1st-class environment when you want to write code for JBoss Tools
h1. Tools and technologies
h2. Java
JBoss Tools requires Java 6. Ensure your JRE and JDK are compatible with Java 6
h2. Eclipse PDE/RCP
JBoss Tools are a set of plugins for Eclipse. Then get your favourite recent version of Eclipse from here: http://eclipse.org/downloads/ http://eclipse.org/downloads/ We recommand you using +Eclipse for RCP and RAP Developers+. But you can also install PDE in any other installation of Eclipse:
https://community.jboss.org/servlet/JiveServlet/showImage/102-18124-6-185... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18124-6...
h2. Git and EGit
Instlall Git CLI, and install EGit in Eclipse (EGit is already provided in most Eclipse installations).
h2. m2e
m2e (maven integation for Eclipse) is also required. It's recommended that you also install *m2e-tycho* and *m2e-eGit* connector from +Preferences > Maven > Discovery > Open Catalog+.
https://community.jboss.org/servlet/JiveServlet/showImage/102-18124-6-202... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18124-6...
h2. Tips for productivity and quality
Here are some highly recommanded plugins that will make your more efficient when inside the IDE
h3. Install Code Recommanders
Provides additional snippets, templates and smart completion. Not intrusive. You can find it on the "Juno" update-site or the current Eclipse release site.
h3. Static analysis
Static analysis will detect bug very early and will save you minutes of debug every day. Using it will make you and your colleagues happier. It tells you while typing code that you may have a bug. No need to wait for running test or CI reports to detect this.
h4. Enable all JDT warnings
JDT provides very good static analysis, and can prevent you from writing bugs. You simply have to turn all "ignored" advices to "warning" in Window > Preference > Java > Compiler > Errors/Warning.
https://community.jboss.org/servlet/JiveServlet/showImage/102-18124-6-185... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18124-6...
h4. Install Findbugs for Eclipse
http://marketplace.eclipse.org/content/findbugs-eclipse-plugin http://marketplace.eclipse.org/content/findbugs-eclipse-plugin
h4. Install PMD for Eclipse
http://marketplace.eclipse.org/content/pmd-eclipse http://marketplace.eclipse.org/content/pmd-eclipse
h3. Coverage
Coverage answers to the question "What is tested or net?".
JBoss Tools CI builds provide Jacoco reports for coverage by unit tests (file name is jacoco.exec). This file can easily be analyzed inside Eclipse on your Java editor using EclEmma plugin: http://marketplace.eclipse.org/content/eclemma-java-code-coverage http://marketplace.eclipse.org/content/eclemma-java-code-coverage
h1. Get source
Each JBoss Tools component is now its own GitHub repo: https://github.com/jbosstools/ https://github.com/jbosstools/
h2. To work on a specific component
The easiest way to get started is to check out source for only the module you wish to work on, and import Java projects from this part of the source tree.
Example:
* I want to fix a bug in CDI component of JBT: git clone git://github.com/jbosstools/jbosstools-server.git and import plugins and tests projects from plugns/* and tests/*
h1. Set up a target platform
*Target Platform = Allowed Dependencies* We provide several TP that have different purpose. We do set up some default TP for development, that you should use. You should use those Target Platforms instead of installing the dependencies in your IDE. Then you IDE becomes "The tools you need to develop" whereas the Target Platform provides the dependencies.
Import into your Eclipse workspace JBoss Tools target platforms from GitHub:
git clone git://github.com/jbosstools/jbosstools-target-platforms.git
Then select the version you want for the target platform. Those versions are available as tags. You can see the list of tags with git tag -l.
Let's say for this example we want the target platform 4.2.0.c.
cd jbosstools-target-platforms
git checkout 4.2.0.c
Then, in Eclipse, +Import > Existing Maven Project+, browse to the +jbosstools-target-platfroms/jbosstools/multiple.+
Double-click on +multiple.target+, and click +Set As Target Platform+
+https://community.jboss.org/servlet/JiveServlet/showImage/102-18124-6-20254/setTp.png https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18124-6...
+
h1. Run JBoss Tools and Tests from your IDE
Once Target Platform is configured, you can easily give a try to your plugins using +Run As > Java Application.+ You can also run automated tests from your IDE using +Run As... > JUnit Plugin Tests+.
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-18124]
Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
11 years, 11 months
- 1
- 0