Accessing ClearQuest Web fails with Error 500 java.lang.NullPointerException when hyperlinking to, refreshing login page, or attempting connect from separate web-browser tab

Flash (Alert)


Abstract

This Flash Alert is meant to inform you of an issue that occurs after upgrading IBM Rational ClearQuest (CQ) Web server to the CQ 7.1.2.10 or CQ 8.0.0.6 fixpacks, where users may receive a blocking Error 500 java.lang.NullPointerException.

Content

This issue has been identified as a product defect under APAR PM86523.

The CQ Web SystemOut.log logs will also mention NullPointerExceptions.

While this error may be blocking within the current browser tab, the Change Management (CM) Server is still active.

Temporary workarounds:

  • Clear your browser cache, and connect only within a single browser-tab to CQ Web.

  • The CQ Web server is not down. If you connect from another machine, clear the browser cache, or use a new browser you can still log in.

WORKAROUND

To resolve the problem prior to the APAR disposition:

  1. Stop all CQ Web services (such as cqwebprofile/cmprofile).

  2. Locate the common.jsp file as follows:

    CQ 7.1.2.10:
    <rational_common>\CM\profiles\cmprofile\installedApps\dfltCell\TeamEar.ear\cqweb.war\jsp\

    CQ 8.0.0.6:
    <cqwebprofile>\installedApps\dfltCell\TeamEAR.ear\cqweb.war\jsp\

  3. Backup the common.jsp file to common.jsp.original and keep it in a safe location, outside of this directory if possible (to prevent upgrade or install issues in the future).

  4. Modify the common.jsp file as follows:

    Find the section of code:


    loginId = (String)loginService.getLoginUserId();
    loginId = loginId.replaceAll("\"", "&#34;"); // WI40585
    if(loginId == null) loginId = "";


    Replace with:


    loginId = (String)loginService.getLoginUserId();
    if(loginId == null) loginId = "";
    loginId = loginId.replaceAll("\"", "&#34;"); // WI40585


    Save the file changes.

    Note: Unless otherwise recommended by IBM Rational Client Support, it is not supported to modify this file under any other circumstances other than the above mentioned workaround.

  5. Delete or rename the "_index.class" file to clear out the WebSphere Application Server (WAS) profile cache on the server:

    CQ 7.1.2.10:
    <rational_common>\CM\profiles\cmprofile\temp\dfltNode\server1\TeamEAR\cqweb.war\_index.class

    CQ 8.0.0.6:
    <cqwebprofile>\temp\dfltNode\server1\TeamEAR\cqweb.war\_index.class

  6. Start the CQWeb services

  7. Verify that a new "_index.class" file is created on the first attempt to access CQ Web.

  8. Clear the browser cache and close the browser.

  9. Re-open the browser and test or validate the solution.

Rate this page:

(0 users)Average rating

Document information


More support for:

Rational ClearQuest
Web Client (7.1)

Software version:

7.1.2.10, 8.0.0.6

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1633978

Modified date:

2013-04-11

Translate my page

Machine Translation

Content navigation