[jbossts-issues] [JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict

[Mark Little (JIRA)]

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

Mark Little edited comment on JBTM-2400 at 5/15/15 9:45 AM:
------------------------------------------------------------

I added a warning message to the lock record if it forces a rollback due to state change. I'm still not sure if this may output too many warnings, especially as the number of conflicts occur (amount of contention increases with threads etc.) So we may want to revisit this eventually and turn it into an info/trace.


was (Author: marklittle):
I added a warning message to the lock record if it forces a rollback due to state change. I'm still not sure if this may output too many warnings, especially as the number of conflicts occur (amount of contention increases with threads etc.) So we may want to revisit this eventually and turn it into an info.

> Add logging to help clarify if a TX is rolling back due to OCC conflict
> -----------------------------------------------------------------------
>
>                 Key: JBTM-2400
>                 URL: https://issues.jboss.org/browse/JBTM-2400
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: STM
>            Reporter: Tom Jenkinson
>            Assignee: Mark Little
>
> Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback.
> I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)