Forum Discussion

arniehouston's avatar
arniehouston
New Member
5 months ago
Solved

WSS throwing NPE

I am trying to call a SOAP service running in my IDE on my local machine. It uses SSL and the messages must be signed/encrypted/timestamped.

Everything appears to be set up correctly and when invoking a method I get no SSL type error.

What I am getting is a WSS message:

java.lang.NullPointerException: Cannot invoke "String.length()" because "s" is null

Help! I have no clue here.

From the log.

2025-05-15 14:44:29,860 INFO  [SoapUI] Used java version: 17.0.12
2025-05-15 14:45:00,813 WARN  [DOMReference] The input bytes to the digest operation are null. This may be due to a problem with the Reference URI or its Transforms.
2025-05-15 14:45:00,935 INFO  [SoapUISSLSocketFactory] Initializing Keystore from [C:\Dev\oracle\weblogic12\user_projects\domains\mydomain\server-keystore.jks]
2025-05-15 14:45:01,218 INFO  [SoapUISSLSocketFactory] Initializing Keystore from [C:\Dev\oracle\weblogic12\user_projects\domains\mydomain\server-keystore.jks]
2025-05-15 14:45:02,060 INFO  [AbstractHttpRequestDesktopPanel] Got response for [ClassWebServicePortSoap11.LookupUser:Request 1] in 610ms (0 bytes)
2025-05-15 14:49:08,838 WARN  [DOMReference] The input bytes to the digest operation are null. This may be due to a problem with the Reference URI or its Transforms.
2025-05-15 14:49:08,915 INFO  [AbstractHttpRequestDesktopPanel] Got response for [ClassWebServicePortSoap11.LookupUser:Request 1] in 42ms (0 bytes)

  • Hi arniehouston​ 

    This particular NPE in the digest process is almost always due to a missing or mismatched Reference URI.

    Double-check that each reference in the signature refers to a real, non-null, and properly tagged element in the request.

    Matching IDs (wsu:Id) and configuration between your WSS profile and your actual SOAP message is critical

    Hope this helps - Happy to help further!!
    Thank you very much and have a great one!
    Warm regards

1 Reply

  • Humashankar's avatar
    Humashankar
    Icon for Champion Level 3 rankChampion Level 3

    Hi arniehouston​ 

    This particular NPE in the digest process is almost always due to a missing or mismatched Reference URI.

    Double-check that each reference in the signature refers to a real, non-null, and properly tagged element in the request.

    Matching IDs (wsu:Id) and configuration between your WSS profile and your actual SOAP message is critical

    Hope this helps - Happy to help further!!
    Thank you very much and have a great one!
    Warm regards