[ http://jira.jboss.com/jira/browse/JBAS-28?page=comments#action_12310701 ] Alex Loubyansky commented on JBAS-28: -------------------------------------
The warning means that the entry is not in the cache. For the 'idle' machine it's ok since it might not have the entry in the cache. In this case, it's safe to ignore this message and the log level should be DEBUG or TRACE. For the machine doing the work, it seems like it tried to remove the entry from the cache more than once. First of all, a question for you whether it makes sense for your application? (if no, just don't make the cache invalidable) Second, there was an issue, i.e. an entry was invalidated as many times as the number of invocations on the instance was done in the tx. But I thought I fixed it with 'use transaction local instead of custom impl of the concept; also each key is invalidated now only once at commit, not as many times as the instance was invoked (missed call to synchronizations.put() in previous implementation)' http://cvs.sourceforge.net/viewcvs.py/jboss/jboss/src/main/org/jboss/cache/invalidation/InvalidationsTxGrouper.java?r1=1.1.2.5&r2=1.1.2.6 If you can debug it, please, do. > CacheInvalidator(3.2.7RC1 jdbc2) complains alot, why? > ----------------------------------------------------- > > Key: JBAS-28 > URL: http://jira.jboss.com/jira/browse/JBAS-28 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-3.2.7 > Environment: 3.2.7 jdbc2 with Cache Invalidation(JMS) > Oracle 9i > SonicMQ > Win 2000 Pro > JDK1.4 > 2 Jboss instances(1 doing work, 1 sitting idle recieving cache invalidation > messages) > Reporter: Ivan O. Parra > Assignee: Scott M Stark > > > We keep seeing these warning in our log files. > Quote: > jvm 1 | 11:19:31,671 WARN [CacheInvalidator] removal of 466 rejected for > null: the entry could not be found > and > Quote: > jvm 1 | 11:17:13,859 WARN [CacheInvalidator] removal of 1 rejected for > TransactionImpl:XidImpl [FormatId=257, GlobalId=scale-server2//10163, > BranchQual=]: the entry could not be found > So what is this and how do I get rid of it? > Other things I notice: > 1) The invalidator with the null transaction is not referenceing this data. > IE. This particular machine has not accessed that table/row (yet). This is > the "idle" machine. > 2) The invalidator with the defined transaction is shown more than once(some > times once, sometimes 3-4 times). > What I think may be happening. > 1) The cache is being invalidation by the InvalidationManager on the global > cache that has not been set. > 2) On commit of a modified row, multiple removes aer being called on the > same transaction. If only one call is done, it works. But if multiple > removes for the same transaction is done, this warning appears. > I can throw into debugger to confirm both scenarios. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
