XmlRpcException
We observe this kind of exceptions, please find out what they mean and how we can prevent them:
#!
[ERROR] [org.apache.xmlrpc.server.XmlRpcErrorLogger] - No method matching arguments: java.lang.Boolean, java.lang.String
org.apache.xmlrpc.XmlRpcException: No method matching arguments: java.lang.Boolean, java.lang.String
at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.execute(ReflectiveXmlRpcHandler.java:110)
at org.apache.xmlrpc.server.XmlRpcServerWorker.execute(XmlRpcServerWorker.java:46)
at org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:86)
at org.apache.xmlrpc.server.XmlRpcStreamServer.execute(XmlRpcStreamServer.java:200)
at org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(XmlRpcServletServer.java:112)
at org.apache.xmlrpc.webserver.XmlRpcServlet.doPost(XmlRpcServlet.java:196)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:314)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
Comments (12)
-
Account Deleted -
jep, it is related to pingback/trackback but not for sending a pingback/trackback. XmlRpcServlet is used to log pingbacks/trackbacks sent to BibSonomy. @jaeschke do we still need this pingback interface? Can we deactivate the error logging? (As far as i know we only log these events and don't do anything, right?)
-
- edited description
-
- changed status to open
-
- marked as trivial
-
- removed responsible
-
Can we log into a separate file? The idea was to collect these pingbacks for potential later analysis. I found that it is also quite useful to identify spam.
-
Account Deleted We could log these errors in another logfile, but probably more interesting would be to have non-error log output from pingbacks sent to bibsonomy. Where does the logging come from? Directly from XmlRpcServlet or all org.apache.xmlrpc.** or elsewhere?
-
I think we can disable this logging. If I understand it correctly, it happens when an invalid request is sent. We are not interested in these requests.
-
-
assigned issue to
-
assigned issue to
-
- changed status to resolved
added to log4j config
-
- changed milestone to 3.6.2
- Log in to comment
sounds like it is related to pingback/trackback