Web Service Job ends with Null Pointer Exception

book

Article ID: 84992

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
+++++++++++++++++++++++++++++++++++++ Start of Runtime Exception ++++++++++++++++++++++++++++++++++++
java.lang.NullPointerException: Cannot get property '_serviceClient' on null object
at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:56)
at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:156)
at org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java:44)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:235)
at SOAP.runJob(WebService.groovy:3970)
at com.uc4.extensibility.types.CITAgent.dispatchJob(CITAgent.java:258)
at com.uc4.ex.cit.CITJob.execute(CITJob.java:179)
at com.uc4.ex.Job.run(Job.java:469)
at com.uc4.ex.ThreadPool$RunnableDecorator.run(ThreadPool.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
++++++++++++++++++++++++++++++++++++++ End of Runtime Exception ++++++++++++++++++++++++++++++++++++++

A Web Service job ends with a NullPointerException: Cannot get property '_serviceClient' on null object and the above mentioned Error Message.

Cause

Cause type:
Defect
Root Cause: RA WebService Agent v3 uses Axis2 framework which causes the problem.

Environment

OS Version: N/A

Resolution

Update to a fix version listed below or a newer version if available.

The issue is fixed with RA Webservice Agent Solution Soap v4.1 which is compatible with Automation Engine 12. 

There won't be a fix for RA Web Service Agent v3 because the RA Web Service Agent v3 uses Axis2 framework that causes the problem. 

For obvious reasons we can not change the framework for a released major version as this would bring in incompatiblity changes and therefore conflict with our release policy. 

The RA SOAP Web Service Solution v4.1 Agent is not dependent upon any framework because it uses a native mode therefore the issue can't be reproduced with this Agent version. 

 

Fix Status: Released

Fix Version(s):
RA WebServiceSolution SOAP 4.1 - Available

Additional Information

Workaround :
Two available options: 
  1. The Automic preferred option: Upgrade the system to Automation Engine v12 and the RA Web Service Agent v4.1.
Or
  1. Use an alternative tool like Microsoft Web Services Description Language Tool (Wsdl.exe) - https://msdn.microsoft.com/en-us/library/7h3ystb6(VS.80).aspx