0

We have a web service that uses a complex input type. We created the mapping for the web service (domain-to-XML) and used this in the webservice call in a microflow. When the microflow contains the web service call function the complete server will no longer start (Mendix version 2.5.3 and 2.5.4). The server will return the error: Request action: start Message: Starting MxRuntime failed. Cause: Webservice must not be null Stack trace: com.mendix.m2ee.api.AdminException: Starting MxRuntime failed. at com.mendix.core.MxRuntime.z(SourceFile:257) Caused by: java.lang.IllegalArgumentException: Webservice must not be null at dD.<init>(SourceFile:20) at com.mendix.core.MxRuntime.J(SourceFile:690) at com.mendix.core.MxRuntime.A(SourceFile:303) at com.mendix.core.MxRuntime.z(SourceFile:252) at com.mendix.core.MxRuntime.a(SourceFile:234) at lz.execute(SourceFile:54) at com.mendix.m2ee.server.handler.AdminHandler.handle(AdminHandler.java:84) 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.headerComplete(HttpConnection.java:992) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:550) When using a simple webservice (input type is string and output as well) all works fine. Any ideas what is happing here would be greatly appreciated. This issue is caused by the webservice containing a custom authentication in the wsdl definition. Updating the header part of the MF webservice call with a custom header will allow the server to start again.

asked 2011-05-02

0 answers