3 Replies Latest reply: Jul 23, 2014 2:56 AM by Erik Gustafsson RSS

    Heap space problem when scenario run 2nd time with scalability tool

      I am trying out the Scalability Tool for benchmarking. I ran a test scenario successfully this morning (2 concurrent users; 2 iterations). When I ran it again later, I got a "could not reserve enough space for object heap" error. I rebooted and tried again and the same error. What should I be looking for?

       

      Thanks,

       

      Wood

        • Re: Heap space problem when scenario run 2nd time with scalability tool
          Erik Gustafsson

          Hi Wood,

           

          Sounds like you are configuring it wrong, have you read the manual on how to configure this properly?

          Do you have enough resources for this?

           

          Regards,

          Erik

            • Re: Heap space problem when scenario run 2nd time with scalability tool

              Hi Erik,

               

              Thanks for your reply. Errors I saw in the Jmeter log file were:

               

              2014/07/17 08:04:02 ERROR - jmeter.protocol.http.sampler.HTTPSampler: readResponse: java.io.IOException: Authentication failure

               

              2014/07/17 08:04:02 ERROR - jmeter.protocol.http.sampler.HTTPSampler: Cause: java.io.IOException: Authentication failure

               

              2014/07/17 08:04:02 ERROR - jmeter.util.XPathUtil: Type=Val=false Tol=false org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.

               

              2014/07/17 08:04:02 ERROR - jmeter.util.XPathUtil: Type=Val=false Tol=false org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.

               

              2014/07/17 08:04:02 ERROR - jmeter.util.XPathUtil: Type=Val=false Tol=false org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.

               

              but the Scalability UI says “could not reserve enough space for object heap”. Nevertheless, I was able to run the tool again later without making any Jmeter changes.

               

              I’m beginning to suspect that it is User Account Control issues which I’m under the impression that the system may reset from time to time. In that case, the message in the Scalability UI would have been misleading.

               

              Thanks,

               

              Wood