PM34046: Too long URLs lead to errors in certain browsers

6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6
7.0.0.2 Download: WebSphere Portal and WCM V7.0 fix pack 2
Fixes integrated in WebSphere Portal 7.0.0.1 & 7.0.0.2 Combined Cumulative Fixes

APAR status

• Closed as program error.

Error description

• Some browsers have a limit for the length of URLs. By
  navigating
  to many pages and interacting with portlets on these pages, the
  navigational state of portal, i. e. the portal URL, can exceed
  this length limit.
  This even can apply if long render parameters are swapped to
  the
  session.
  

Local fix

• n/a
  

Problem summary

• Some browsers have a limit for the length of URLs. By
  navigating to many pages and interacting with portlets on these
  pages, the navigational state of portal, i.e. the portal URL,
  can exceed this length limit. This even can apply if long render
  parameters are swapped to the session.
  

Problem conclusion

• This APAR introduces a way to limit the number of portal pages
  whose navigational state is tracked in the URL. This also
  applies to the navigational state of portlets residing on those
  pages. The basics behind that are documented under
  http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?to
  pic=/com.ibm.wp.ent.doc_v615/admi/historylimit_scn.html.
  However, the property mentioned there ("keymanager.lru.size" in
  the "WP StateManagerService properties") to limit the history
  applies only to the render parameters that are sourced out to
  the session.
  
  Manual Steps:
  With this APAR some new configuration possibilites were
  introduced.
  These can be set in the resource environment provider "WP
  StateManagerService":
  
        historymanager.enabled
  
  The HistoryManager allows to cleanup state for pages visited
  some time ago.
  Allowed values are "true" or "false".
  Default value is "true".
  Example: historymanager.enabled = true
  
  
        historymanager.threshold
  
  The threshold meaning the number of pages whose portlets and
  shared state should be kept. Must be a positive integer.
  Default value is "10"
  Example: historymanager.threshold = 10
  
        historymanager.prp.removalstrategy
  
  Defines a strategy how the shared state is cleaned up. Possible
  values are "no_removal", "wcm_id" or
  "explicit_bucket_assignment"
  The meaning of these values is as follows:
       - "no_removal":
             public render parameters will not be removed, i. e.
  only portlet specific state will be removed.
       - "wcm_id":
             Public render parameters will be removed if the
  expired page has an explicit shared state bucket assigned that
  starts with the String "ibm.wcm."
       - "explicit_bucket_assignment":
             Public render parameters will be removed if the
  expired page has an explicit shared state bucket assigned --
  regardless of a prefix. This is a more general strategy than
  "wcm_id".
  Default value is "explicit_bucket_assignment"
  Example: historymanager.prp.removalstrategy =
  explicit_bucket_assignment
  
  Platform Specific:
     This fix applies to all platforms.
  
  PM34046 is part of Cumulative Fix 13 - available on Fix
  Central.
  
  Portal 6.1.0.5 / 6.1.5.2:
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  r?apar=PM33742&productid=WebSphere%20Portal&brandid=5
  
  You may need to type or paste the complete address into your Web
  browser.
  

Temporary fix

Comments

APAR Information

• 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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R610 PSY

     UP

• R615 PSY

     UP