A socket read timeout occured. The read will be retried

[Joao Ramos]

Hi community,

We have 1 server with only the VSE componente(TU is the name of the vse).

Looking at the logs for this server, we keep getting this warn message and nothing else:
It is bad to debug other errors.

"A socket read timeout occured. The read will be retried"

Can you tell me what this might be or how to remove this message from the log?

Server details: Windows 2016 R2 (64-bit). DevTest 10.5

Regards
João Paulo Ramos

------------------------------
System Analyst
Bradesco
------------------------------

Attachment(s)

vse.log   5.43 MB 1 version

[Senthil Manohar]

Hi Joao Paulo Ramos,

I reviewed the log and it's just a WARN message which you can choose to ignore. However, it seems to be occurring often and your log file keeps growing as well, which would result in memory issues in a long run.

Couple of questions

-Is this a Performance VSE?
-How long you have been seeing this WARN? (this just started coming up? or it's been there for long time)

You need to find out the root-cause for the Socket read timeout and I assume you have right configurations for the VSE.

Please check the below knowledge article, which might give you more insights.

https://knowledge.broadcom.com/external/article/121588/warn-comitkolisavsesiooldiosession-a-so.html
https://knowledge.broadcom.com/external/article/115806/vse-is-crashing-after-load-test-is-perfo.html

Thanks,
Senthil Manohar
Atos

[Vaibhav Jain]

Hi Ramos,

Socket timeout warnings are frequent in logs as it will wait for a predefined time and keep trying to establish the connection.

You can use the below property in your properties file to avoid it:
log4j.logger.com.itko.lisa.vse.sio.OldIOSession=ERROR

Hope this will help to suppress these messages.

Thanks

------------------------------
Regards,
Vaibhav Jain
Capgemini
------------------------------

[Joao Ramos]

​Hi Guys,

Yes, there is the possibility of using the VSE as Performance. We've been seeing this message for a few months.

I looked through the articles and made the changes but the warn's keeps showing.
I'm attaching the log and local.propertie.

Regards,

------------------------------
System Analyst
Bradesco
------------------------------

Attachment(s)

vse.log   180 KB 1 version

[Vaibhav Jain]

Could you share the properties file once again, I am unable to find it previous messages. Also, I assume you already restarted the components post changes in the properties file.

Thanks

------------------------------
Regards,
Vaibhav Jain
Capgemini
------------------------------

[Joao Ramos]

​Attached

------------------------------
System Analyst
Bradesco
------------------------------

Attachment(s)

local_Community.txt   16 KB 1 version

[Vaibhav Jain]

Hi Ramos,

You should add the property "lisa.vse.ssl.tcp.uses.nio=false" in VSE local.properies
and add the property "log4j.logger.com.itko.lisa.vse.sio.OldIOSession=ERROR" in your logging.properties not local.properties.

Thanks

------------------------------
Regards,
Vaibhav Jain
Capgemini
------------------------------