Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1.0
-
Fix Version/s: 2.1.3
-
Labels:None
-
Number of attachments :
Description
BTM provides a very good reporting when one tries to commit a transaction with no enlisted resource. These are most probably development errors.
Adding a flag or a logging strategy that would output the stack trace of the creation of the transaction as well as the stack trace of the commit of that transaction would definitely help to spot the actual issue.
Activity
Ludovic Orban
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 2.2.0 [ 16461 ] |
Ludovic Orban
made changes -
| Fix Version/s | 2.1.3 [ 18046 ] | |
| Fix Version/s | 2.2.0 [ 16461 ] |
Ludovic Orban
made changes -
| Assignee | Ludovic Orban [ lorban ] | Stéphane Nicoll [ sni ] |
Stéphane Nicoll
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Ludovic Orban
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Assignee | Stéphane Nicoll [ sni ] | Ludovic Orban [ lorban ] |
| Resolution | Fixed [ 1 ] |
Stéphane Nicoll
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
I implemented such mechanism and deployed a 2.1.3-SNAPSHOT version in the codehaus snapshot repository.
Could you please try it out and report back here if it works as you expected? See http://docs.codehaus.org/display/BTM/Maven2#Maven2-Earlyversions for the details about how to configure your Maven 2 pom to get access to the BTM snapshots.
Thanks!