Service Virtualization

  • 1.  Unable to instantiate Crypto class

    Posted Sep 11, 2018 05:47 AM

    For one of our request in CA Devtest(10.2.4) we are getting the below response:

     

    <faultcode>soapenv:Server.generalException</faultcode>
    <faultstring>Unable to instantiate Crypto class; nested exception is:
     java.lang.NullPointerException; nested exception is:
     org.apache.ws.security.WSSecurityException: Unable to instantiate Crypto class; nested exception is:
     java.lang.NullPointerException</faultstring>

     

    Can some one please help me understand the meaning of this response

     

    Thanks and Regards

    Yugain Sharma



  • 2.  Re: Unable to instantiate Crypto class
    Best Answer

    Posted Sep 11, 2018 11:13 AM

    Hello Yugain,

     

    Are you using a keystore with WS Security?

    If yes, verify the path provided and try with different slashes (/ - \).

     

    You can also create a MAR info file for the test case or VSM by right click on the test case/VSM and select "Create MAR info file". Check whether security token details (keystore/jks files) are included in mari file. If not included, you can try to add those details manually or place the keystore in the PROJECT_ROOT/Data folder, update the step and recreate the mari file.

    Once you verify the keystore is available in the MARinfo file you can create the MAR file from mari (right click on mari file and select "Create MAR file").

    Once MAR file is created, you can run/deploy it.

     

    Hope it helps.

    Heloisa



  • 3.  Re: Unable to instantiate Crypto class

    Posted Sep 12, 2018 02:41 AM

    Hello Maria

     

    Thanks for the solution. The issue was with the path provided for keystore.

     

    Thanks and Regards

    Yugain Sharma



  • 4.  Re: Unable to instantiate Crypto class

    Broadcom Employee
    Posted Sep 14, 2018 03:08 AM

    Super !!!



  • 5.  Re: Unable to instantiate Crypto class

    Broadcom Employee
    Posted Sep 12, 2018 01:25 AM

    Hi Yugain

                  While you follow the advice of Heloisa, I just wanted to ask a question. Did you get the erroneous response for only a 'specific request' and you get valid response for all other requests ? In case if the problem remains even after Heloisa's suggestion, please kindly share your .VSI file.

     

    regards

    Sankar