AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode

0
We are getting this error every 15 minutes in our logs. The log nodes are all on info (so not trace). And the funny part is that this is a webservice between a V4 cloud and a V3 cloud so all Menidix. I saw these posts: https://community.mendix.com/link/questions/89178 and https://community.mendix.com/link/questions/3672 But again as said the have all logs on info. Anybody a guess why Mendix would return these errors? Regards, Ronald   2019-07-01T00:00:17.472993 [APP/PROC/WEB/0] jul 01, 2019 12:00:17 AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode 2019-07-01T00:00:17.473012 [APP/PROC/WEB/0] SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1 2019-07-01T00:15:26.644066 [APP/PROC/WEB/0] jul 01, 2019 12:15:26 AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode 2019-07-01T00:15:26.644077 [APP/PROC/WEB/0] SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1 2019-07-01T00:30:27.593174 [APP/PROC/WEB/0] jul 01, 2019 12:30:27 AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode 2019-07-01T00:30:27.593186 [APP/PROC/WEB/0] SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1 2019-07-01T00:45:02.571568 [APP/PROC/WEB/0] jul 01, 2019 12:45:02 AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode 2019-07-01T00:45:02.571589 [APP/PROC/WEB/0] SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1 2019-07-01T00:45:04.509113 [APP/PROC/WEB/0] jul 01, 2019 12:45:04 AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode 2019-07-01T00:45:04.509127 [APP/PROC/WEB/0] SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1 2019-07-01T00:45:04.910984 [APP/PROC/WEB/0] jul 01, 2019 12:45:04 AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode 2019-07-01T00:45:04.910995 [APP/PROC/WEB/0] SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1 2019-07-01T00:45:05.666969 [APP/PROC/WEB/0] jul 01, 2019 12:45:05 AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode 2019-07-01T00:45:05.666992 [APP/PROC/WEB/0] SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1 2019-07-01T00:45:07.881890 [APP/PROC/WEB/0] jul 01, 2019 12:45:07 AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode 2019-07-01T00:45:07.881905 [APP/PROC/WEB/0] SEVERE: SAAJ0303: Operation getFaultNode not supported by SOAP 1.1 2019-07-01T00:45:08.225512 [APP/PROC/WEB/0] jul 01, 2019 12:45:08 AM com.sun.xml.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultNode [EDIT] Received message from Mendix support: This will be fixed in Mendix Studio Pro 8.18.2 and 9.0.4
asked
2 answers
0

Does this thread answer your question? The answer seems to be that it's not important, but if you see those messages, you could have a log node set to trace.

answered
0

Hi everyone,

we are also receiving a lot of these errors since migrating to cloud V4. I received the message from Mendix support:

‘The SEVERE log node is not from Mendix we use only below listed log levels. This could be a custom log node. Do you have custom (Java) code that calls SOAP services?
https://docs.mendix.com/howto/monitoring-troubleshooting/log-levels#level ‘

We are currently investigating what could be the cause of it. Also, I want to add, that all of our log levels are also set to INFO, and we are live in production for more than 5 years, and this is the first time that we noticed this log level. Of course, stack trace does not exist, so currently we are ‘assuming’ which webservices might cause this, and debugging processes in order to get more information.

In the meantime, did you find out anything else that can light up our analysis :) ?

Thank you in advance!

answered