AnsweredAssumed Answered

A complete message could not be read on socket

Question asked by Loktyukhov Vladimir on Dec 20, 2017

Hello!

 

We have problem with authectation agent. We install it to PC and it cant connect to RSA. In log BiztierServerWrapper I found java error:

 

INFO   | jvm 1    | main    | 2017/12/19 14:15:06 | <Dec 19, 2017 2:15:06 PM FET> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read from it on X.X.X.X:60,479 during the configured idle timeout of 5 seconds.>
INFO   | jvm 1    | main    | 2017/12/19 14:16:01 | <Dec 19, 2017 2:16:01 PM FET> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read from it on X.X.X.X:60,486 during the configured idle timeout of 5 seconds.>
INFO   | jvm 1    | main    | 2017/12/19 14:17:12 | <Dec 19, 2017 2:17:11 PM FET> <Error> <HTTP> <BEA-101083> <Connection failure.
INFO   | jvm 1    | main    | 2017/12/19 14:17:12 | java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1968e18c:Socket[addr=/X.X.X.X,port=60489,localport=5500] - idle timeout: '30000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs
INFO   | jvm 1    | main    | 2017/12/19 14:17:12 |  at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:1076)
INFO   | jvm 1    | main    | 2017/12/19 14:17:12 |  at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:304)
INFO   | jvm 1    | main    | 2017/12/19 14:17:12 |  at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
INFO   | jvm 1    | main    | 2017/12/19 14:17:12 |  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
INFO   | jvm 1    | main    | 2017/12/19 14:17:12 |  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
INFO   | jvm 1    | main    | 2017/12/19 14:17:12 | >
INFO   | jvm 1    | main    | 2017/12/19 14:35:31 | <Dec 19, 2017 2:35:31 PM FET> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read from it on X.X.X.X:65,518 during the configured idle timeout of 5 seconds.>

 

How can i solve it?

Outcomes