IBM Support

PI81651: PROTOCOL HANDLER TIMES OUT EARLIER THAN EXPECTED WHEN DOORS IS CONFIGURED WITH RDS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • While accessing a URL of an object/module from a DOORS Database
    configured with RDS for authentication, protcolhandler times out
    after 30 seconds and throws the following error:
    Unable to open DOORS URL. Failed to start DOORS client. (You
    must have access to an authenticated DOORS session in order to
    open a DOORS URL)
    
    For a DOORS Database that is not configured with RDS for
    authentication, protocolhandler times out after 120 seconds.
    Steps to reproduce:
    - Configure DOORS Database with latest version of RDS
    - Open a browser and paste a URL of an object or module from a
    DOORS Database configured with RDS for authentication
    - If prompted to choose an application to open the URL
    (DOORS/DOORS Web Access), choose DOORS
    - In the login prompt of DOORS, wait for 30 seconds to induce
    the necessary delay
    
    Expected result:
    Protocol handler should have same timeout, irrespective of DOORS
    is configured for authentication
    
    Actual result:
    Protocol handler times out earlier for a DOORS database
    configured with RDS
    

Local fix

  • Increase the timeout via Registry entry for protocol handler,
    found in HKEY_CLASSES_ROOT\doors\shell\open\command.
    The value of the key represents the command used when a DOORS
    URL is accessed. Increase the value of -s switch, which
    represents the timeout value.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users/environments affected.                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Protocol handler times out earlier than expected when DOORS  *
    * is configured with RDS. While accessing a URL of an          *
    * object/module from a DOORS Database configured with RDS for  *
    * authentication, protcolhandler times out after 30 second.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Client side fix.
    

Problem conclusion

  • This has been resolved in the DOORS 9.6.1.10 release. Timeout is
    now 120 seconds irrespective of whether or not RDS is used.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI81651

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    961

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-15

  • Closed date

    2017-12-15

  • Last modified date

    2017-12-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    TLOGIC DOORS

  • Fixed component ID

    5724V61DR

Applicable component levels

  • R961 PSY

       UP



Document information

More support for: Rational DOORS

Software version: 961

Reference #: PI81651

Modified date: 15 December 2017