HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Add a new idea Subscribe
Status Needs Review
Workspace Notes
Created by Guest
Created on Sep 30, 2024

RELATED IDEAS

Keep Alive TCP 1352 protocol

This is a common and old problem about Notes NRPC in a network.

The protocol TCP don't have a keep alive inside...

Many experience here:


https://www.dominopoint.it/dominopoint/dominopoint_blog.nsf/dx/keepalive-notes-client-problemi-sedi-remote-timeout

https://support.hcltechsw.com/community?id=community_question&sys_id=b2b698521b50b010f37655352a4bcb05


https://kb.juniper.net/InfoCenter/index?page=content&id=KB7258&actp=METADATA


and this old KB:


https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0079436



If HCL will support inside TCP 1352 the keep alive feature... this will solve all problem


Also this is the same issue:

https://domino-ideas.hcltechsw.com/ideas/DOMINO-I-2415





  • Attach files
  • Guest
    Reply
    |     Oct 25, 2024

    Linux and MacoOS have a default keep alive of 75 seconds.
    This is really a Windows issue. A two hour default keep altive packet send interval isn't really helpful.
    All other stateful applications would suffer from the same long default.

    IMHO it makes more sense to ask Microsoft to change their default to the same 75 seconds.


Copyright © 2023 HCL Technologies Limited