PM65729: MS TRAPS ARE NOT TRIGGERED BY PORTAL REQUEST EVENTS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Problem Abstract: MS Traps do not fire for Portal request events
    
    ---------------------------------
    Users Affected: Users setting traps against Portal requests
    
    ---------------------------------
    Problem Description: Traps created to fire against the names of
    Portal request events are never triggered
    
    The customer creates some Portal type events by accessing WAS
    Portal applications. The portal request events are verified when
    looking at Server Activity Display (in the Recent Requests tab)
    and in the Performance Analysis Reports.
    
    However if the customer takes the string that forms the name of
    the Portal request event and uses this to create a trap, it
    never triggers even though we are sure the portal event was
    created
    
    ---------------------------------
    Keyword/Symptom: INCORROUT
    
    ---------------------------------
    Component ID: 5724Y92MS
    
    ---------------------------------
    Severity: 2
    
    ---------------------------------
    Local Fix/Workaround: N/A
    
    
    ---------------------------------
    Approvals:
    
    L2: Oneil Richardson
    L3: Keyuri Patel
    ---------------------------------
    

Local fix

  • N/A
    

Problem summary

  • USERS AFFECTED: Customers trying to set traps against portal
    requests
    
    PROBLEM DESCRIPTION: Traps created to fire against the names of
    Portal request events are never triggered
    The customer creates some Portal type events by accessing WAS
    Portal applications. The portal request events are verified when
    looking at Server Activity Display (in the Recent Requests tab)
    and in the Performance Analysis Reports.
    However if the customer takes the string that forms the name of
    the Portal request event and uses this to create a trap, it
    never triggers even though we are sure the portal event was
    created
    
    RECOMMENDATION: Apply the fix 7103 ifix4
    

Problem conclusion

  • The traps were not triggered for portal
    requests because DC was never sending a request name in the
    entry/start request. DC only sent request name in the exit
    record. Venkatesh said it is tricky to fix this on DC side so I
    fixed it on MS side with a workaround. I am bypassing the
    condition for portal server where traps condition are checked
    for entry event.
    
    The fix for this APAR is included in 7.1.0.3 Ifix4
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM65729

  • Reported component name

    TCAM AD MAN SER

  • Reported component ID

    5724Y92MS

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-29

  • Closed date

    2013-01-29

  • Last modified date

    2013-01-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

    TCAM AD MAN SER

  • Fixed component ID

    5724Y92MS

Applicable component levels

  • R710 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Composite Application Manager for Application Diagnostics
ITCAM for APPLICATION DIAGNOSTICS Managing Server

Software version:

710

Reference #:

PM65729

Modified date:

2013-01-29

Translate my page

Machine Translation

Content navigation