IBM Support

PM60748: UNABLE TO USE CQWEB WHEN 3RD PARTY PRODUCT USES JSESSIONID, EVEN WHEN CQWEB IS CONFIGURED TO USE MODIFIED COOKIE NAME.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Use of 3rd party product that generates a JSESSIONID  named
    cookie with path '/' in the same web-browser session causes
    various CQ Web critical functionality to fail in version 7.1 and
    8.0.
    
    Workarounds:
    Use another web-browser, or do not use 3rd party product that
    creates JSESSIONID cookies in your browser that will also be
    used for a CQ Web session.
    
    Note:
    Changing of ClearQuest Web default cookie name from JSESSIONID
    to something else, while taking affect, does not override the
    behavior of the presence of another JSESSIONID.
    
    Symptoms include:
    1) CQ Navigator for workspace appears empty (no Personal or
    Public Queries folders shown).
    2) Unable to load a form for a record submit.
    3) Unable to populate list of submittable record types.
    4) Unable to load User Profile editor.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    By default, after deploying ClearQuest Web on an IBM
    WebSphere Application Server, the JSESSIONID cookie path is
    set to the domain root /. If there are other web
    applications running on WebSphere Application Server that
    set the JSESSIONID cookie path to /, this creates a
    JSESSIONID conflict, which causes ClearQuest Web functions
    to fail.
    

Problem conclusion

  • A fix is available in ClearQuest 7.1.2.9 and 8.0.0.5.
    
    The ClearQuest Web session id name is no longer hard coded
    to use JSESSIONID.  If there's a JESSIONID conflict, the
    ClearQuest Web session id can now be renamed.
    
    The following technote also explains an alternate
    workaround:
    http://www-01.ibm.com/support/docview.wss?uid=swg21595387
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM60748

  • Reported component name

    CLEARQUEST WIN

  • Reported component ID

    5724G3600

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-19

  • Closed date

    2012-12-15

  • Last modified date

    2012-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

    CLEARQUEST WIN

  • Fixed component ID

    5724G3600

Applicable component levels

  • R800 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 December 2012