SOAP: error occured: java.io.IOException: invalid content type for SOAP

[former_member213666]

Hi gurus,

i have synchronus scenario with flow as  soap --> PI 7.31 java only --> proxy.

I am getting the below error in the message monitering.

Exception caught by adapter framework: java.io.IOException: Error receiving or parsing request message: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.

Any suggestions are appreciated.

[engswee]

Is the message protocol in the SOAP receiver channel using XI 3.0?

[former_member213666]

Hi Eng Swee Yeoh,

in my scenario sender is soap and receiver it is proxy. And yes for proxy

Adapter : soap

t/p :HTTP

M/p : XI 3.0

[engswee]

Can you provide screenshot of receiver SOAP/proxy channel?

[former_member213666]

Hi Eng Swee Yeoh..

please find the receiver channel screenshot below

[engswee]

Since you are using HTTP Destination, please provide configuration of the HTTP Destination in NWA

[former_member213666]

hi Eng Swee Yeoh,

please find the error mesage when i try to ping the http destination

[former_member182412]

Hi

HTTP 500 is valid for this destination check this thread

is the URL which you configured is like below??

http://<ecchost>:<ecc_http_port>/sap/xi/engine?type=entry

Regards,

Praveen.

[former_member213666]

Hi Praveen,

the URL which we maintained in NWA is same as you mentioned.

so the HTTP Destination error ..we dont have to bother?

in the link : https://scn.sap.com/thread/3328693

its mentioned like message paylaod might be empty..

please help

[former_member182412]

Hi

When you ping the channel you are not passing any payload so you are sending the empty payload that is why you are getting HTTP 500 with fault message from the service. you can ignore that error.

If your PI version support this, can enable TraceHTTP as shown in below

Regards,

Praveen.

[former_member213666]

Thanks a lot everyone for your assistance.

As you said the issue was at the proxy side. As the synchronous inbound proxy does not returning any response.we were getting this error.

[former_member213666]

Hi Bhavesh,

please find the logviewer message below.

Unable to call the caller service :

[EXCEPTION]

Failed to call the endpoint: null; nested exception caused by:

java.io.IOException: Error receiving or parsing request message: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.

at com.sap.aii.adapter.soap.ejb.XIHttpDestinationCallerService.callHttpPost(XIHttpDestinationCallerService.java:171)

at com.sap.aii.adapter.soap.ejb.XIHttpDestinationCallerService.call(XIHttpDestinationCallerService.java:58)

at com.sap.aii.af.sdk.xi.srt.TransportBubble.onMessage(TransportBubble.java:47)

at com.sap.aii.af.sdk.xi.srt.ExtensionBubble.onMessage(ExtensionBubble.java:60)

at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.callBubbleSequenceReceiver(XISOAPAdapterBean.java:1237)

at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:983)

at sun.reflect.GeneratedMethodAccessor4043.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)

at com.sun.proxy.$Proxy8408.process(Unknown Source)

at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)

at sun.reflect.GeneratedMethodAccessor4036.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)

at com.sun.proxy.$Proxy8343.process(Unknown Source)

at com.sap.aii.af.app.listener.AFWListenerBean.onMessage(AFWListenerBean.java:430)

at sun.reflect.GeneratedMethodAccessor4041.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)

at com.sun.proxy.$Proxy8326.onMessage(Unknown Source)

at com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(ServicesImpl.java:361)

at com.sap.aii.adapter.xi.ms.XIEventHandler$TRPProcessingBlock.process(XIEventHandler.java:1840)

at com.sap.engine.messaging.impl.spi.stage.ProcessorImpl.proceedToProcessingBlock(ProcessorImpl.java:101)

at com.sap.engine.messaging.impl.spi.stage.ProcessorImpl.proceedToProcessingBlock(ProcessorImpl.java:120)

at com.sap.engine.messaging.impl.spi.stage.ProcessorImpl.proceedToProcessingBlock(ProcessorImpl.java:120)

at com.sap.engine.messaging.impl.spi.stage.ProcessorImpl.proceedToProcessingBlock(ProcessorImpl.java:120)

at com.sap.engine.messaging.impl.spi.stage.ProcessorImpl.proceedToProcessingBlock(ProcessorImpl.java:120)

at com.sap.engine.messaging.impl.spi.stage.ProcessorImpl.processMessage(ProcessorImpl.java:72)

at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:485)

at com.sap.engine.messaging.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:74)

at com.sap.engine.messaging.impl.core.queue.Queue.run(Queue.java:1109)

at com.sap.engine.messaging.runtime.MSWorkWrapper.run(MSWorkWrapper.java:58)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

[former_member186851]

Hello PiUSER,

Check if the below note helps you

856597 - FAQ: XI 3.0 SOAP Adapter

Also ensure the user has the roles to hit the proxy, I mean ECC.

[bhavesh_kantilal]

Hello,

Please look at my previous reply,

- What is the output of your mapping. Is it valid in line with the ABAP Proxy?

- Is the Proxy class implemented on ECC

- Do you see the message in SXMB_MONI In ECC

- Did you check for any dumps in ECC in ST22 etc?

Unfortunately, all of these steps are needed to arrive at what could be wrong and need responses!

Regards,

Bhavesh

[former_member213666]

hi Bhavesh thanks a lot for responding...please find the message log below.

[bhavesh_kantilal]

So the error occurs when the message is sent to the ABAP Proxy.

Can you confirm if the ABAP proxy is generated in the target system and its associated implementation done?

A HTTP 500 on the ABAP proxy side typically tells me that the ABAP Proxy generation and implementation is not done.

Also check SXMB_MONI on your ECC system and see what happened there.

Do check ST22 ABAP Dumps as well.

If all seems Ok, try to execute the Proxy with the output of your mapping and see what happens there.

Regards,

Bhavesh

[bhavesh_kantilal]

In addition to what I have mentioned can you look at the Further Links Tab --> Log Viewer and share the error?

[bhavesh_kantilal]

- Where are you getting the error? In the Sender Channel or in the Receiver Channel?

- My guess here would be  that the issue is on the Receiver Proxy Channel. If yes, can you confirm the Proxy has been generated and corresponding implementation taken care of?

Regards,

Bhavesh