SOAP Fault AXIS 2 problem

[Former Member]

Hello,

We have SAP PI 7.1 scenario where 2 nonSAP systems exchange messages. It is synchronous scenario where we use SOAP AXIS. Scenario is:

GIS <-> SAP PI <-> MAXIMO

Sending system is GIS, receiving system is MAXIMO. After message is sent from GIS to SAP PI, SAPI PI executes mapping and send mapped message to MAXIMO through channel (adapter Type SOAP, Message protocol AXIS). After message is received by MAXIMO, message is checked and if there is something wrong with message or MAXIMO is not able to process the message (wrong data), MAXIMO sends Exception in SOAP Fault message through AXIS 2 Framework. Just to explain: MAXIMO is IBM's Asset Management System which in verion 7.0 supports only AXIS 2 as a message protocol for SOAP.

Problem is: When SAP PI receives Fault (Exception) then in SXMB_MONI is error:

com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException

Interesting is: when regular Response message from MAXIMO is send, SAP PI receives response correctly and message is mapped and send back to GIS, but for Fault message from MAXIMO which is generated by same framework( AXIS2) in MAXIMO, SAP PI is not even able to receive Fault message correctly and own exception is thrown - com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException

I found note (1039369) regarding AXIS where it is explicitly stated that AXIS 2 is not supported, but how come Response generated by MAXIMO (by MAXIMO's AXIS 2 framework) is correctly received and Fault Exception generated by the same MAXIMO's AXIS 2 framework doesn't ?

Screenshot from AXIS Adapter Message Servlet says( you can see also adapter version and AXIS version (1.4) - latest AXIS 1 edition :

Axis Adapter Message Servlet

Component Versions

Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)

Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)

Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)

Required Components

Apache-Axis

Found: org.apache.axis.AxisEngine at /usr/sap/XID/DVEBMGS00/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/axis.jar

Jakarta-Commons Discovery

Found: org.apache.commons.discovery.Resource at /usr/sap/XID/DVEBMGS00/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-discovery-0.2.jar

Jakarta-Commons Logging

Found: org.apache.commons.logging.Log at /usr/sap/XID/DVEBMGS00/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-logging-1.1.jar

Number of Missing Components: 0

Status: OK

Is there any way to make also Fault message generated by AXIS2 correctly receive in SAP PI ? Or is there any workaround ? Or is this bug from SAP which is fixed in higher version of SPS (patch) of XIAF framework ?

I appreciate any hint or comment or finally solution.

Many thanks

Iv

[baskar_gopalakrishnan2]

Here are my few cents.

You are consuming third party (Maximo) web service using PI SOAP receiver adapter using Axis. Do the following steps.

I suspect problem occurs in the fault message mapping. Nothing related to PI or AXIs upgrade or more.

a)Test outside PI.

Import Maxima WSDL in SOAPUI or XMLSPY and try to simulate fault message as response from MAXIMO and see you get the same null pointer exception

b)WHen you import WSDL , you will see Maximo's fault message and I believe you map that fault message to sender fault message.

c) This might be problem at their side, while populating fault message data in their side, they may run into null pointer exception.

Null pointer exception would cause if you invoke a variable or object that has no value or null.

[Former Member]

HI,

Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:

Patch level of XIAF:

1. customers SAP PI level is

Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)

Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)

2. our SAP PI level is

Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)

Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)

Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)

Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.

What do you think ?

Thanks