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

[Srinivasan Bakthavachalam (JIRA)]

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

Srinivasan Bakthavachalam commented on JBCACHE-1476:
----------------------------------------------------

The same problem is seen. The version used is JBC 3.0.3GA.
The tricky thing analyzed was the source is not having the class, but the binary has the class org.jboss.cache.transaction.TransactionLog.
Please let me know how to resolve for getting rid of the errror message.

Source - http://anonsvn.jboss.org/repos/jbosscache/core/tags/3.0.3.GA/src/main/java/org/jboss/cache/transaction/

Please check the binaries

> 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