PK82601: Invalid action IDs caused by legacy portlet state manager

APAR status

• Closed as program error.

Error description

• The problem was originally detected in the Personalization UI
  (PZN) which in some cases failed to create new PZN rules. The
  portlet action which was supposed to create the PZN rule was
  not
  invoked by the portal framework.
  The problem, however, is not PZN-specific. Any portlet action
  URL created with the LegacyPortletStateManagerService SPIs
  might have the same problem. Internally the problem is caused
  by
  a PortletRequest object which is not correctly unwrapped to get
  to the original servlet request. This causes problems in all
  portal framework components which use the request object as
  part
  of a cache key. The component which is responsible for creating
  and validating action IDs is one such component.
  
  SYMPTOM:
  
  When trying to add a new PZN rule or edit an existing rule by
  selecting
  a
  value, the information is not saved and the following error is
  printed
  to the Systemout.log:
  
  [5/11/09 11:49:06:119 SGT] 00000204 ActionManager W
  com.ibm.wps.state.accessors.action.manager.ActionManagerImpl
  internalExecuteAction id = n6jfN77400008 is invalid.
  [5/11/09 11:49:06:119 SGT] 00000204 WPActionPhase W
  com.ibm.wps.engine.phases.WPActionPhase processPortlets
  EJPEI0169E:
  Cannot execute the received action
  com.ibm.wps.engine.commands.LegacyActionDispatcher@4bc04bc due
  to a
  security violation. The assigned action ID n6jfN77400008 is
  invalid.
  

Local fix

Problem summary

• The problem was originally detected in the Personalization UI
  (PZN) which in some cases failed to create new PZN rules. The
  portlet action which was supposed to create the PZN rule was not
  invoked by the portal framework.
  The problem, however, is not PZN-specific. Any portlet action
  URL created with the LegacyPortletStateManagerService SPIs might
  have the same problem. Internally the problem is caused by a
  PortletRequest object which is not correctly unwrapped to get to
  the original servlet request. This causes problems in all portal
  framework components which use the request object as part of a
  cache key. The component which is responsible for creating and
  validating action IDs is one such component.
  

Problem conclusion

• This fix makes sure that the PortletRequest is correctly
  unwrapped (by the LegacyPortletStateManagerService) to avoid the
  problems outlined above.
  
  
  Failing Module(s):
     Engine: State handling
  
  Affected Users:
     All
  
  Version Information:
      Portal Version(s): 6.1.0.1
       Pre-Requisite(s): PK79235
        Co-Requisite(s): ---
  
  Platform Specific:
     This fix applies to all platforms.
  
  A fix is available from Fix Central:
  
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  r?apar=PK82601&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

  WEBSPHERE PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R61A PSY

     UP