IBM Support

PM28119: SEARCH INDEXING HANGS ON INVALID XML FILES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An invalid XML file can cause the text search indexing to hang.
    This is caused by an error in the SAX parser which attempts to
    analyze the XML file during the indexing process.  The invalid
    XML can cause the SAX parser to hang.
    

Local fix

  • Locate and remove the invalid XML document.
    

Problem summary

  • Invalid XML files which are stored as attached binaries can
    cause the search indexing to hang.
    

Problem conclusion

  • PM28119
    =======
    
    Problem Description:
       SEARCH INDEXING HANGS ON INVALID XML FILES
    
    Problem Solution:
      PM28119 contains code changes.
    
    Affected Users:
       All portal users.
    
    Pre-Requisite(s):
       Portal Version: 6.1.0.5
       Portal Fixes:   ---
    
    Installation Steps:
       NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN
    ORDER TO INSTALL A FIX.
              The WebSphere Portal Update Installer (PUI) can be
    downloaded from the following link:
              http://www.ibm.com/support/docview
    .wss?rs=688&uid=swg24006942
    
    *Reminder: the version of PUI used varies based on the version
    of WebSphere Portal.
    Ensure the correct version is in use.*
    
    Refer to the "Maintaining the cluster" topic in the 6.0
    InfoCenter
    (http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index
    .jsp?topic=/com.ibm.wp.ent.doc/wpf/clus_maint.html)
    for additional information on installing or uninstalling interim
    fixes in clustered environments
    while maintaining continuous availability of your portal.
    
    1. Stop the WebSphere Portal server
    2. Apply the PM28119.jar using the PUI (Portal update
    installer).
       Refer to the PUI readme for further information on using the
    PUI.
    3. Restart the WebSphere Portal server.
    
    
    Uninstall:
    NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.
           DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT
    HAVE FIRST BEEN REMOVED.
           YOU MAY REAPPLY ANY REMOVED FIX.
    
    Use the Portal Update Installer to uninstall the fix:
    
       1. Shutdown WebSphere Portal.
       2. Follow the instructions that are packaged with the Portal
    Update Installer on how to uninstall a fix.
       3. Restart WebSphere Portal.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM28119

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7600

  • Reported release

    60E

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-03

  • Closed date

    2010-12-06

  • Last modified date

    2010-12-06

  • 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

  • R60E PSY

       UP

  • R610 PSY

       UP

  • R61A PSY

       UP

  • R61B PSY

       UP

  • R61C PSY

       UP

  • R610 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
06 December 2010