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
Similar Messages
-
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,
LaneHi 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 -
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!
-
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 moreBaseline.grf is not able to connect to Endeca Server. Make sure Endeca Server has started correctly and then run baseline.grf graph.
Regards,
Srikanth -
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 SantosoMarkus,
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 -
Read timed out, for file checkin using SCS API
Hi,
I have installed content server and deployed CIS in standalone oc4j.
I want to checkin files using the SCS API. Initially I was to able checkin a file of size 120MB successfully. When I tried to checkin a file of size 300MB , file is checked in but an Exception with the msg "Read timeout out" is thrown.
I am able to checkin the same file(300MB) through content server front end without any error.Why do I get exception when using the API?
[2008-01-11 09:56:07,343] [main] WARN (com.stellent.cis.server.api.scs.protocol.impl.HDAProtocol) - Unable to find end header mark! ()
[2008-01-11 09:56:07,343] [main] WARN (com.stellent.cis.server.api.scs.protocol.impl.HDAProtocol) - Did not read any headers from input, setting type to UNKNOWN_TYPE
com.stellent.cis.client.command.CommandException: com.stellent.cis.server.api.scs.request.SCSRequestException: Error reading the response from the Content Server: Read timed out
at com.stellent.cis.server.api.scs.impl.SCSCommand.executeRequest(SCSCommand.java:338)
at com.stellent.cis.server.api.scs.impl.SCSCommand.execute(SCSCommand.java:222)
at com.stellent.cis.client.command.impl.services.CommandExecutorService.executeCommand(CommandExecutorService.java:57)
at com.stellent.cis.client.command.impl.CommandFacade.executeCommand(CommandFacade.java:158)
at com.stellent.cis.client.command.impl.BaseCommandAPI.invokeCommand(BaseCommandAPI.java:84)
at com.stellent.cis.client.api.scs.document.checkin.impl.SCSDocumentCheckinAPI.checkinFileStream(SCSDocumentCheckinAPI.java:707)
at test.CheckinFile.execute(CheckinFile.java:85)
at test.CheckinFile.main(CheckinFile.java:60)
Caused by: com.stellent.cis.server.api.scs.request.SCSRequestException: Error reading the response from the Content Server: Read timed out
at com.stellent.cis.server.api.scs.request.impl.SCSRequestProcessor.parseResponse(SCSRequestProcessor.java:223)
at com.stellent.cis.server.api.scs.request.impl.SCSRequestProcessor.processRequest(SCSRequestProcessor.java:114)
at com.stellent.cis.server.api.scs.request.impl.SCSRequestFilterChain.doRequestFilter(SCSRequestFilterChain.java:61)
at com.stellent.cis.server.api.scs.request.stream.SCSOptimizedPublishFilter.handleRequest(SCSOptimizedPublishFilter.java:128)
at com.stellent.cis.server.api.scs.request.impl.SCSRequestFilterChain.doRequestFilter(SCSRequestFilterChain.java:58)
at com.stellent.cis.server.api.scs.request.stream.SCSOptimizedRetrieveFilter.handleRequest(SCSOptimizedRetrieveFilter.java:250)
at com.stellent.cis.server.api.scs.request.impl.SCSRequestFilterChain.doRequestFilter(SCSRequestFilterChain.java:58)
at com.stellent.cis.server.api.scs.request.rewrite.SCSRewriteURLFilter.handleRequest(SCSRewriteURLFilter.java:140)
at com.stellent.cis.server.api.scs.request.impl.SCSRequestFilterChain.doRequestFilter(SCSRequestFilterChain.java:58)
at com.stellent.cis.server.api.scs.request.cache.impl.SCSServiceCacheFilter.handleRequest(SCSServiceCacheFilter.java:104)
at com.stellent.cis.server.api.scs.request.impl.SCSRequestFilterChain.doRequestFilter(SCSRequestFilterChain.java:58)
at com.stellent.cis.server.api.scs.request.impl.SCSRequestExecutorProxy.execute(SCSRequestExecutorProxy.java:105)
at com.stellent.cis.server.api.scs.impl.SCSCommand.executeViaProxy(SCSCommand.java:353)
at com.stellent.cis.server.api.scs.impl.SCSCommand.executeRequest(SCSCommand.java:335)
... 7 more
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.read1(BufferedInputStream.java:254)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
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 com.stellent.cis.server.api.scs.protocol.impl.HDAProtocol$1.read(HDAProtocol.java:379)
at java.io.FilterInputStream.read(FilterInputStream.java:90)
at com.stellent.cis.server.api.scs.protocol.impl.BaseHDAProtocol.determineFormat(BaseHDAProtocol.java:150)
at com.stellent.cis.server.api.scs.protocol.impl.HDAProtocol.readMessage(HDAProtocol.java:308)
at com.stellent.cis.server.api.scs.request.impl.SCSRequestProcessor.parseResponse(SCSRequestProcessor.java:206)
... 20 more
Regards
RajiI would probably guess that CIS is configuring its socket threads to have particular timeouts (to limit the time you would wait if something seriously went wrong with the request). Typically CIS is focused on page generation in APP servers or portals and these app servers (or portals) tend to like timeouts on their requests. This of course is unsuitable for the scenario of uploading the file. I would consult the CIS documentation to see if there are any mechanisms for tuning this behavior. If not, try contacting support.
-
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 AMHi 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 -
Read timed out error while opening monitor tab in DataServices
Hello all,
Am getting a "Read timed out" error when I try to open the monitor tab in DataServices admin console for a few jobs only. For several jobs, monitor tab opens just fine. But for a few it doesnt and throws the error mentioned above. Mostly this behaviour is noticed with a job having several workflows and dataflows.
The version of DS used is 12.1.0.0. Tried to gather some info on this issue, but couldnt find any relevant thread. Would really appreciate if anyone could help me with it.
Regards,
Premcheck the following post
http://www.forumtopics.com/busobj/viewtopic.php?t=148213 -
Error: Read timed out&MESSAGE_NOT_FOUND.
Hi,
There's a synchronous scenario (File-File). A connection failure occured during a query from buisness-process (BPM). Since then an error (error message) appears constantly in Runtime Workbench-Component Monitoring-Communication Channels.
Success
RRB: entering RequestResponseBean
Success
RRB: passing through ...
Success
RRB: suspending the transaction
Success
RRB: leaving RequestResponseBean
Success
Application attempting to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.
Success
Trying to put the message into the call queue.
Success
Message successfully put into the queue.
Success
The message was successfully retrieved from the call queue.
Success
The message status set to DLNG.
Error
Received XI System Error. ErrorCode: GENERAL ErrorText: com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out ErrorStack:
Error
Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out.
Error
Transmitting the message using connection http://*****:8010/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out.
Error
The message status set to FAIL.
Error
Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out
Error
Attempt to process file failed with com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Read timed out
Error
Attempt to process file failed with com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException
File removing and the channel rebooting the channel donu2019t help.
After rebooting the channel:
Error
Received XI System Error. ErrorCode: MESSAGE_NOT_FOUND ErrorText: ErrorStack: XML message not found
Error
Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MESSAGE_NOT_FOUND:.
Error
Transmitting the message using connection http://*****:8010/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MESSAGE_NOT_FOUND:.
Error
The message status set to FAIL.
Error
Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MESSAGE_NOT_FOUND:
Error
Attempt to process file failed with com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MESSAGE_NOT_FOUND:
Error
Attempt to process file failed with com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException
Any ideas?hi,
try this,
go to Message Monitoring in RWB, delete all the messages with status system error and onhold.
it shd solve your problem
Regards,
Sukarna.chirumamilla. -
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,
JitenderHI 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. -
IO Error: Socket read timed out / IOP_iopinstance1_datasource" closed
Hi ,
Can somebody suggest what could be the probable cause of following errors showing up in IOP log file?
####<Aug 16, 2011 10:49:11 PM PDT> <Info> <Common> <sc-csttest> <IOPServer_iopinstance1> <weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@357ac2f7> <<anonymous>> <> <0000J7MI9kZFk3vLsYw0yX1EIpFA00002K> <1313560151943> <BEA-000628> <Created "1" resources for pool "IOP_iopinstance1_datasource", out of which "1" are available and "0" are unavailable.>
####<Aug 16, 2011 10:49:12 PM PDT> <Info> <JDBC> <sc-csttest> <IOPServer_iopinstance1> <weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@357ac2f7> <<anonymous>> <> <0000J7MI9kZFk3vLsYw0yX1EIpFA00002K> <1313560152146> <BEA-001128> <Connection for pool "IOP_iopinstance1_datasource" closed.>
java.sql.SQLRecoverableException: IO Error: Socket read timed out
Thanks
LokeshThis particular error means your database is down and socket is timedout. Or the query takes so long that the reader timedout -- unlikely.
Also, the general weblogic socket write errors, which you might see sometimes means that the client got disconnected before the server wrote results back. This is harmless -
when i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"
Hi, Michal
I have read your Weblog. It makes sense to me. Thanks a lot for your help! However, I still have some questions and listed them as following. Could you please help to answer them?
<b>Q1:</b> I am new to SAP-XI. So I have no idea about TCODE-SXMB_ADM. Could you introduce more details about it?
<b>Q2:</b> The XI system I am using is running on SAP-ICC's machine. The tools I can use are:
<b>1.</b>Builder for Integration Repository
<b>2.</b>Builder for Integration Configuration
<b>3.</b>System Landscape Directory
<b>4.</b>Runtime Workbench
<b>5.</b>Administration System (for Repository, Directory, Runtime)
Please note that I do not have a complete control on this SAP-XI. Do you think whether or not I can set the timeout parameter by following the instructions provided in your Weblog?
For more details about my SAP-XI, please access the following Web page:
http://iccxi.sap.com:58000/rep/support/admin/index.html
<b>Q3:</b> The following messages are extracted from the SAP-XI. Wish they are hepful to solving my problem.
2006-06-19 05:12:16 Success The message was successfully received by the messaging system. Profile: XI URL: http://iccxi.sap.com:58000/MessagingSystem/receive/AFW/XI
2006-06-19 05:12:16 Success Using connection AFW. Trying to put the message into the request queue.
2006-06-19 05:12:16 Success Message successfully put into the queue.
2006-06-19 05:12:16 Success The message was successfully retrieved from the request queue.
2006-06-19 05:12:16 Success The message status set to DLNG.
2006-06-19 05:12:16 Success Delivering to channel: ValidationRequestHandlerServiceChannel
2006-06-19 05:12:16 Success SOAP: request message entering the adapter
2006-06-19 05:12:37 Success SOAP: call failed
2006-06-19 05:12:37 Error SOAP: error occured: java.net.ConnectException: Connection timed out: connect
2006-06-19 05:12:37 Error Exception caught by adapter framework: Connection timed out: connect
Thanks
Menghua Li -
SLD server exception: IO error: Read timed out
Hi,
I have deployed the components for NWDI and after that when i am creating the Domain,I am doing update CMS data for creating a Track. I am getting the following error:
SLD server exception: IO error: Read timed out
Can any one help on this.
Thanks
Ravi.SHi,
My SLD is a PI 7.0 system and my NWDI is configured on a standalone Java system.
I have done the SLDDataSupplier check, and it connects fine to the SLD.
Also on my http://<hostname>:<port>/devinf/main in the NWDI system, the SLD link points to the right SLD and im able to connect.
Still at the CMS update stage it gives the error -
SLD (URL http://<hostname>:<port>/) server exception: IO error: Read timed out -
JDBC pooling Oracle driver Socket read timed out
I run Java EE application on Glassfish server v3 together with Oracle 12 DB on the same machine under Windows Server 2012 64bit. I use latest ojdbc7 driver.
Connection pool config:
<jdbc-connection-pool validation-table-name="DUAL" steady-pool-size="20" statement-cache-size="100" associate-with-thread="true" statement-timeout-in-seconds="30" idle-timeout-in-seconds="60" max-wait-time-in-millis="2000" validate-atmost-once-period-in-seconds="20" datasource-classname="oracle.jdbc.pool.OracleDataSource" pool-resize-quantity="5" max-pool-size="60" res-type="javax.sql.DataSource" name="dbPool" is-connection-validation-required="true">
<property name="driverClass" value="oracle.jdbc.OracleDriver"></property>
<property name="user" value="xxx"></property>
<property name="url" value="jdbc:oracle:thin:@(DESCRIPTION=(ENABLE=BROKEN)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))"></property>
<property name="password" value="xxx"></property>
<property name="portNumber" value="1521"></property>
<property name="databaseName" value="orcl"></property>
<property name="serverName" value="127.0.0.1"></property>
<property name="oracle.jdbc.ReadTimeout" value="300000"></property>
<property name="oracle.net.CONNECT_TIMEOUT" value="10000"></property>
</jdbc-connection-pool>
After 2 or 3 hours, when there is more than 1 user (3-5) using my application, it stops responding and I get this in glassfish logs
javax.enterprise.resource.resourceadapter.com.sun.enterprise.resource.allocator|_ThreadID=152;_ThreadName=Thread-2;|RAR5038:Unexpected exception while creating resource for pool dbPool. Exception : javax.resource.spi.ResourceAllocationException: Connection could not be allocated because: IO Error: Socket read timed out
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: IO Error: Socket read timed out
From the database side it looks like this
Fatal NI connect error 12560, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for 64-bit Windows: Version 12.1.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 12.1.0.1.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 12.1.0.1.0 - Production
Time: 13-JUN-2014 03:14:49
Tracing not turned on.
Tns error struct:
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (3404) as a result of ORA-609
When I just reset db listener everything works ok for next 1-2 hours (depends on application load). So temporary solution is to run bat script from windows scheduler to reset the listener every 1h.
I tried everything I could find - applied these parameters:
- Sqlnet.ora:
SQLNET.INBOUND_CONNECT_TIMEOUT=180
SQLNET.EXPIRE_TIME=5
- Listener.ora:
INBOUND_CONNECT_TIMEOUT_LISTENER_IPC=120
But still without successIs the problem here just that you need a connection pool that closes idle connections? Some pools will close idle connections after a time out period. And the pool lets you set that time out period. If the pool you are using doesn't provide that then use a different pool.
Maybe you are looking for
-
Oracle DBA related issues ?????
where can i discuss DBA related issues? thanks
-
Hi I was getting the jms test error under the BIP Scheduler configuration so in order to rectify it i followed the steps in https://cn.forums.oracle.com/forums/thread.jspa?messageID=10678840 but it has effected and the server went down...then i follo
-
Is there really no way to download songs from itunes in mp3 format? Seriously?
-
IPod won't sync - or do anything else
I bought a new iPod touch today, and I just plugged it in with the USB to my computer. It started off fine, and I registered it etc. It is now taking an enternity to sync each application. My friends that own iPod touchs say that is usually takes abo
-
EBS 12.1.1 multinode configuration
Hello: I have installed EBS 12.1.1. on multi node condiguration: 1 db sever 3 app servers. Everything works OK, but when I try to log in to the server1 (http://server1.mydomain.com:8000) it redirects me to the server3 (http://server3.mydomain.com:800