Useless stacktrace?

0
What's the problem with the stacktrace below? I get this stacktrace every exact 10 minutes, so my guess was that there was something wrong with a scheduled event every 10 minutes. But no, I do not have a scheduled event which is triggered every 10 minutes. Everything is working fine though. These stacktraces are just messing up my log file. How can I figure out what's wrong? Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: Action with name '' not found. Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (1/22) java.lang.ClassNotFoundException Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (2/22) at java.net.URLClassLoader$1.run(URLClassLoader.java:202) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (3/22) at java.security.AccessController.doPrivileged(Native Method) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (4/22) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (5/22) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (6/22) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (7/22) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (8/22) at eg.a(SourceFile:118) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (9/22) at eg.b(SourceFile:146) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (10/22) at com.mendix.core.Core.execute(SourceFile:190) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (11/22) at bC.execute(SourceFile:39) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (12/22) at com.mendix.m2ee.server.handler.AdminHandler.handle(AdminHandler.java:84) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (13/22) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (14/22) at org.eclipse.jetty.server.Server.handle(Server.java:334) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (15/22) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (16/22) at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1007) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (17/22) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:747) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (18/22) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:209) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (19/22) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (20/22) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (21/22) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) Dec 7 11:13:10 127.0.0.1 dsitest: ERROR - ActionManager: (22/22) at java.lang.Thread.run(Thread.java:662) Dec 7 11:20:03 127.0.0.1 dsitest: INFO - Core: Removing expired session for user 'Guest_4e5c1557-e09e-4301-a347-f254b2c5f0b6'
asked
1 answers
2

This is a error message which is caused by monitoring software running on the mendix environment. So your application is probably hosted @ mendix. Upgrading to a new version (2.5.6 and above) will fix this issue.

I've reported this ticket #8846 a couple of months ago and migrating to a new version worked for me. Our log is fine now.

answered