Forum Discussion

GMSoapUI's avatar
GMSoapUI
Contributor
10 years ago

How to trace java.lang.NullPointerException error.

Can someone please tell me how to debug java.lang.NullPointerException errors? I have an automated solution written in groovy and every so often in the error log I get the line: ERROR:java.lang.NullP...
nmrao's avatar
nmrao
Champion Level 3
10 years ago

It is difficult to say unless there is more information like what is the reproducible steps along with soapui version, os etc.,

  • GMSoapUI's avatar
    GMSoapUI
    Contributor
    10 years ago

    Hi and thanks for your reply.

     

    The OS is Windows 7 Pro 64-bit.

    SoapUI version is 5.1.2

     

    The steps to reproduce are simply running my groovy script. It occurs several times throughout the script because the script loops through many test cases each of which contain several test steps. I know this may not be particularly helpful as you would need my entire project but my employer very likely won't let me share it due to it being intellectual property. I can ask.

     

    I find the user-friendliness of SoapUI to be quite poor especially when it comes to debugging things. It never tells you the script or the line number and this makes debugging nearly impossible. It would be great to have a full IDE within it.

     

    Regards

    • nmrao's avatar
      nmrao
      Champion Level 3
      10 years ago
      In general log files shows the error line of the groovy script, in my opinion. Have you checked soapui.log, soapui-error.log files?
      At least you could tell what script is doing, that would help to understand or post the script if possible.
    • nmrao's avatar
      nmrao
      Champion Level 3
      10 years ago
      If you are a pro user, then you must be able to use Ready API using the same license where groovy script has context sensitive help support like IDE.
      • GMSoapUI's avatar
        GMSoapUI
        Contributor
        10 years ago

        Hi Rao,

         

        Thank you for your reply again. Here is another example of how unhelpful I find the messages in the logs. In the SoapUI log I have this error:

         

        error_001.png

         

        So I do as it states and look in the error log for the details. That shows this:

         

        error_002.png

         

        There are no additional details. I don't have any idea what Script1 is as I have many scripts - why doesn't it refer to the script by the name I have given it? There is no line number anywhere, which would at least help. The variable it is complaining about *was* one I was using but I now no longer use it. I have searched every script individually for the variable in case I have a bad reference but the search string is not found in any script. Saying 'see error log for details' would be really helpful *if* there were some actual details rather than a repeat of what is in the SoapUI log. Do you understand the difficulties this is now presenting me with?

         

        I will take a look at Ready API as I'm disheartened with how hard simple debugging is in SoapUI Pro. It is costing me huge amounts of time to track down errors. I really don't want to have to switch products though.

         

        Thanks.

         

        Gary.