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.

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

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

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é

Java.io.InterruptedIOException: Read timed out

Hi,
I have this error message in my web services-application.
I use Weblogic 7.0 and Java j2re1.4.2_03
Can you help me???
Best regards
Luig

Hello,
Please try posting this question along with additional details to:
weblogic.developer.interest.webservices.general
http://forums.bea.com/forum.jspa?forumID=2055
Regards,
/Raj

Java.io.IOException: Connection timed out while using non-blocking NIO

Hi,
I am using non-blocking NIO on jdk 1.6 to transfer files between two processes. The problem is that the sender thread times out on the write call even though it's in non-blocking mode. It doesn't make sense. The receiver on the other end is running fine, and even tries to read from the socket after the sender drops the connection, and throws a Connection reset by peer exception. I should mention that the receiver is sometimes busy doing other stuff, and may be a second or two late in issuing the read call. But if I understand correctly, default TCP timeout is about 2 minutes, so there's no reason why it should timeout in a second or two. I'd appreciate it if anyone has any insight.
Thanks!

No I have definitely completed the connection since I it happens a while after the transfer has actually started and part of the file has already been transferred. Oh btw, I should mention that it doesn't always happen. It's intermittent. And it's not a network issue since iperf tests between the two nodes show nothing unusual.

BIP fails to render a pdf report with Read timed out

Hi,
If a run a report with large query/data, BIP after 2 minutes fails with this error: java.sql.SQLException: java.net.SocketTimeoutException: Read timed out.
The BIP report run a OBIEE Query, and BI Server log return this:
[2012-07-03T14:47:39.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 00i8cAKOjzl7Y7k5wzCCyW0002gS0001OO] [tid: 28f0] [nQSError: 43119] Query Failed:
[2012-07-03T14:55:23.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 7a1d39a9491c6b05:-116dac4a:137a8e42d31:-8000-00000000000d1d0a] [tid: 2d7c] [nQSError: 46066] Operation cancelled. [[
ExecutePhysical Exchange
[2012-07-03T14:47:39.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 00i8cAKOjzl7Y7k5wzCCyW0002gS0001OO] [tid: 28f0] [nQSError: 17012] Bulk fetch failed. [[
[nQSError: 17001] Oracle Error code: 1013, message: ORA-01013: user requested cancel of current operation
at OCI call OCIStmtFetch.
How can I run the report? ...If I try the Phisical Query that OBIEE wrote on log, its work fine.
Thank you, R.

up!

RMI: Read timed out

I have a rmi call.
Client: JDK1.5.0_06 Windows 2003
Server: JDK1.5.0_06 Windows XP
I got following exceptions in client side sometimes, but not always:
java.rmi.MarshalException: error marshalling arguments; nested exception is:
java.net.SocketException: Connection reset by peer: socket write error
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
So I set -Dsun.rmi.server.exceptionTrace=true property to server side and got following exceptions:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.net.SocketTimeoutException: Read timed out
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:282)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
60)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:701)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java
:2217)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream
.java:2616)
at java.io.ObjectInputStream$BlockDataInputStream.readFully(ObjectInputS
tream.java:2646)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1609)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1293)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1628)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1293)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:19
12)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
713)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream
Is this problem caused by network or do you have any work around for it?

try to increase the socket read duration by adding -Dcom.sun.CORBA.transport.ORBTCPReadTimeouts= to the variable list of your JVM.
If it does not work, you can take a look at the sun bug 6553303 or search for the related bugs from the bug database. I saw a similar bug before.

Org.apache.axis2.AxisFault: Read timed out

We have web service client generated from wsdl2jave of axis2-1.4.1, we are getting an error on calling webservice operation, i have manually set timeout at one of the operation invocation, that looks fine now, but we have call so many places, do i need to set time all place same, I am not sure code i have used to set time is correct.
please advice how to over come the issue, web service has been deployed on WAS, client application started giving this error, after we have installed a patch to address security issue, can we address the issue from code level.
here is the code added to set timeout
int timeOutInMilliSeconds = 3 * 60 * 1000; // Two minutes
stub._getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT, new Integer(timeOutInMilliSeconds));
stub._getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT, new Integer(timeOutInMilliSeconds));
//end here
GetPermittedTypesResponse response = stub.getPermittedTypes(get);
permittedTypes = response.getReturn();
Here is error stack trace
org.apache.axis2.AxisFault: Read timed out
at org.apache.axis2.AxisFault.makeFault(Unknown Source)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(Unknown Source)
at org.apache.axis2.transport.http.HTTPSender.send(Unknown Source)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(Unknown Source)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Unknown Source)
at org.apache.axis2.engine.AxisEngine.send(Unknown Source)
at org.apache.axis2.description.OutInAxisOperationClient.send(Unknown Source)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(Unknown Source)
at org.apache.axis2.client.OperationClient.execute(Unknown Source)
at com.ecs.services.EcsObjectServiceStub.instantiateDocument(Unknown Source)
at com.ey.edocs.ecs.client.EcsObjectClient.instantiateDocument(Unknown Source)
at com.ey.edocs.ldi.helpers.ObjectHelper.createEcsObject(Unknown Source)
at com.ey.edocs.ldi.helpers.ObjectHelper.createEcsEmail(Unknown Source)
at com.ey.edocs.ldi.views.Import$16.run(Unknown Source)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(Unknown Source)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at org.apache.commons.httpclient.HttpParser.readRawLine(Unknown Source)
at org.apache.commons.httpclient.HttpParser.readLine(Unknown Source)
at org.apache.commons.httpclient.HttpConnection.readLine(Unknown Source)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(Unknown Source)
at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(Unknown Source)
at org.apache.commons.httpclient.HttpMethodBase.readResponse(Unknown Source)
at org.apache.commons.httpclient.HttpMethodBase.execute(Unknown Source)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Unknown Source)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(Unknown Source)
at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source)
at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Unknown Source)
... 14 more

Baseline.grf is not able to connect to Endeca Server. Make sure Endeca Server has started correctly and then run baseline.grf graph.
Regards,
Srikanth

SocketTimeoutException: Read timed out

First of all, I am sorry to bug you with a newbie question.
I am using Axis1.4. I write a build script and created the client stubs from WSDL, which generated the following files for me:
customer.CustomerServiceInterface.java
customer.CustomerWS.java
customer.CustomerWSBindingImpl.java
customer.CustomerWSBindingSkeleton.java
customer.CustomerWSBindingStub.java
customer.CustomerWSLocator
customer.types.Customer.java
customer.types.CustomerAddress.java
customer.types.GetCustomerElement.java
customer.types.GetCustomerResponseElement.java
customer.types.GetTestFaultElement.java
customer.types.GetTestFaultResponseElement.java
customer.types.OraIntException.java
Then I wrote a client application with a main method like this:
CustomerWSBindingStub stub = new CustomerWSBindingStub();
stub.setUsername("test");
stub.setPassword("test");
stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, "http://test.test.com:8878/CustomerWS/CustomerWS");
stub.setTimeout(60000);
GetCustomerElement element = new GetCustomerElement("1");
GetCustomerResponseElement response = stub.getCustomer(element);
This gives me the following error:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketTimeoutException: Read timed out
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.SocketTimeoutException: Read timed out
I tried changing the TimeOut, but with no luck. Is there any basic thing that I am missing? I got no clues.
Any help will be highly appreciated.

Hi,
The sender is able to send Object successfully and part of the applet code is
                               URLConnection con = getServletConnection("connection");
                    OutputStream outstream = con.getOutputStream();
                    ObjectOutputStream oos = new ObjectOutputStream(outstream);
                               Object[] sendObj = new Object[3];
                    sendObj[0] = (Object) someObject;
                    oos.writeObject(sendObj);
                    oos.flush();
                    oos.close();
     this applet part doesnt throw any exception.But when the Servlet is about to read the object the servlet part
                       InputStream in = request.getInputStream();
               ObjectInputStream inputFromApplet = new ObjectInputStream(in);
               Object[] appletInput = (Object[]) inputFromApplet.readObject();
   this part throws the above exception.
please help me out.
Thanks
John

SocketTimeoutException: Read timed out - Context Is Too Large

I've successfully generated ADS Forms through WebDynpro for a while, but have now run into an issue when the complex node used to fill the report is around 1,000 rows. The process to retrieve the data via the EJBs, along with the process to fill the context, takes around 10 seconds, but the actual generation of the PDF fails due to the following exception:
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:280)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:222)
     at com.sap.tc.webdynpro.clientserver.adobe.AdobeFormHelper.createPDFDocumentForUIElement(AdobeFormHelper.java:457)
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:158)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterHandleActionEvent(ClientApplication.java:1147)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:402)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:252)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     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:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
I'm not finding anything related to report size for this issue, only versioning of ADS and read credentials.
Are there limitations to the amount of information that can be generated with the SAP provided credentials?
Do I need to break up the amount of information displayed at one time?
Thanks,
Lane

Hi Lane,
first of all, the time out is definitely not related to the credential, it is simply a technical prerequisite for being able to create PDF forms using Interactive Forms at all.
If you are on NW '04 SP11 or lower, try upgrading to a later version. SP 12 (and higher) contains a newer version of Adobe document services that renders much faster.
Also, by default the Web service client socket timeout is set to 60. Try changing this parameter in the Visual Administrator: Server -> Services -> Web Services Container on the Settings tab.
We have seen online scenarios with performance issues when the context was rather large. It may make more sense to create smaller PDFs with a stricter data selection.
Hope this helps!
Kind regards,
Markus Meisl
SAP NetWeaver Product Management

Adobe Doc. Service problem: Read Timed Out

Hi,
I'm using Sneak Preview SP15. I've followed the guide
and still have the problem. Based on the flow chart in
the guide, I just need to do 3 steps. two of them are
already done by the installation process. The steps are:
1. Create User ID and group
2. Set up basic authentication
3. Install credential file
When I performed the test from
localhost:50000/AdobeDocumentServices/Config it return
the version info, which indicates that the config is
correct. Then I execute one of the demo web dynpro
application using adobe form, and it produced Read timed
out error.
Does anyone know what did I do wrong?
The error stack is:
[code]
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:268)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:209)
     at com.sap.tc.webdynpro.clientserver.adobe.AdobeFormHelper.createPDFDocumentForUIElement(AdobeFormHelper.java:417)
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:161)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterHandleActionEvent(ClientApplication.java:1088)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:393)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:640)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     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:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
[/code]
Message was edited by: Iwan Santoso

Markus,
Thanks. You are the man! I think that's it. I don't have access to the system right now, but I will check that setting this weekend. I know I haven't changed it during installation. In the mean time, I will check those OSS Notes for my bed time reading
I did not realized the interactive form has its own forum Next time I will post in the correct forum.
Umadevi,
Thanks for the feed back. I don't think that is the problem since the same project when i deploy and run in the office server it runs just fine. The problem only when I Deploy and Run on my sneak preview server. If changing the setting as Markus mentioned above doesn;t work, then I will try to change the cardinality of the node.
Reagards,
Iwan

Data Federator - Read timed out

Hi,
I'm using Data Federator XI 3.0 SP2. I have a datasource connecting to a web service. The web service may return take a long time to do heavy processing, etc., before returning any data. If I call the web service via Data Federator, I will get the following error
Exception was thrown while executing a query on Data Federator Query Server.
An exception occurred when querying Data Federator Query Server.
    [Data Federator Driver][Server]
[Wrapper /TEST/sysadmin/sources/draft/ReturnInputAsOutput]HTTP input/output exception: Read timed out
      [Wrapper /TEST/sysadmin/sources/draft/ReturnInputAsOutput]HTTP input/output exception: Read timed out
        [Wrapper /TEST/sysadmin/sources/draft/ReturnInputAsOutput]HTTP input/output exception: Read timed out
          HTTP input/output exception: Read timed out
I'm guessing that the Data Federator query timed out because the web service takes a long time to response, is it not? If this is the case, how do I increase timeout value? If this is not the case, then what does the error mean and how do I resolve it?
Thanks.
Edited by: Chih Hui Wan on Nov 19, 2009 9:15 AM

Hi Dayanand,
For testing purpose, I created a small simple web service with only one operation that sleep for more than two minutes before returning a string. I called this web service operation from Data Federator. After waiting for a while, I got the "Read timed out" error
Regards,
Chih Hui

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

Similar Messages

Maybe you are looking for