Skip to Content

mapping error with null pointer exception

Sep 25, 2017 at 06:34 AM


avatar image


We are facing an issue in SOAP to IDOC scenario. where in, out of 100 messages from third party system only few messages are getting failed with below mapping error:

MappingException: Mapping failed, NullPointerException: while trying to invoke the method of a null object returned from .

We don't see any payload in this message and they are not sure why these empty messages are coming to PI.

Is this the problem with PI or with third party system?

Please share your views on this.



10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Manoj K Sep 25, 2017 at 09:49 AM

This looks like a third party issue as there is empty payload it gets failed in your module level of soap adapter . DO check the content type too some times due to mismatch of content type PI interprets it as empty payload.



Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thanks Manoj for the reply.

We are getting this error for 1 or 2 messages out of 100. we are not able to get any clue from PI side to debug this.

Its SOAP to Proxy Async scenario.

Some transactions are happening from SAP to web service, in turn webservice is sending status of those transactions to SAP. While receiving the status from web service, this error is occurring.

Its pending since long time, request immediate help on this.



Vadym Diachenko
Sep 26, 2017 at 06:17 PM

As Manoj correctly noted getContentType method of interface has to return MIME type of message attachment. NullPointerException typically is being thrown by that method in case there is no main payload. I'd suggest you to sniff the network traffic incoming to network interface of PI machine and by comparing the timestamp of the error registered in PI discover whether the message sent from 3rd party sender system contained the actual payload.

If it did, then the problem can be localized in ICM instance or further on application level. Otherwise, the problem is with sender or, even possibly with network.

Best regards,

10 |10000 characters needed characters left characters exceeded