[jboss-jira] [JBoss JIRA] Updated: (JBAS-3880) java.rmi.ConnectException: Failed to communicate (java.net.SocketTimeoutException: Read timed out)
Nishant Saini (JIRA)
jira-events at jboss.com
Tue Nov 28 04:34:56 EST 2006
[ http://jira.jboss.com/jira/browse/JBAS-3880?page=all ]
Nishant Saini updated JBAS-3880:
--------------------------------
Priority: Blocker (was: Major)
> java.rmi.ConnectException: Failed to communicate (java.net.SocketTimeoutException: Read timed out)
> --------------------------------------------------------------------------------------------------
>
> Key: JBAS-3880
> URL: http://jira.jboss.com/jira/browse/JBAS-3880
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB2
> Affects Versions: JBossAS-4.0.4RC1, JBossAS-4.0.3 SP1
> Environment: Windows 2003 Server, Windows XP, J2SDK 1.4.2, JDK 1.5.0_09
> Reporter: Nishant Saini
> Assigned To: Scott M Stark
> Priority: Blocker
>
> Hi
> I have a client application which is accessing a Remote EJB deployed over JBoss AS 4.0.4 RC1 and JBoss AS 4.0.3 SP1. The client sends and recieves some large chunks of data to and from the server. But the following exception has started to come on client very frequently. Can we increase The Time out? Is the time out occurring during the reciept or sending of data or during the ping pong between server and client?
> How can we solve this problem? What is the cause of this problem?
> java.rmi.ConnectException: Failed to communicate; nested exception is:
> java.net.SocketTimeoutException: Read timed out
> at org.jboss.invocation.pooled.interfaces.PooledInvokerProxy.invoke(PooledInvokerProxy.java:382)
> at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
> at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
> at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
> at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
> at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
> at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
> ... 8 more
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> at java.io.BufferedInputStream.fill(Unknown Source)
> at java.io.BufferedInputStream.read(Unknown Source)
> at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source)
> at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source)
> at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source)
> at java.io.ObjectInputStream.readObject0(Unknown Source)
> at java.io.ObjectInputStream.readObject(Unknown Source)
> at org.jboss.invocation.pooled.interfaces.PooledInvokerProxy.invoke(PooledInvokerProxy.java:366)
> ... 14 more
> If any body finds the solution of this problem, please tell us.
> Thanks
> Nishant Saini
> http://www.simplyjava.com
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list