2 Replies Latest reply on Apr 20, 2018 3:21 PM by holper

    Caught type error - malformed XML returned as Tomcat server response!

    kobyq

      Hi guys

       

      I'm quite new to SAM, I've been trying to attache the "Tomcat Server" Application Monitor to my Apache Tomcat/7.0.54 instance.

       

      When I do and run a test, I get the error message "Caught type error - malformed XML returned as Tomcat server response!". I have checked the output of "http://myserver/manager/status/?XML=true" and can confirm that it is returning valid XML.

       

      Please help!

        • Re: Caught type error - malformed XML returned as Tomcat server response!
          Malik Haider

          Few weeks back i have a customer with same issue , I am not sure if you have the same exact issue however i am adding the findings below.

           

          We tried few changes however, responses from that server was very larger than usual and split into smaller chunks. And our Tomcat monitor is currently unable to handle such responses.

           

          We also try configuring other options, like "maxTrailerSize". But it looks like the only way to disable chunked responses is adding a call to "Response::setBufferSize()" directly in Tomcat code that provides the the response.

           

          We have finally created  a Feature request for supporting chunked responses from Tomcat.

          Unfortunately, I don't see any easy workaround except for using a Linux Script monitor and writing a new script that would collect the data.

           

          This feature request is still active with the development team .

           

          You might have many Tomcat servers where this script will work and with some it wont work as response received in chunks due to the response size depending on the server case.

           

          if you need more information about this feel free to contact Solarwinds Tech Support

          1 of 1 people found this helpful
          • Re: Caught type error - malformed XML returned as Tomcat server response!
            holper

            Hi,

             

            We checked with our developer and found that there is indeed an error in the XML delivery. We put the source code of the page (http://{$IP}:{$PORT}/manager/status/?XML=true) to validate in https://www.xmlvalidation.com/ and there indicated the error.