timeout error on weblogic cluster - weblogic

Question

I want to run a web application on a cluster.There are 2 servers(10.0.0.32 and 10.0.0.192). When I try to run this application on 10.0.0.192 I am getting below error.
By the way I am using adminserver on 10.0.0.32. I can control server 10.0.0.192 without any problem from 10.0.0.32 adminserver.
####<Dec 30, 2013 3:02:36 PM EET> <Error> <HTTP> <dell-PC> <10-0-0-192> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1388408556025> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP#4bd7f3dd:Socket[addr=/10.0.0.32,port=55179,localport=7002] - idle timeout: '30000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs
at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:1076)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:293)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Answer 1

Cause:
The above error indicates that the default configured timeout period of '60' secs is not sufficinet to transfer the complete message to the server.
Resolution:
Increase the Complete Message Time Out to 480 seconds in weblogic console:
Server --> Protocols --> General -> Advanced Attributes -> Complete Message Timeout
You must reboot the server.
A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection'" on WebLogic :
weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection#12c22dd4', in the configured timeout period of '60' secs
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
for this we can increase timeout period by setting the parameters
-Dweblogic.CompleteT3MessageTimeout=
-Dweblogic.CompleteMessageTimeout=