IBM Support

PM66727: Issues when adding ws handler to Notification Service

Fixes are available

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Issues  encountered when trying to add ws handler to
    the Notification Service for outbound invocation handling.
    
    1.Exceptions encountered when trying to add ws handler to the
    Notification Service for outbound invocation handling.
    
    2.After Notification Service has been created, add ws handler
    to the notification service, another exception encountered.
    However,next time you go back to the notification service, ws
    handler seems has been added and asked you to save the change.
    
    3. After notification service has been created, adding the ws
    handler the service point for inbound invocation handling. This
    procedure finished successfully, however, the ws handler logic
    is not being invoked.
    
    4. On another attempt, adding the ws handler to the service
    point while creating the notification service and service
    point. This time,the result shows that the ws handler logic was
    being invoked for inbound invocation.
    
    5. Removing the ws handler from droplist on notification
    service point, the ws handler logic is still being invoked. It
    seems like the operation of removing the ws handler from the
    service point does not work.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application                   *
    *                  Server users of JAX-WS Outbound handlers    *
    *                  with WS-Notification.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Errors reported when configuring a      *
    *                      WS-Notification service to use a        *
    *                      JAX-WS outbound handler.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When specifying a WS-Notification service JAX-WS outbound
    handler, a NoClassDefFoundError was reported by the
    administration console. After saving the configuration change,
    the outbound handler was not invoked by the WS-Notification
    service as expected.
    

Problem conclusion

  • The administration console has been updated to correctly alter
    the WS-Notification service configuration. The underlying web
    services runtime has also been updated to correctly invoke the
    handlers.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.27, 8.0.0.5, and 8.5.0.1.  Please refer to the
    Recommended
    Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM66727

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-13

  • Closed date

    2012-08-22

  • Last modified date

    2012-08-22

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM66727

Modified date: 22 August 2012