[
https://issues.apache.org/jira/browse/JCS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767143#comment-17767143
]
Thomas Vandahl edited comment on JCS-237 at 9/20/23 2:43 PM:
-------------------------------------------------------------
The error message suggests that you have a cache listener that implements
ICacheListener where it should rather implement IRemoteCacheListener.
It is not a good sign when this warning occurs because it actually shows that
something is wrong in the implementation. Watch for the warning "Dropping Event
and marking Event Queue {0} as non-functional."
Please double-check your code.
Other than that, JCS actually uses java.util.logging by default. If you did not
call JCS.setLogSystem(LogManager.LOGSYSTEM_LOG4J2) before JCS.getInstance(...),
your log4j-configuration will not take effect.
For disabling warnings for the logger LogManager.getLog(
AbstractCacheEventQueue.class ), see the documentation of your log system.
was (Author: tv):
The error message suggests that you have a cache listener that implements
ICacheListener where it should rather implement IRemoteCacheListener.
It is not a good sign when this warning occurs because it actually shows that
something is wrong in the implementation. Watch for the warning "Dropping Event
and marking Event Queue {0} as non-functional."
Please double-check your code.
Other than that, JCS actually uses java.util.logging by default. If you did not
call JCS.setLogSystem(LogManager.LOGSYSTEM_LOG4J2) before JCS.getInstance(...),
your log4j-configuration will not take effect.
For disabling warnings for the logger LogManager.getLog(
AbstractCacheEventQueue.class ), see the documentation of your log system.
> Remote Cache update makes lot of log entries
> --------------------------------------------
>
> Key: JCS-237
> URL: https://issues.apache.org/jira/browse/JCS-237
> Project: Commons JCS
> Issue Type: Bug
> Components: RMI Remote Cache
> Affects Versions: jcs-3.1
> Reporter: Murali Thirugnanam
> Priority: Critical
> Fix For: jcs-3.1
>
>
> Remote Cache update makes lot of warnings as below in the log file. There is
> no application functionality issue due to this, but still we want to get rid
> these logs. Also, confirmed that there is no null values is being passed when
> updating the cache and this log is being written.
> Kindly help us to avoid logging these warnings, as we are not seeing any
> functionality issues. Already, tried updating the log4j2.xml to log only
> FATAL, still could these warning in the log file.
> ======================
> 2023-09-18 19:17:39,085 WARNING
> [org.apache.commons.jcs3.engine.AbstractCacheEventQueue]
> (CacheEventQueue.QProcessor-authCacheThread-317) Error while running event
> from Queue: PutEvent for key:
> com.interwoven.cache.model.auth.AuthTokenCacheKey@1f85b856 value: null.
> Retrying...: java.rmi.RemoteException: Method is not Remote: interface
> org.apache.commons.jcs3.engine.behavior.ICacheListener::public abstract void
> org.apache.commons.jcs3.engine.behavior.ICacheListener.handlePut(org.apache.commons.jcs3.engine.behavior.ICacheElement)
> throws java.io.IOException
> at
> java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:214)
> at
> java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:162)
> at deployment.cache-service.war//com.sun.proxy.$Proxy210.handlePut(Unknown
> Source)
> at
> deployment.cache-service.war//org.apache.commons.jcs3.engine.AbstractCacheEventQueue$PutEvent.doRun(AbstractCacheEventQueue.java:281)
> at
> deployment.cache-service.war//org.apache.commons.jcs3.engine.AbstractCacheEventQueue$AbstractCacheEvent.run(AbstractCacheEventQueue.java:218)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
