IBM Support

PI76990: MEDIATION POINTS STUCK IN WAITING FOR STATUS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Mediation Points stuck in Waiting For Status, caused by
    a ClassCastException seen in the logs:
    ----
    java.lang.ClassCastException:
    com.ibm.ws.sib.processor.impl.store.itemstreams.MediatedXmitMsgs
    ItemStream incompatible with
    com.ibm.ws.sib.processor.impl.interfaces.MediationExecutionPoint
            at
    com.ibm.ws.sib.processor.impl.destination.AbstractProtoRealizati
    on.cleanupPremediatedItemStreams(AbstractProtoRealization.java:4
    04)
            ...
    ----
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: SIB mediation points stuck in           *
    *                      "Waiting For status", after being       *
    *                      disabled the enabled in the admin       *
    *                      console.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Mediation Points stuck in Waiting For Status, caused by
    a ClassCastException seen in the logs:
    ----
    java.lang.ClassCastException:
    com.ibm.ws.sib.processor.impl.store.itemstreams.MediatedXmitMsgs
    ItemStream incompatible with
    com.ibm.ws.sib.processor.impl.interfaces.MediationExecutionPoint
    at
    com.ibm.ws.sib.processor.impl.destination.AbstractProtoRealizati
    on.cleanupPremediatedItemStreams(AbstractProtoRealization.java:4
    04)
    ...
    ----
    Incorrect guard logic caused processing to take the wrong
    branch in an if/else block, resulting in code trying to cast
    the mediation object to an incorrect form.
    Adjusting the guard logic by adding and explicit type check
    corrected the problem, allowing to processing to take the
    desired code branch.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI76990

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-22

  • Closed date

    2017-08-16

  • Last modified date

    2017-08-16

  • 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 APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021