2

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)
8
  • Please check the below link it may be useful... stackoverflow.com/questions/1307154/… Commented Jan 7, 2014 at 10:26
  • @TataraoVana I changed jta but timeout error still continues. I can control 10.0.0.192 server without error I mean I can start-restart-stop that server from 10.0.0.32 adminconsole but I couldn't deploy any application to 10.0.0.192 from 10.0.0.32 adminconsole. Commented Jan 8, 2014 at 8:27
  • While deploying what kind of error you are getting? Commented Jan 8, 2014 at 9:21
  • @TataraoVana Same error in the question. When I open server monitoring tab it says "This server is not currently reachable. No additional monitoring information is available." but I can control this server(start-restart-stop). Commented Jan 8, 2014 at 9:49
  • Try restarting the server which controls other server....Tail the logs for any other warnings or errors... Commented Jan 8, 2014 at 10:20

1 Answer 1

2

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=

Sign up to request clarification or add additional context in comments.

12 Comments

Still got same error. There must be something wrong with my managed servers I think.
Try this.... you can set the client version on the command line of the client: -Dweblogic.CompleteMessageTimeout=480
I set complete message timeout on both servers. Same error "......in the configured timeout period of '480' secs......"
Seems to be a socket bug... check the below link it may be useful... 3y.uu456.com/bp-09bcsc0e6c8sec3a87c2cs94-1.html
"telnet 10.0.0.32 7002" seems ok but "telnet 10.0.0.32 55179" says "couldn't open connection to host". What is port 55179 and how can I edit this port number?
|

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.