cancel
Showing results for 
Search instead for 
Did you mean: 

Exception: object is null in SOAP Receiver Adapter after SP11 PI 7.1

Former Member
0 Kudos

Hi Experts,

We executed one support package (from 7.1 SP7 to SP11). Before executing this procedure all TMS interfaces were

running well.

It wasn't executed any change in the code from interfaces, because we believe the support package impacted some configuration, parameter and etc.

We verified the transactions: SXMB_ADMIN, SM59, SXI_CACHE and we deployed the AXIS again but the error persists.

We developed 4 interfaces: 3 Synchronous and 1 Asynchronous, all using SOAP adapter receiver.

It's presenting the following message error in RWB and SXMB_MONI:

"com.sap.engine.interfaces.messaging.api.exception.MessagingException:

java.lang.IllegalArgumentException: object is null"

Do you have an idea, where is the problem?

Best Regards,

Daniela

Accepted Solutions (0)

Answers (1)

Answers (1)

Romerito
Explorer
0 Kudos

HI Dani,

I was looking for this error and I found this post . This post says about other errors, but sugests many ideas to found the soluction, like:

1- non-deployed all AXIS jars; (but in this case it deployed all)

2- Exists this note for one erro in AXIS: (https://service.sap.com/sap/support/notes/1028961).

3- this document (http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f) that have sets for header parameters. This is interesting becouse one of this parameters is obligatory but isn't filled, can occur error like "null object".

By the way, you can check if have update to AXIS (http://ws.apache.org/axis/), becouse isn't a SAP application and in other systems can have this error.

I hope this helps,

Romerito Silva

Romerito
Explorer
0 Kudos

I found this FAQ (https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1039369) about AXIS using in PI SOAP Adapter.

10. I am getting org.apache.axis.ConfiguraitonException: adapter is null

You may see this exception in the stack trace part of the returned SOAP fault detail or in the channel process status or messaging monitors. This error indicates that the channel has not been initialized correctly. This problem can potentially occur in two situations. 1) the initialization of the Axis channel was invoked but the handler was not instatiated or 2) the initialization of the Axis channel was not triggered by the SOAP adapter. For the first case, you can try to restart the channel manually. This will show some error indicating why the handler could not be instantiated. For the second case, which may only occur when the affected Axis channel is hosted by the SOAP adapter, you can restart the SOAP adapter application.

Former Member
0 Kudos

Hi Romerito,

Thanks for your findings.

We'd tried already the procedures you've mentioned and as we didn't suceed on fix the issue, we opened a ticket to SAP.

As soon as I have any news, I will update this thread.

Until there, any help will be wellcome.

Best Regards,

Daniela