Internal server error

0
Sometimes we're getting web service errors. This happens when we do a web service call to another mendix app. Sometimes this results in a internal server error. What does this mean, is this on our side or the ws host side? com.mendix.modules.webservices.WebserviceException: Internal server error at fh.a(SourceFile:76) at com.mendix.core.Core.importXmlStream(SourceFile:1748) at com.mendix.core.Core.importXmlStream(SourceFile:1733) at bF.a(SourceFile:211) at bF.a(SourceFile:102) at kW.a(SourceFile:66) at eO.executeAction(SourceFile:96) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:49) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:473) at iu.b(SourceFile:155) at com.mendix.core.Core.executeSync(SourceFile:163) at it.a(SourceFile:71) at kW.a(SourceFile:66) at eO.executeAction(SourceFile:96) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:49) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:473) at iu.b(SourceFile:155) at com.mendix.core.Core.execute(SourceFile:187) at dx.execute(SourceFile:183) at jy.a(SourceFile:300) at jy.a(SourceFile:232) at jy.processRequest(SourceFile:183) at fA.a(SourceFile:75) at com.mendix.core.MxRuntime.processRequest(SourceFile:893) at com.mendix.m2ee.server.handler.RuntimeHandler.handle(RuntimeHandler.java:40) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1007) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:747) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:209) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.server.nio.BlockingChannelConnector$ConnectorEndPoint.run(BlockingChannelConnector.java:187) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:662) Caused by: Internal server error at l.a(SourceFile:176) at fh.a(SourceFile:64) at com.mendix.core.Core.importXmlStream(SourceFile:1748) at com.mendix.core.Core.importXmlStream(SourceFile:1733) at bF.a(SourceFile:211) at bF.a(SourceFile:102) at kW.a(SourceFile:66) at eO.executeAction(SourceFile:96) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:49) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:473) at iu.b(SourceFile:155) at com.mendix.core.Core.executeSync(SourceFile:163) at it.a(SourceFile:71) at kW.a(SourceFile:66) at eO.executeAction(SourceFile:96) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:49) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:473) at iu.b(SourceFile:155) at com.mendix.core.Core.execute(SourceFile:187) at dx.execute(SourceFile:183) at jy.a(SourceFile:300) at jy.a(SourceFile:232) at jy.processRequest(SourceFile:183) at fA.a(SourceFile:75) at com.mendix.core.MxRuntime.processRequest(SourceFile:893) at com.mendix.m2ee.server.handler.RuntimeHandler.handle(RuntimeHandler.java:40) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1007) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:747) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:209) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.server.nio.BlockingChannelConnector$ConnectorEndPoint.run(BlockingChannelConnector.java:187) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:662)
asked
2 answers
3

It's an error you'll receive at the client side informing you that something went wrong with the web service call at the server side. To see more details about what went wrong, see the server log.

answered
1

As noted by Alexander, this signals that a fault was received by the webservice caller (a toplevel xml element that's called "fault", to be exact). If you don't have an error log, server-side, at the same timestamp, I suggest you turn on tracelogging for webservices so that you can pinpoint which messages are triggering this exception.

answered