IBM Support

PM04261: SEMANTIC TAG SERVICE INITIATING TOO MANY HTTP REQUESTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Adding the following line to the rendering JSP of Place
    Center/Search Center application, integrates with Portal's
    semantic tag service, and will add "live" behavior for
    displayed people names.
    
    <script type='text/javascript'
    src='/wps_semanticTag/javascript/semanticTagService.js'></script
    
    However, this has significant performance overhead. This
    Javascript code initiates 8 more http requests before any user
    interaction, most  of them not cacheable.
    

Local fix

  • A patch has been created that successfully addresses this issue.
    

Problem summary

  • Fixed in WebSphere Portal Version 6.1.0.4 and 6.1.5.1.
    

Problem conclusion

  • Fixed in WebSphere Portal Version 6.1.0.4 and 6.1.5.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM04261

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7600

  • Reported release

    615

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-30

  • Closed date

    2010-06-29

  • Last modified date

    2010-06-29

  • 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

  • R610 PSY

       UP

  • R615 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.1.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 June 2010