Operation getFaultNode not supported by SOAP 1.1

The following message gets logged in our m2ee_log.txt file : 02 Apr 2012 9:56:06 AM com.sun.xml.messaging.saaj.soap.ver11.Fault11Impl getFaultNode SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1 And in our logs : 2012-04-02 09:57:53.094 TRACE - Webservices: Could not get fault node. 2012-04-02 09:57:53.094 TRACE Webservicesjava.lang.UnsupportedOperationException: Not supported in SOAP 1.1 at com.sun.xml.messaging.saaj.soap.ver11.Fault11Impl.getFaultNode(Fault1_1Impl.java:289) at bP.a(SourceFile:132) at kX.a(SourceFile:70) at eY.executeAction(SourceFile:105) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:49) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:436) at iA.b(SourceFile:155) at com.mendix.core.Core.execute(SourceFile:277) at com.mendix.core.Core.execute(SourceFile:252) at jI.a(SourceFile:286) at jI.b(SourceFile:137) at jI.a(SourceFile:91) at com.mendix.modules.webservices.WebserviceModule.handleWebserviceCall(SourceFile:430) at dN.processRequest(SourceFile:27) at fM.a(SourceFile:71) at com.mendix.core.MxRuntime.processRequest(SourceFile:946) at com.mendix.m2ee.server.handler.RuntimeHandler.handle(RuntimeHandler.java:42) 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) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:203) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:662) I don't know where, why or when this gets thrown, but it's been occurring in the m2ee_log file since we've upgraded to Mendix 2.5.8. Can anyone please shed some light on the issue? I assume it has something to do with calling a web service OR a web service being called. There is nothing to link it to a specific operation though, therefore analyzing it is a bit difficult. It also has no effect on how we are processing. Any help would be greatly appreciated. Thanx.
1 answers

This is nothing important, the server is just attempting to get the faultnode element in the xml (to obtain more error information) but this isn't supported in SOAP 1.1. It will throw an exception in that case but these are just logged. This is also only TRACE output so I'm not sure why you're seeing this unless you set your loglevels to TRACE.