Error java io IOException Cannot read connection identification byte

[Former Member]

Hi,

I have EP 7.0 SP 16. with Web Dispatcher and in the default.trc log file are a lot of this error:

java.io.IOException: Cannot read connection identification byte.

at com.sap.engine.core.cluster.impl6.JoinPortListener$SocketProcessor.run(JoinPortListener.java:156)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

This error appear 500 times in 30 minutes aprox.

¿Could it be a error of SSL?

And we have this warnig a lot of times too:.

Cannot get input and output streams from socket. ConnectionsManipulator is not initialized.

java.io.EOFException: Connection closed by remote host.

at iaik.security.ssl.Utils.a(Unknown Source)

at iaik.security.ssl.o.c(Unknown Source)

at iaik.security.ssl.r.f(Unknown Source)

at iaik.security.ssl.f.c(Unknown Source)

at iaik.security.ssl.f.a(Unknown Source)

at iaik.security.ssl.r.d(Unknown Source)

at iaik.security.ssl.SSLTransport.startHandshake(Unknown Source)

at iaik.security.ssl.SSLSocket.startHandshake(Unknown Source)

at com.sap.engine.services.ssl.factory.SSLSocket.startHandshake(SSLSocket.java:162)

at com.sap.engine.services.ssl.factory.SSLSocket.getInputStream(SSLSocket.java:280)

at com.sap.engine.core.manipulator.TCPRunnableConnection.init(TCPRunnableConnection.java:351)

at com.sap.engine.core.manipulator.TCPRunnableConnection.run(TCPRunnableConnection.java:554)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:80)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:150)

¿Could it be relationed?.

Thanks in advance.

[Former Member · Accepted solution]

Hi,

When the error happens, does the server hang? Is the error reproducible?

Please try changing the lazy.autoclose.timeout property in configtool

Note 885645 J2EE Engine Server Node Hangs because of lazy communication

Best regards,

Warren

[Former Member · Accepted solution]

Thanks a lot by the answer.

-The error happens very often(500 times en 30 minutes aprox.)

-does the server hang?, The server hang one week ago, then the memory was increased and now work well, but I am afraid that it will hang againg when the load increase.

- Is the error reproducible?, No, We don´t know what is the source of the error.

We check the value of the lazy.autoclose.timeout property in configtool and is 0, like the note recommends

¿Any other ideas, please?.

[Former Member]

Any solution for this? I also getting this error. The program required to read the XML Response from the URL called. It only happened to some URL that I passed with the parameter ' in the URL. It won't hang the server due to it is exception handled therefore just my program will flagged as unsuccessful call but actually it already process the request.

Thanks.

[Former Member]

We are getting this message :

Cannot get input and output streams from socket. ConnectionsManipulator is not initialized.

And we are also on NW7 SP16. Any ideas what causes this or how to fix?

Thanks,

BK