SOAP Axis Receiver adapter - adapter is null exception

[Former Member]

Hi All

We are using SOAP (Axis) Receiver adapter to connect to a MS webservice. Below is the configuration of the adapter.

Adapter Type: SOAP

Transport Protocol: HTTP (Axis)

Message Protocol: Axis

Adapter Engine: Integration Server

SOAP Version: 1.1

Ecapsulaqtion Format: MIME

Version Apache Axis version: 1.4

I deployed the file aii_af_axisprovider.sda and the http://host:port/XIAxisAdapter/MessageServlet status is OK.

Processing Sequence: [Did not make chagnes to Standard processing sequence]

AF_Adapters/axis/AFAdapterBean Local Enterprise Bean afreq

AF_Adapters/axis/HandlerBean Local Enterprise Bean xireq

AF_Adapters/axis/HandlerBean Local Enterprise Bean trp

AF_Adapters/axis/HandlerBean Local Enterprise Bean xires

AF_Adapters/axis/AFAdapterBean Local Enterprise Bean afres

Module Configuration

trp handler.type java:com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender

trp module.pivot true

xireq handler.type java:com.sap.aii.axis.xi.XI30OutboundHandler

xires handler.type java:com.sap.aii.axis.xi.XI30OutboundHandler

This configuration was working for a long time and suddenly it stopped working. We are getting the below error.

We did not make any chagnes to the Server or the Communicaiton channels in the mean time. It just Stopped working...

 Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: org.apache.axis.ConfigurationException: adapter is null org.apache.axis.ConfigurationException: adapter is null at com.sap.aii.adapter.axis.modules.HandlerCore.process
at com.sap.aii.adapter.axis.modules.HandlerBean.process HandlerBean.java:88 at sun.reflect.GeneratedMethodAccessor314.invoke

We cannot use HTTP REceiver adapter instead of SOAP Axis adapter as suggested int eh below thread b'cos the target webservice needs NTLM authentication which is supported only by SOAP-Axis Adapter.

Regards,

Siva Maranani

[Former Member]

Dear Siva

we are facing the same issue

did u manage to solve it ?

thanks

Shai

[Former Member]

Hi Siva,

just like Sunil said, you can check the channel monitor.

If the error history from the channel startup is already gone, you can just stop and start the channel This should either write an error entry (if the problem is permanent, for example, some missing library) or an OK entry (if the problem was temporarily caused by some internal technical issue like a cluster communication problem).

Once the channel is successfully started, you can send messages.

If the channel is started with some error. The error text typically tells you what is wrong with the channel.

If you are not sure if you have packaged everything correctly, go check the axis adapter deployment page. For your NTLM case, you also need some optional components. You get this information from the axis adapter FAQ note and probably from the blog you referred to.

Good luck

Best regards, Yza

[sunil_singh13]

Siva,

Error is saying that it is due to some Configuration issue. Can you check the history of Communication channel if there is Version created for this communication channel, if there are then select the one(date) during which it was working and try to re run. If it doesn't help then I would suggest to redploy it as you haven't done any customization to the communicational channel and I think this would be faster approach(you just need to deploy the adapter which is hardly 10 min work).

Thanks,

Sunil Singh