Our published webservice in Mendix is called by several third parties during the day. Some of these requests fail with a webservice exception / soap fault and then we need the request to reproduce the error. Is there a way to log the initial raw request and delete it when the call is successfully handled? So if there is something wrong with the webservice call, we want to find the raw request. If the call is handled without an error, we don't need the raw request. By tracing the log level node 'Webservices' we're able to log the raw request, but that means every request is logged. That would be too much information, considering the fact that the webservice will be called more than thousand times a day. Anyone with a proper solution / pointers to an approach?
asked
Samet Kaya
2 answers
1
You could write a custom log handler, log web services on trace on that handler and delete the log message afterwards when the request went ok.
answered
Sebastiaan van den Broek
1
I believe that the only way to really achieve this is set the log level of webservices to trace. Or perhaps you could build a custom request handler on /ws2 that logs any incomming data to some request entity and then redirect that call to /ws. Basically you are building a proxy.