Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Trivial
-
Resolution: Fixed
-
Affects Version/s: 1.3.3
-
Fix Version/s: 2.0.0
-
Labels:None
-
Number of attachments :
Description
When a transaction timeout occurs the only information that is clearly stating the transaction was rollbacked due to a timeout is in DEBUG level.
In production, it's common to discard all DEBUG (or even INFO) messages, then it's difficult to known the reason of this timeout.
Could you change log level to WARN for the following message?
DEBUG (SessionId=,bitronix.tm.timer.TransactionTimeoutTask,33,bitronix-scheduler) [] marking a Bitronix Transaction with GTRID
[737072696E672D62746D00000128F259EEC600000000], status=ACTIVE, 1 resource(s) enlisted (started Tue Jun 01 09:11:39 CEST 2010) as timed out
Activity
Ludovic Orban
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 2.0.0 [ 16256 ] | |
| Affects Version/s | 2.0.0 beta1 [ 16527 ] | |
| Affects Version/s | 2.0.0 [ 16256 ] |
Ludovic Orban
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Ludovic Orban
made changes -
| Affects Version/s | 1.3.3 [ 14658 ] | |
| Affects Version/s | 2.0.0 beta1 [ 16527 ] |
Ludovic Orban
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
In TransactionTimeoutTask.java, replacing:
with
should do the job. Right?