[jbosscache-issues] [JBoss JIRA] Commented: (JBCACHE-1476) TransactionLog generates spurious ERROR logs on read-only transactions

[Manik Surtani (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBCACHE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12474972#action_12474972 ] 

Manik Surtani commented on JBCACHE-1476:
----------------------------------------

Have you tried 3.1.0.GA?

> TransactionLog generates spurious ERROR logs on read-only transactions
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1476
>                 URL: https://jira.jboss.org/jira/browse/JBCACHE-1476
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transactions
>    Affects Versions: 3.0.2.GA
>            Reporter: Krzysztof Sobolewski
>            Assignee: Manik Surtani
>         Attachments: TransactionLogTest.patch
>
>
> We're testing our internal component with JBoss Cache 3.x and we noticed lots of ERROR logs from TransactionLog like this one:
> 2009-02-11 13:47:49,773 ERROR [org.jboss.cache.transaction.TransactionLog] (main) Could not find matching prepare for commit: GlobalTransaction:<192.168.1.18:7900>:3
> It turns out that these logs are harmless and happen only on transactions that are committed without doing any writes (i.e. read-only transactions). Even though it's mostly harmless, it's annoying, hence this bug.
> I'm going to attach a patch with a test case, which modifies the log4j configuration and adds a "deadly" appender to TransactionLog's logger to demonstrate the issue (it's a little bit funny...)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira