Skip to Main Content
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

100 VOTE
Status Under Consideration
Workspace Domino
Categories Administration
Created by Guest
Created on Jan 8, 2020

Make Domino http task more robust.

Make Domino HTTP more robust. Enable it to to force HTTP agents to terminate with out the need for server restarts to clear.

Domino HTTP is a poor "agent manager". More often than not when a HTTP agent times out, HTTP doesn't manage to stop the agent. Often a HTTP restart/quit results in hanging threads instead. Not cool having to do a server restart to handle such issues.

As more and more Domino applications becomes 100% web-applications we need better tools to handle such events without having to restart the Domino server. A restart of HTTP should be powerful enough to handle such "trivial" events.

  • Attach files
  • Guest
    Sep 23, 2023

    Agents have time limits which are configurable. the agent backend code should take care of terminating the agent.

    If you are running into issues like this, this usually is an indication of a different root cause. Mostly it is a matter of designing the application in the right way.

    "hanging shell commands" is a good indication of a badly implemented solution.

    If a thread in an application invokes a "shell" (a different program or system call in general) it gives up contol until this call has ended. There is nothing Domino could do. Or an application in general could do.

    The only way around would be to start it detached and control the execution. In case of a detected hang you would kill the process.

    Another way would be to have a separate thread that performs the call. But then what would you do in case of an detected hang? You can't kill this hanging thread if it is part of your application...

    If you invoke another application (in general not just with Domino) you are giving up control (e.g. system(), popen() and other calls).

    External call-outs are not always to avoid. In case you can't it is your responsibility that the called application returns and does not hang!

  • Guest
    Feb 11, 2020

    This is also an issue on hanging shell commands called via a web agent!