Existing Webservice Returns "Error Invoking Web Service Dispatch java.lang.NullPointerException"
(Doc ID 2684196.1)
Last updated on AUGUST 01, 2023
Applies to:Oracle Transportation Management Cloud Service - Version 20.1 and later
Information in this document applies to any platform.
The outbound web service call returns an error on a random base, and we have to re-upload the WSDL Document again inside a new web service object, and reassign to the external system before it starts working again.
It's hard to reproduce. It seems to happen to any outbound call using web services (External Distance engine, external Service Engine or any other object that supports send integration via web services). When we re-upload the WSDL link, we create a new WSDL Document. We don't re-upload the existing one and are using URL storage.
It was noticed that the web service is being creating in PUBLIC domain - it should be created in a business domain. But we have also seen this error when the web service is created in a business domain.
When we face the issue we receive:
To solve it, we edit the Webservice, updated the time out from 1m into 1m 1sec and save the webservice again
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document