IBM Support

PI21719: PROBLEMS WITH LOAD BALANCED DWA ENVIRONMENT - LOGGING IN TO DWA FROM RTC IS ERRATIC

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • From DWA to RTC everything is working as expected (create new
    items,mouse hover,....).
    From RTC to DWA everything is working as long as we use only ONE
    DWA instance within the DWA cluster. As soon as a second DWA
    instance is activated and has also active sessions, the
    following problems occur (after some time):
    
    Associate Project Area with Doors Repository
    1. Open Project Area Configuration
    2. Add Association
    3. Select Doors
    4. Login Window Pops Up in a separate window
    5. Enter Username ? Password
    6. Login Pop-Up reloads / same view / no error msg
    7. Enter Username ? Password
    8. DWA View on Repository opens in a separate window
    9. No Doors Information is provided within RTC Association
    Window
    
    Hover Over in RTC
    1. Associate Doors Req to RTC WI (in Doors)
    2. Open Work Item in RTC
    3. Go to Links Tab ? Hover Over on Doors Link
    4. 'Please login to view information' -? Click login
    4. Login Window Pops Up in a separate window
    5. Enter Username ? Password
    6. Login Pop-Up reloads / same view / no error msg
    7. Enter Username ? Password
    8. DWA View on Repository opens in a separate window (looks like
    the original login window)
    9. Hover Over the Doors Links again -? 'Please login to view
    information'
    User is sent into a loop of continually being asked to login
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who have integrated DOORS with RTC/RQM via OSLC.       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Logging in from RTC/RQM can present multiple login           *
    * challenges. This problem only presents when multiple DWA     *
    * server are in use.                                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    * DWA users sticky sessions.
    * Sticky sessions require a user session.
    * User sessions are identified by jsession id.
    * This is shared between client (in DWA domain) and Tomcat.
    * OAuth requires 3 requires to authenticate:
     - get request token
     - get auth token
     - get access token
    * Only the the second stage (get auth) has access to the
    jsession id.
    * It is possible for any of these requests to go to a different
    server.
    * This will not work as DWA server do not currently share any
    information.
    
    The change was to enable all DWA servers to have access to the
    OAuth tokens.
    

Problem conclusion

  • This has been resolved in the 9614 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI21719

  • Reported component name

    TLOGIC DOORS WE

  • Reported component ID

    5724V97WA

  • Reported release

    130

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-10

  • Closed date

    2015-10-23

  • Last modified date

    2015-10-23

  • 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 WE

  • Fixed component ID

    5724V97WA

Applicable component levels

  • R961 PSY

       UP



Document information

More support for: Rational DOORS

Software version: 1.3

Reference #: PI21719

Modified date: 23 October 2015