PK97946: PORTAL SERVER THREAD HANG AFTER OCCURENCE OF ILLEGALARGUMENTEXCE PTION

Recommended Updates for WebSphere Portal and Web Content Management V6.0
6.0.1.7 Download: WebSphere Portal and Web Content Manager V6.0.1, fix pack 7

APAR status

• Closed as program error.

Error description

• Root cause is an IllegalArgumentException from theme code in
  the
  UrlGenerationTag:
  com.ibm.wps.engine.tags.UrlGenerationTag doStartTag EJPEJ0002E:
  An error occurred while executing CreateUrlCommand.
  
  com.ibm.wps.command.CommandException: EJPEJ0013E: Execution of
  CreateUrlCommand failed.
  at
  com.ibm.wps.util.CreateUrlCommand.execute(CreateUrlCommand.java:
  
  310)
  at
  com.ibm.wps.engine.tags.UrlGenerationTag.doStartTag(UrlGeneratio
  
  Tag.java:245)
  at com.ibm._jsp._Default._jspService(_Default.java:1382)
  Caused by: java.lang.IllegalArgumentException: ObjectID is of
  wrong ResourceType!
  
  This causes a locking issue so that subsequent threads that are
  performing data modification (e.g. page layout changes) are
  hung. This is indicated by WAS warning in log file:
  WSVR0605W: Thread "WebContainer : 4" (00000050) has been active
  for 664095 milliseconds and may be hung.  There is/are 1
  thread(s) in total in the server that may be hung.
  WSVR0605W: Thread "WebContainer : 7" (0000005c) has been active
  for 619985 milliseconds and may be hung.  There is/are 2
  thread(s) in total in the server that may be hung.
  

Local fix

• NA
  

Problem summary

• Root cause is an IllegalArgumentException from theme code in the
  UrlGenerationTag:
  com.ibm.wps.engine.tags.UrlGenerationTag doStartTag EJPEJ0002E:
  An error occurred while executing CreateUrlCommand.
  Caused by: java.lang.IllegalArgumentException: ObjectID is of
  wrong ResourceType!
  
  This causes a locking issue so that subsequent threads that are
  performing data modification (e.g. page layout changes) are
  hung.
  This is indicated by WAS warning in log file:
  WSVR0605W: Thread "WebContainer : 7" (0000005c) has been active
  for 619985 milliseconds and may be hung.  There is/are 2
  thread(s) in total in the server that may be hung.
  

Problem conclusion

• This APAR corrects the exception handling in model
  synchronization code.
  
  Manual Steps:
     None
  
  Failing Module(s):
     Engine: Tags & Commands
  
  Affected Users:
     All users
  
  Version Information:
      Portal Version(s): 6.0.1.3
       Pre-Requisite(s): PK72523 PK72210
        Co-Requisite(s): ---
  
      Portal Version(s): 6.0.1.5
       Pre-Requisite(s):
        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=PK97946&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

• R60G PSY

     UP

• R60J PSY

     UP