An error has occurred while handling the request

0
Dear forum, Does anyone know what this error means in Mendix 5? And what is the root cause of it? or direction how to investigate? 2015-01-26 12:55:59.714 ERROR - Connector: An error has occurred while handling the request. [User 'xxxxx' with session id 'd82aec0e-863e-4972-b296-9819bd0d8c8c' and roles 'HRUser'] 2015-01-26 12:55:59.714 ERROR - Connector: java.lang.InterruptedException: null at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1038) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326) at scala.concurrent.impl.Promise$DefaultPromise.tryAwait(Promise.scala:208) at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:218) at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223) at scala.concurrent.Await$$anonfun$result$1.apply(package.scala:111) at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53) at scala.concurrent.Await$.result(package.scala:111) at com.mendix.core.session.ActionDispatching.sendAction(SourceFile:42) at com.mendix.core.session.ActionDispatching.handleAction(SourceFile:35) at com.mendix.systemwideinterfaces.core.IMonitoredAction$class.monitor(SourceFile:32) at com.mendix.pf$i.monitor(SourceFile:330) at com.mendix.pf.a(SourceFile:283) at com.mendix.pf.a(SourceFile:223) at com.mendix.pf.a(SourceFile:205) at com.mendix.pf.processRequest(SourceFile:102) at com.mendix.externalinterface.connector.MxRuntimeConnector.processRequest(SourceFile:74) at com.mendix.core.impl.MxRuntimeImpl.processRequest(SourceFile:729) at com.mendix.m2ee.appcontainer.server.handler.RuntimeHandler.handle(RuntimeHandler.java:45) at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:368) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:953) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1014) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:861) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.run(BlockingChannelConnector.java:298) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:745)
asked
1 answers
1

It's a null exception (Connector: java.lang.InterruptedException: null). Several possible causes for thjis. Could be as simple as a string function (like substring) on an emtpy field, but sometimes it's somewhat less obvious then that.

You can debug with different loglevels, and see which MF-action generates this error of course.

answered