Provisioning order using SOAP API failed on OSDM8.2 version due to Catch Null Pointer Exception (Doc ID 2594131.1)

Last updated on SEPTEMBER 28, 2021

Applies to:

Goal

Customer reported that after upgrade from OCSDM8.1 to OCSDM8.2, the post upgrade check failed while testing provisioning task such as add session-agent/delete session-agent etc.. using SOAP API

The Provisioning system reported following fault:

Server raised fault: 'Catch null pointer exception, possible it is caused by end user pass wrong attribute name'

You could check for the error details within NNC/SDM in the NorthboundSoapOut.log .
  
01/02 05:30:04.763 INFO [com.acmepacket.ems.ws.service.adminmgmt.AdminMgmtImpl] - Method: [login] Thread: [xyz] Msg:[Login user is abc; Login Feapp IP address=1.2.3.4; SessionId=ABCDEFGH]
01/02 05:30:04.970 ERROR [com.acmepacket.ems.ws.service.configmgmt.ConfigMgmtUtil] - Method: [getDeviceByName] Thread: [xyz] Msg:[Catch null pointer exception, possible it is caused by end user pass wrong attribute name]

Provisioning is working OK if done manually, but the issue is observed only when SOAP API is used for provisioning.

This error has not been encountered when running on OCSDM8.1 and it's introduced after the upgrade to OCSDM8.2.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.