IBM Support

PM75463: PORTLET AGGREGATION TAG LIBRARY DOES NOT WORK WITH REMOTE REQUEST DISPATCHER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the portlet aggregation tag library is used to
    reference portlets that are enabled for Remote Request
    Dispatcher and are deployed on a remote server, the request
    for the remote portlet may fail with the following error
    message:
    
    Error 500:
    com.ibm.wsspi.portletcontainer.InvalidPortletWindowIdentifierExc
    eption:Context path cannot be found: <context path>
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: In combination with Remote              *
    *                      Request Dispatchter the Portlet         *
    *                      Aggregation Tag Library may fail with   *
    *                      error 500.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Portlet Aggregation Tag Library code fails to create local
    web application definition proxy objects for remote web
    applications when Remote Request Dispatcher is used. Since the
    portlet container code that is invoked by the tag library
    expects web application definition objects it will fail if the
    object is not found.
    

Problem conclusion

  • The Portlet Aggregation Tag Library is changed to create local
    web application definition proxy objects when Remote Request
    Dispatcher functionality is used. These proxy objects
    represent remote web application definitions and are then used
    by the portlet container.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.6 and 8.5.0.2.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM75463

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-19

  • Closed date

    2012-11-13

  • Last modified date

    2012-11-13

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021