So we're trying to monitor several web services, but some are failing due to the response exceeding a 1000 bytes limit:
URL: http://blah/blah/soap-service Content-Length not known but larger than 1000.
Does anyone know if there is a reason for this 1000 byte limit, and if there is any way to remove it?
Alternatively, is there an alternative to the SOAP Monitor Plugin?
Is this an exception thrown by the SOAP Monitoring Plugin when making the SOAP Call or is this the error that comes back from the Web Service you are testing?
I almost assume that this is a limit on your server-side web service implementation where your web or app server is not accepting a Content-Length > 1000. In that case you would need to talk with your Web service folks to figure out if they enforce such a limit on the service-side.
If this exception really comes from the monitoring plugin we need to look at the implementation. it is all available on GitHub + we can try to reach out to the author of the plugin.
Would you be able to post more details about this exception on this post? I am sure you find more info in the plugins log file which you can find on the collector where it gets executed
posted onto dropbox a fix to this plugin.
If you still get the error, it would be great to get more detail on the error. The SOAPMonitor log file would be particularly useful. Let me know if you don't know how to retrieve the log file.