GetInputStream from request - read timed out

I'm using Weblogic server 5.1 and a third party product
(Blackboard), running on Win2k and IIS5.0.
I've created a servlet and configured weblogic to execute the servlet
for a given extension etc.. which works fine, but when trying to read from
the ServletInputStream I get an IOException, "Read timed out". This isn't a
problem in weblogic.servlet.internal.ServletInputStreamImpl, but something
further back that sets the input stream. I've tried reset, but it appears
that reset and marking is not supported. I know POSTs are working within the
third party application, but I'm using PROPFIND and trying to read XML (the
content-length is correct).
Any suggestions,
Matt Elton
Univeristy of Northumbria
Newcastle
UK

I 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.

Similar Messages

Read of HTTP Request POST parameters failed:Read timed out

Hi !
Any one seen this exception . any ideas of the cause?
java.lang.RuntimeException: Read of HTTP Request POST parameters failed: Read timed out
at org.apache.catalina.connector.HttpRequestBase.parseParameters(HttpRequestBase.j ava:665)
at org.apache.catalina.connector.HttpRequestBase.getParameterValues(HttpRequestBase.java :737)
at org.apache.catalina.connector.RequestFacade.getParameterValues(RequestFacade.java:170 )
Thanks,

Assuming there is nothing wrong with
org.apache.catalina.connector.HttpRequestBase.parseParameters
I can only think of 2 things:
1. The timeout is set for an extremely short time in the Apache settings (server.xml의)
2. The client application is sending the POST verry slow or incorrect. For example the
client says that the POST is 500 long than sends 200 and leaves the connection open.
You can try and post the following:
request.txt:
POST /somePath/somefile.js HTTP/1.1
Host: localhost:44
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Content-Length: 45
depreciatedButWontPostWithoutAName=some+valueThe client sending the request:
import java.io.*;
import java.net.*;
import java.io.DataOutputStream;
import java.applet.Applet;
public class appTest extends Applet implements Runnable {
     public static final int HTTP_PORT = 80;
     public static final String hostName = "localhost";
     public void run() {
          try{
               InetAddress addr = InetAddress.getByName(hostName);
               Socket s = new Socket(addr,HTTP_PORT);
               BufferedWriter wr = new BufferedWriter(new OutputStreamWriter(s.getOutputStream(), "UTF8"));
               s.setSoTimeout(2000);
               File fileToSend = new File("request.txt");
               FileInputStream fleHTML = new FileInputStream(fileToSend);
               StringBuffer sbHTMFile = new StringBuffer();
               int b = fleHTML.read();
               while(b!=-1){
                    sbHTMFile.append((char) b);
                    b = fleHTML.read();
               wr.write(sbHTMFile.toString());
               wr.flush();
               BufferedReader rd = new BufferedReader(new InputStreamReader(s.getInputStream()));
               String line;
               while ((line = rd.readLine()) != null) {
                    System.out.println(line);
               wr.close();
               rd.close();
               } catch (Exception e) {
                    e.printStackTrace();
     public void init(){
          new Thread(this).start();
     public appTest(){
          new Thread(this).start();
     // main program
     public static void main(String argv[]) throws Exception {
          new appTest();
}In appTest.java change HTTP_PORT to the port you need and hostName to the
hostname you need.
In request.txt change the /somePath/somefile.js to the location you desire.
And change Host: localhost:44 to the hostname and post you desire.

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

The request has timed out after 00:00:00 milliseconds.

Hello,
I am having weird exception when I try to send a message to a topic and there's nothing on the internet I could "google with Bing" about it.
Here's the error message
The request has timed out after 00:00:00 milliseconds. The successful completion of the request cannot be determined. Additional queries should be made to determine whether or not the operation has succeeded.
There are two things weird about it:
The timeout period is 0 miliseconds
The number of miliseconds is given in format 00:00:00
Here's the whole stack
Timestamp: 5.5.2014. 11:15:58
Message: HandlingInstanceID: b9fcc3c8-c167-47ab-8473-ae45bfb62311
An exception of type 'System.TimeoutException' occurred and was caught.
05/05/2014 11:15:58
Type : System.TimeoutException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : The request has timed out after 00:00:00 milliseconds. The successful completion of the request cannot be determined. Additional queries should be made to determine whether or not the operation has succeeded.
Source : Microsoft.ServiceBus
Help link :
Data : System.Collections.ListDictionaryInternal
TargetSite : TAsyncResult End[TAsyncResult](System.IAsyncResult)
HResult : -2146233083
Stack Trace :
Server stack trace:
Exception rethrown at [0]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.TokenProviderHelper.EndGetAccessTokenCore(IAsyncResult result, String& expiresIn)
at Microsoft.ServiceBus.TokenProviderHelper.EndGetAccessTokenByAssertion(IAsyncResult result)
at Microsoft.ServiceBus.SharedSecretTokenProvider.OnEndGetToken(IAsyncResult result, DateTime& cacheUntil)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult.OnEndTokenProviderCallback(IAsyncResult result, DateTime& cacheUntil)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResultBase`1.OnCompletion(IAsyncResult result)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResultBase`1.<GetAsyncSteps>b__f(T thisPtr, IAsyncResult r)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [1]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(TokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationToken(String appliesTo, String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken, String parentLinkId, RetryPolicy policy, TrackingContext trackingContext, RequestInfo requestInfo)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessage(String action, Object body, String parentLinkId, RetryPolicy policy, TrackingContext trackingContext, RequestInfo requestInfo)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.SendCommandAsyncResult.CreateWcfMessage()
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpTransactionalAsyncResult`1.<GetAsyncSteps>d__40.MoveNext()
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.Start()
Exception rethrown at [2]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.EndSendCommand(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.<.ctor>b__1(IAsyncResult result, Boolean forceCleanUp)
at Microsoft.ServiceBus.Messaging.BatchManager`1.PerformFlushAsyncResult.OnSingleOperationCompleted(IAsyncResult result)
Exception rethrown at [3]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.BatchManager`1.BatchedObjectsAsyncResult.End(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.BatchManager`1.EndBatchedOperation(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.BatchManagerAsyncResult`1.OnBatchedCallback(IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult.AsyncCompletionWrapperCallback(IAsyncResult result)
Exception rethrown at [4]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.OnEndSend(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.MessageSender.RetrySenderAsyncResult.<GetAsyncSteps>b__f(RetrySenderAsyncResult thisPtr, IAsyncResult r)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
Exception rethrown at [5]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.TopicClient.EndSend(IAsyncResult result)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Niva.Framework.Azure.Bus.AzureServiceBus.<EnqueueAsync>d__0.MoveNext() in c:\nivatech\papiri\source\framework\Azure\Bus\AzureServiceBus.cs:line 98
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Niva.Framework.Analytics.BusinessActivityLogRepository.<EnqueueAddAsync>d__29.MoveNext() in c:\nivatech\papiri\source\framework\Core\Analytics\BusinessActivityLogRepository.cs:line 51
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Niva.Papiri.Web.Controllers.BaseController.<RegisterActivityAsync>d__4.MoveNext() in c:\nivatech\papiri\source\web\site\Controllers\BaseController.cs:line 102
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Niva.Papiri.Web.Controllers.HomeController.<Index>d__0.MoveNext() in c:\nivatech\papiri\source\web\site\Controllers\HomeController.cs:line 35
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Mvc.Async.TaskAsyncActionDescriptor.EndExecute(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<BeginInvokeAsynchronousActionMethod>b__36(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.CallEndDelegate(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResultBase`1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass48.<InvokeActionMethodFilterAsynchronouslyRecursive>b__41()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass33.<BeginInvokeActionMethodWithFilters>b__32(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.CallEndDelegate(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResultBase`1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<>c__DisplayClass2b.<BeginInvokeAction>b__1c()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<BeginInvokeAction>b__1e(IAsyncResult asyncResult)
Additional Info:
TimeStamp : 5.5.2014. 11:15:58
FullName : Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
AppDomainName : /LM/W3SVC/2/ROOT-1-130437489467023302

We had the same issue and solved it.
We changed the authorization of the servicebus to SAS and all is working fine now.
1. Check Azure Portal select your ServiceBus and go to register configuration
2. You need the Name and Key of existing Rule (here RootManageSharedAccessKey) or insert a new Rule. We created a new rule with no manage access.
3.1 In Code:
Replace the SharedSecretCredentials with SAS Tokenprovider and add it to the endpoint behaviors like before
TransportClientEndpointBehavior sas = new TransportClientEndpointBehavior();
sas.TokenProvider = TokenProvider.CreateSharedAccessSignatureTokenProvider("NAMEofRULE","KEYofRULE");
3.2 App.Config:
Simply change the tokenprovider line from
<behaviors>
 <endpointBehaviors>
 <behavior name="sharedSecretClientCredentials">
 <transportClientEndpointBehavior>
 <tokenProvider><sharedSecret issuerName="ACSNAME" issuerSecret="ACSKEY"/></tokenProvider>...
to
<sharedAccessSignature keyName="NAMEofRule" key="KEYofRULE"/>
Hope it helps!

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.

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"

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?
Q1: I am new to SAP-XI. So I have no idea about TCODE-SXMB_ADM. Could you introduce more details about it?
Q2: The XI system I am using is running on SAP-ICC's machine. The tools I can use are:
1.Builder for Integration Repository
2.Builder for Integration Configuration
3.System Landscape Directory
4.Runtime Workbench
5.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
Q3: 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

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

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
Raji

I 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.

Unhandled Exception: System.TimeoutException: The request channel timed out while waiting for a reply after 00:01:59.9139778.Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding.

Hi,
I created a simple plugin and since i wanted to use Early Binding i added Xrm.cs file to my solution.After i tried registering the plugin (using the Plugin Registration Tool) the plugin does not gets registered and i get the below mentioned Exception.
Unhandled Exception: System.TimeoutException: The request channel timed out while waiting for a reply after 00:01:59.9139778. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this
operation may have been a portion of a longer timeout.
Server stack trace:
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Xrm.Sdk.IOrganizationService.Update(Entity entity)
at Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy.UpdateCore(Entity entity)
at Microsoft.Crm.Tools.PluginRegistration.RegistrationHelper.UpdateAssembly(CrmOrganization org, String pathToAssembly, CrmPluginAssembly assembly, PluginType[] type)
at Microsoft.Crm.Tools.PluginRegistration.PluginRegistrationForm.btnRegister_Click(Object sender, EventArgs e)
Inner Exception: System.TimeoutException: The HTTP request to 'https://demoorg172.api.crm.dynamics.com/XRMServices/2011/Organization.svc' has exceeded the allotted timeout of 00:01:59.9430000. The time allotted to this operation may have been a portion of a
longer timeout.
at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
Inner Exception: System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
And to my Surprise after i remove the Xrm.cs file from my solution the Plugin got registered!
Not understanding what exactly is the issue.
Any Suggestions are highly appreciated.
Thanks,
Shradha


Hello Shardha,
I really appreciate that you have faced this issue.This is really very strange issue and basically it occurs because of big size of your early bound class and slow internet
connection.
I would strictly recommend you to reduce the file size of your early bound class and then register.By default early bound class is created for all the entities which are
present in CRM(System entities as well custom entities).Such kind of early bound classes takes lots of time to register on server and hence timeout exception comes.
There is some standard define to reduce the size of early bound class.Please follow the link to get rid from big size of early bound class.
Create a new C# class library project in Visual Studio called SvcUtilFilter.
In the project, add references to the following:
CrmSvcUtil.exe(from sdk) This exe has the interface we will implement.
Microsoft.Xrm.Sdk.dll (found in the CRM SDK).
System.Runtime.Serialization.
Add the following class to the project:
using System;
using System.Collections.Generic;
using System.Xml.Linq;
using Microsoft.Crm.Services.Utility;
using Microsoft.Xrm.Sdk.Metadata;
namespace SvcUtilFilter
 /// <summary>
 /// CodeWriterFilter for CrmSvcUtil that reads list of entities from an xml file to
 /// determine whether or not the entity class should be generated.
 /// </summary>
 public class CodeWriterFilter : ICodeWriterFilterService
 //list of entity names to generate classes for.
 private HashSet<string> _validEntities = new HashSet<string>();
 //reference to the default service.
 private ICodeWriterFilterService _defaultService = null;
 /// <summary>
 /// constructor
 /// </summary>
 /// <param name="defaultService">default
implementation</param>
 public CodeWriterFilter( ICodeWriterFilterService defaultService )
 this._defaultService = defaultService;
 LoadFilterData();
 /// <summary>
 /// loads the entity filter data from the filter.xml file
 /// </summary>
 private void LoadFilterData()
 XElement xml = XElement.Load("filter.xml");
 XElement entitiesElement = xml.Element("entities");
 foreach (XElement entityElement in entitiesElement.Elements("entity"))
 _validEntities.Add(entityElement.Value.ToLowerInvariant());
 /// <summary>
 /// /Use filter entity list to determine if the entity class should be generated.
 /// </summary>
 public bool GenerateEntity(EntityMetadata entityMetadata, IServiceProvider services)
 return (_validEntities.Contains(entityMetadata.LogicalName.ToLowerInvariant()));
 //All other methods just use default implementation:
 public bool GenerateAttribute(AttributeMetadata attributeMetadata, IServiceProvider services)
 return _defaultService.GenerateAttribute(attributeMetadata, services);
 public bool GenerateOption(OptionMetadata optionMetadata, IServiceProvider services)
 return _defaultService.GenerateOption(optionMetadata, services);
 public bool GenerateOptionSet(OptionSetMetadataBase optionSetMetadata, IServiceProvider services)
 return _defaultService.GenerateOptionSet(optionSetMetadata, services);
 public bool GenerateRelationship(RelationshipMetadataBase relationshipMetadata, EntityMetadata otherEntityMetadata, IServiceProviderservices)
 return _defaultService.GenerateRelationship(relationshipMetadata, otherEntityMetadata, services);
 public bool GenerateServiceContext(IServiceProvider services)
 return _defaultService.GenerateServiceContext(services);
This class implements the ICodeWriterFilterService interface. This interface is used by the class generation
utility to determine which entities, attrributes, etc. should actually be generated. The interface is very simple and just has seven methods that are passed metadata info and return a boolean indicating whether or not the metadata should be included
in the generated code file.
For now I just want to be able to determine which entities are generated, so in the constructor I read from an XML
file (filter.xml) that holds the list of entities to generate and put the list in a Hashset. The format of the xml is this:
<filter>
<entities>
 <entity>systemuser</entity>
 <entity>team</entity>
 <entity>role</entity>
 <entity>businessunit</entity>
</entities>
</filter>
Take a look at the methods in the class. In the GenerateEntity method, we can simply check the EntityMetadata parameter
against our list of valid entities and return true if it's an entity that we want to generate.
For all of the other methods we want to just do whatever the default implementation of the utility is. Notice
how the constructor of the class accepts a defaultService parameter. We can just save a reference to this default service and use it whenever we want to stick with the default behavior. All of the other methods in the class just call the default
service.
To use our extension when running the utility, we just have to make sure the compiled DLL and the filter.xml file
are in the same folder as CrmSvcUtil.exe, and set the /codewriterfilter command-line argument when running the utility (as described in the SDK):
crmsvcutil.exe /url:http://<server>/<org>/XrmServices/2011/Organization.svc /out:sdk.cs /namespace:<namespace> /codewriterfilter:SvcUtilFilter.CodeWriterFilter,SvcUtilFilter
/username:[email protected] /password:xxxx
That's it! You now have a generated sdk.cs file that is only a few hundred kilobytes instead of 5MB.
One final note: There is actually a lot more you can do with extensions to the code generation utility.
For example: if you return true in the GenerateOptionSet method, it will actually generated Enums for each CRM picklist (which it doesn't normally do by default).
Also, the source code for this SvcUtilFilter example can be found here.
Use at your own risk, no warranties, etc. etc.
Please mark as a answer if this post is useful to you.

HttpIOException: read timed out

Hi,
I have a Servlet that receives large XML structures in a soap attachment. The client calls my
doPost(HttpServletRequest request, HttpServletResponse response) method
and I try to read the request ServeltInputStream by
BufferedInputStream inbuf = new BufferedInputStream(request.getInputStream());
When I try to read out the inbuf stream I got sometimes the following exception: "HttpIOException: read timed out"
I have no idea why. Can anyone help? Thanks in advance.

Are you using the Orion server ?
(the HttpIOException class is not 'standard' - are you using com.evermind.server.http.HttpIOException?).
In that case, looks like a bug with the Orion server itself :
http://www.mail-archive.com/[email protected]/msg01436.html

When I try to download iOS 6 to my iPhone 4 it says " Verification Failed. Request has timed out". What do I do?

How to download iOS 6 on iPhone 4??. Keeps saying "verification fAiled. Request has timed out"

Try try again. Thre server are heavily loaded. The connection dropped becasue the computer thinks it waited to long. Disabling your security software on the computer can help resolve this too.

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: 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.

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.

GetInputStream from request - read timed out

Similar Messages

Maybe you are looking for