java.lang.IllegalArgumentException: faultCode argument for createFault was passed NULL

Document created by Nikita_nandakumar on Sep 15, 2014Last modified by dave_lesshafft on Mar 2, 2016
Version 2Show Document
  • View in full screen mode
For instance,

 

You may come across the below error when making a SOAP call :

 

"Error invoking soap operation; Caused by: java.lang.IllegalArgumentException: faultCode argument for createFault was passed NULL; Caused by: faultCode argument for createFault was passed NULL"
In this case, it seems like the endpoint webservice is returning an unknown faultCode.It could also mean an exception being thrown from the web server.

 

Please check the following :

 

1) Verify the field length validation :The illegal argument exception could be related to the maps and the elements within the profiles.There might be the Field Length Validation that is turned ON, and the Min Length or Max Length or both have no values.When the Field Length Validation is turned ON, it requires to have Min Length and Max Length set to some non-zero values.

 

2) Check the box 'Return Application Error Responses in the connector operation.
See if it generates a different error.

 

3) If the process is running on a local atom,try turn on the connector trace logging as described in the link below :

 

http://help.boomi.com/atomsphere/GUID-37E8BE48-29F4-40BD-B918-BA04629BEF1C.html

 

This will help you give more logging info at the connector level.

 

4) Set up  a CharlesProxy to see what the service is returning.You could also attempt to call the service from a tool like SoapUI to see what the service is returning.

Attachments

    Outcomes