SOAP: call failed: java.io.IOException

Hi gurus,
I was executing several stress-tests for an interface between to non-SAP systems over PI, that both use async SOAP adapter communication.
The requirement is to transfer up to 70mb files with single files. I executed the tests successfully with a 50MB message size and lower, and then I tried with a 70MB message, but the message failed and got this error in the adapter log:
SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
I believe this is coming from the adapter itself and not from the receiving system. I have checked the binary message data from the messaging system and it looks perfectly fine.
Any ideas why this is happening? Is there a limitation for message sizes with the SOAP adapter?
I also checked the messaging system configuration settings in the AS Java but could not find anythig related to the SOAP adapter.
Thanks in advance.
Regards,
S. Gökhan TOPÇ

Hi Gokhan,
I believe this is coming from the adapter itself and not from the receiving system. I have checked the binary message data from the messaging system and it looks perfectly fine.
I believe this is a client-side error, as your request was not properly addressed and the SOAP service was not reached.
Any ideas why this is happening? Is there a limitation for message sizes with the SOAP adapter?
Well, SAP's message size limit is huge but a lot depends on your receiving server's capabilities and network connections. So, you might not be able to reach the SAP's tested message size. In my project, I am able to do a max of 55 megs through SOAP.
Hope this helps.
regards,
Neetesh

Similar Messages

SOAP: call failed: java.io.IOException: unable to create a socket ??

Hi
I am getting the following error in PI for one of my sync interfaces.
SOAP: call failed: java.io.IOException: unable to create a socket
The interface works most of the time, but i get this error couple of times a day.
Regards,
XIer

Hav you able to resolve this issue? Please let me know what was cause of this "unable to create a socket"
Thanks,
Sagar

Error SOAP: call failed: java.io.IOException: Read timed out; HTTP 200 OK

Hi PI gurus,
Need some suggestions on one issue below -
Scenario - proxy (SAP) to SOAP (Web based system)
In the RWB Communication Channel Monitirong we are receiving the below error
" Error SOAP: call failed: java.io.IOException: Read timed out; HTTP 200 OK"
the request from XI system is going to target system and printing the lables (as per the functionality) with no issues but the comminication channel is giving the above error and this is causing the repeated sending the same request to target sytem and the data is printing repeateadly. This issues is occuring in Quality environment.
Strangley the same Interface with the same connectivity details is working fine in Development environment. But not working in Quality environment. Checked the firewalls settings on both in XI and Target system side and confirmed that everything is fine.
Below are the Logs both from Quality and developement are as follows
Quality ( Failure Case)
17.03.2011 07:19:59 Success SOAP: request message entering the adapter with user J2EE_GUEST
17.03.2011 07:25:03 Error SOAP: call failed: java.io.IOException: Read timed out; HTTP 200 OK
Development (Success ful)
17.03.2011 07:27:55 Success SOAP: request message entering the adapter with user J2EE_GUEST
17.03.2011 07:27:58 Success SOAP: completed the processing
When we checked with basis team on user id J2EE_GUEST, they confirmed that they are same in Development and Quality.
I repeat,, that the same target url and everthing is same in XI Configuration
Thanks in Advance. Points would be rewared for the best solution.
Thanks,
Jitender

HI Jitender,
If your scenariois working in DEV and if it is not working in QAS.Could you please check if both the systems are at same patch levels..
Please refer below notes :1551161,817894,952402.
Cheers!!!
Naveen.

SOAP: call failed: java.lang.NullPointerException

Hi,
We are geeting the error in RWB -->
SOAP: call failed: java.lang.NullPointerException
We checked the communication channel and interface and all are working fine.
Can anybody suggest?
Regards,
Akki..................

Hi,
use this link to find the answer..
SOAP adapter
Regards,
Amitanshu

SOAP: call failed: java.io.EOFException

Hi all,
I have build a proxy to soap scenario that generates errors during runtime. The scenario
consists of an ABAP program consuming a webservice through PI. The communication
channel shows the following errorlog:
- Message processing started
- request entering
- SOAP: call failed: java.io.EOFException: Connection closed by remote host.
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.
MessagingException: java.io.EOFException: Connection closed by remote host.
Does anyone know the cause of this error?
Thanks in advance.
Regards,
Ivo

Hi Ravi,
although I was able to reach the URL through a webbrowser, this problem was indeed caused by unavailability of the webservice. I just tried the connection without making any changes in PI and everything is working fine now.
Case closed.
Regards,
Ivo

SOAP: call failed: java.io.EOFException: Connection closed by remote host

Hi folks,
my friday crusher:
We have a sync RFC-PI-SOAP scenario.
All is working fine in Dev system.
After moving into Test following error is displayed as the SOAP response message:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.EOFException: Connection closed by remote host.</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also Channel Monitoring says:
Message-Verarbeitung fehlgeschlagen. Grund: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.EOFException: Connection closed by remote host.
Couldn´t find any hints in SDN and the web to this issue.
Does anyone of you has made experiences with that problem?
Maybe it´s a system parameter for time out SOAP connections....?
Many thanks for your help
-and-
have a great weekend!
Cheers
André

Very strange!
But I have the solution:
I have looked into channel monitoring / RWB again.
There I saw, this PI is using two clusters on two application servers.
Everytime the SOAP call is executed through the frist cluster, all was fine.
But no SOAP call was successfully executed by the second cluster.
Fortuity? No!
The second cluster node / app server wasn´t registered for internet access in the used proxy server.
So it wasn´t an PI issue.
Now, all is fine & I´m happy!
Thanks @all for helping!
Cheers,
André

SOAP Receiver adapter error. SOAP CALL Failed

Hi ,
I am implementing scenario R/3->RFC adapter->XI->SOAP REceiver adapter->Web Service (Synchronous). I am getting the error.
SOAP: call failed
SOAP: error occured: java.net.ConnectException: Connection timed out
Message log is as below.
Any clue ?
Thanks & Regards,
Mathew
2005-10-31 18:59:58
Success
output
1130810398454
The message was successfully received by the messaging system. Profile: XI URL: http://host:Port/MessagingSystem/receive/AFW/XI
2005-10-31 18:59:58
Success
output
1130810398458
Using connection AFW. Trying to put the message into the request queue.
2005-10-31 18:59:58
Success
output
1130810398458
Message successfully put into the queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message was successfully retrieved from the request queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message status set to DLNG.
2005-10-31 18:59:58
Success
output
1130810398460
Delivering to channel: CC_CALCULATOR
2005-10-31 18:59:58
Success
output
1130810398564
SOAP: request message entering the adapter
2005-10-31 19:03:07
Success
output
1130810587497
SOAP: call failed
2005-10-31 19:03:07
Error
output
1130810587497
SOAP: error occured: java.net.ConnectException: Connection timed out
2005-10-31 19:03:07
Error
output
1130810587498
Exception caught by adapter framework: Connection timed out

Hi Mathew,
Check if the webservice is availble??? Based on the error below, it looks like the message is timing out at the Adapter Engine level waiting for the connection to make the webservice call...
Prasad

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

Hi,
We are implementing an XI scenario as follows: Mail Adapter->XI->SOAP Receiver.
Basically, we pass the XML File attachment from the Mail Adapter through XI to the SOAP Adapter. However, we keep getting the following error:
SOAP: error occured: java.io.IOException: invalid content type for SOAP: TEXT/HTML
Any ideas on where we could look to fix this problem?
Thanks,
EC

People,
most of errors like that are 401 (unauthorized), 403 (forbidden), 404 (not found) and so on. To be sure, check the message content that comes back from the webservice, in the Message Monitoring.
Obs: To visualize sync messages payload in Message Monitoring, you'll have to set the Messaging.syncMessageRemover.removebody parameter to false (default is true) in SAP XI AF Messaging service, in the Visual Administrator.
Regards,
Henrique.

Error in SOAP receiver channel: java.io.IOException: invalid http response:

Hi experts,
I have a IDOC to SOAP scenario where SOAP receiver channel is sending data to web service. In the receiver channel I am getting error as below. Kindly help me to resolve this issue. Thanks.
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null"

Did you check this?
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Regards
Pothana

Axis Client Web Service call problem: java.io.IOException: Stream closed

Hi, I tried to call a webservice from Axis Client, and I encounter the following error. Do you guys have any idea what actually happens?
Please help, I am newbie in web services.
==============Root Cause===============
AxisFault
faultCode: { h t t p : / / schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.io.IOException: Stream closed
faultActor:
faultNode:
faultDetail:
     {h t t p : / / xml.apache.org/axis/}stackTrace:java.io.IOException: Stream closed
     at java.io.BufferedInputStream.ensureOpen(BufferedInputStream.java:120)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:270)
     at org.apache.commons.httpclient.ContentLengthInputStream.read(ContentLengthInputStream.java:170)
     at java.io.FilterInputStream.read(FilterInputStream.java:111)
     at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:108)
     at java.io.FilterInputStream.read(FilterInputStream.java:90)
     at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:127)
     at org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.java:688)
     at org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(HttpMethodBase.java:796)
     at org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:224)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:2443)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
     at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
     at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
     {h t t p : / / xml.apache.org/axis/}hostname:compname
java.io.IOException: Stream closed
     at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
     at org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:301)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:2443)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
     at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
     at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
Caused by: java.io.IOException: Stream closed
     at java.io.BufferedInputStream.ensureOpen(BufferedInputStream.java:120)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:270)
     at org.apache.commons.httpclient.ContentLengthInputStream.read(ContentLengthInputStream.java:170)
     at java.io.FilterInputStream.read(FilterInputStream.java:111)
     at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:108)
     at java.io.FilterInputStream.read(FilterInputStream.java:90)
     at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:127)
     at org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.java:688)
     at org.apache.commons.httpclient.HttpMethodBase.getResponseBodyAsString(HttpMethodBase.java:796)
     at org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:224)
     ... 17 more I am calling through proxy, the setting is as follows:
            System.setProperty("https.proxyHost", [proxyname here]);
            System.setProperty("https.proxyPort", [proxyport here]);
            System.setProperty("http.proxyHost", [proxyname here]);
            System.setProperty("http.proxyPort", [proxyport here]);

Are there any problems showing up in the server's log?

Build Failed: java.io.IOException: CreateProcess

Hi,
Would someone help me on my problem. I had encountered a "java.io.IOException: CreateProcess" when the ant script was about to execute the lines below:
<java classname="AllTests" fork="true" failonerror="yes">
 <classpath>
 <path refid="all.classpath" />
 <path refid="emma.coverage.classes" />
 <pathelement location="${emma.instr}" />
 <pathelement location="${classes.temp}" />
 </classpath>
 <jvmarg
 value="-Demma.coverage.out.file=${emma.coverage}/coverage.emma" />
 <jvmarg value="-Demma.coverage.out.merge=true" />
</java>
The result and the message was stated below.
BUILD FAILED
C:\RAD901\build\emma-build.xml:89: java.io.IOException: CreateProcess: "C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6\java\
jre\bin\java.exe" -Demma.coverage.out.file=C:\RAD901\build/temp/emma/coverage/coverage.emma -Demma.coverage.out.merge=true -classpat
h "C:\RAD901\build\libs\XmlWriter.jar;C:\RAD901\build\libs\cactus1-6\aspectjrt-1.1.1.jar;C:\RAD901\build\libs\cactus1-6\cactus-1.6.1
.jar;C:\RAD901\build\libs\cactus1-6\cactus-ant-1.6.1.modified.jar;C:\RAD901\build\libs\cactus1-6\commons-codec-1.3.jar;C:\RAD901\bui
ld\libs\cactus1-6\commons-httpclient-3.0.1.jar;C:\RAD901\build\libs\cactus1-6\commons-logging-1.0.3.jar;C:\RAD901\build\libs\cactus1
-6\httpunit-1.5.4.jar;C:\RAD901\build\libs\cactus1-6\nekohtml-0.7.4.jar;C:\RAD901\build\libs\catalina.jar;C:\RAD901\build\libs\com-d
arwinsys-util.jar;C:\RAD901\build\libs\commons-pool-1.4.jar;C:\RAD901\build\libs\db2jcc.jar;C:\RAD901\build\libs\db2jcc_license_cu.j
ar;C:\RAD901\build\libs\emma.jar;C:\RAD901\build\libs\hapi-0.5.1.jar;C:\RAD901\build\libs\jboss-common.jar;C:\RAD901\build\libs\jstl
-1.0.jar;C:\RAD901\buil
The result was incomplete. I don't know why, but I would like to know the cause of my exception. I hope somebody could help me.
Thank you so much in advance.

Hello all,
I'm having almost the same issue related to error message when I hit a button on my manufacturing software.
*"ScriptException: Error in exec: java.io.IOException: CreateProcess*
*exec(C:\\progra~1\\intern~1\\iexplore.exe http://cbweb4:81/barcode/CMbombyorder.asp\u003FR2=P&T2=12875424-P")*
This is when I hit a button that works for us to show this webpage I wrote previously. Last week we didnt have this issue, this just started this morning and I dont know what do to, it shows something about JAVA, that's why I'm asking to you guys, I dont know if you could please enlight me a little bit.
Thanks in advance.

SOAP: call failed: invalid content type for SOAP: TEXT/HTML

Scenario: Idoc(R3) - -> XI (BPM) <-> webservice
I have tested the web service through a browser and XMLSPY, and this works.
There are no firewall issues.
I have used the TCPGateway to trace the messages. I receive the following error:Connection refused: connect
What is the problem?
Why can I call the web service through a browser/XMLSPY and not through the SOAP adapter?
Best Regards
Niels Færch

Ref: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
First verify your address. it can cause the invalid content type for SOAP: TEXT/HTML error
I have used the TCPGateway to trace the messages. I receive the following error:Connection refused: connect
>> also check if your network has a proxy. in that case you wud need to provide that details in your SOAP adapter

SOAP Call Failed

Hi All,
Please help me in the below issue.
I am using SOAP addapter
Trasnport protocal: HTTP
Message Ptotocal: XI 3.0
Addressing Type:HTTP Destination
HTTP Destination : XXXX --> this was configured in the PI.
Connecton type: H
HTTP Connection to ABAP System
Message was sucessufully from PI and I am able to see the message in the PI MONI, but the message was not reaching the ECC.
While checking the Channel I am facing the below issue.
SOAP tried to access destination XXX of type HTTP which does not currently exist in the destination server.
You can create destinations in the NWA under configuration management infrastructure-destinations
Kindly suggest me the solution.
Thanks & Regards,
Mahi

Hi,
PI 7.3
Input File Type: File
Output File type: Proxy
3rdparty --> pi --> to ECC
SFTP in the sender side of the 3rd party
SOAP is the connectivity between the system UPXI and PI
ECC --> SOAP
Trasnport protocal: HTTP
Message Ptotocal: XI 3.0
If you need any further deatils please let me know.
Mahi

** SOAP to SOAP call - HTTP 404 not found - invalid content type

Hi friends,
We have one scenario SOAP to SOAP call. It is synchronous interface. We are calling the WSDL.
For some of the messages (not all), we are getting the error in SXMB_MONI
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found
In the sender & receiver SOAP communication channel also, same error : SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found
Friends, this error is not coming for all messages. For some of the messages it is coming. For example,
10:50 - Message Processed Successfully
10:54 - Message Processed Successfully
10:59 - Error
11:05 - Message Processed Successfully
By looking threads and blogs, I implemented MessagesTransformBean in the receiver CC and added the parameter Transform.ContentType as 'text/xml;charset=utf-8'.
After implementing this also, error is coming for some of the messages.
Can you kindly clarify friends, what could be the problem?
Kind regards,
Jegathees P.

I'm in agreement with Stefan...
If the problem is intermittent then the system is overloaded at certain times. You would probably need to do some JVM analysis to see the resource usage & look at increasing the memory.
Regards, Trevor

SOAP Call Failure

Hi All,
We are facing the below error in receiver SOAP channel.. We are on PI7.1 ..Are there any installation checks that needs to be looked at as we are facing lot of inconsistencies with SOAP...
What may be the cause of the below error...Also please let me know what all checks are needed as there are inconsistencies with SOAP adapter...
SOAP: call failed: java.net.SocketException: Connection reset
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: java.net.SocketException: Connection reset.

Hi Amit,
Having the same issue :
SOAP: call failed: java.net.SocketException: Connection reset
has your issue been solved and how ?
Regards,

SOAP: call failed: java.io.IOException

Similar Messages

Maybe you are looking for