IBM Support

IV52034: NULLPOINTEREXCEPTION WHEN RUNNING SUBSCRIPTIONNOTIFIER WITH SECURITY DISABLED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If running the SubscriptionNotifier scheduled task on a system
    that does not have security enabled you will see the following
    NullPointerException reported in the SystemOut.log
    
    CNTR0020E: EJB threw an unexpected (non-declared) exception
    during invocation of method "processNotifications" on bean
    "BeanId(ServiceRegistry#ServiceRegistrySubscriptionNotifier.jar#
    SubscriptionNotifierNotification, null)". Exception data:
    java.lang.NullPointerException
    at
    com.ibm.sr.subscriptionnotifier.plugin.SubscriptionNotifierNotif
    icationBean.generateRoleMappings(SubscriptionNotifierNotificatio
    nBean.java:518)
    at
    com.ibm.sr.subscriptionnotifier.plugin.SubscriptionNotifierNotif
    icationBean.processNotifications(SubscriptionNotifierNotificatio
    nBean.java:140)
    at
    com.ibm.sr.subscriptionnotifier.plugin.EJSLocalStatelessSubscrip
    tionNotifierNotification_cd2e8e02.processNotifications(EJSLocalS
    tatelessSubscriptionNotifierNotification_cd2e8e02.java:29)
    at
    com.ibm.sr.subscriptionnotifier.plugin.SubscriptionNotifierPlugi
    nMessageTask.postExecute(SubscriptionNotifierPluginMessageTask.j
    ava:344)
    at
    com.ibm.sr.scheduler.SchedulerMultiTranTaskBean.process(Schedule
    rMultiTranTaskBean.java:338)
    at
    com.ibm.websphere.scheduler.EJSRemoteStatelessSchedulerMultiTran
    Task_84cc3836.process(EJSRemoteStatelessSchedulerMultiTranTask_8
    4cc3836.java:28)
    at
    com.ibm.websphere.scheduler._TaskHandler_Stub.process(_TaskHandl
    er_Stub.java:269)
    at
    com.ibm.ws.scheduler.tasks.BeanTaskInfoWork.doWork(BeanTaskInfoW
    ork.java:126)
    at
    com.ibm.ws.scheduler.AlarmListener.executeTaskWithNotification(A
    larmListener.java:807)
    at
    com.ibm.ws.scheduler.AlarmListener.access$700(AlarmListener.java
    :124)
    at
    com.ibm.ws.scheduler.AlarmListener$TaskWork.doWork(AlarmListener
    .java:436)
    at
    com.ibm.ws.scheduler.AlarmListener$TaskWork.run(AlarmListener.ja
    va:222)
    at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:809)
    at
    com.ibm.ws.asynchbeans.ExecutionContextImpl.go(ExecutionContextI
    mpl.java:86)
    at
    com.ibm.ws.scheduler.AlarmListener.fireTask(AlarmListener.java:1
    416)
    at
    com.ibm.ws.scheduler.AlarmListener.fired(AlarmListener.java:1334
    )
    at
    com.ibm.ws.asynchbeans.AlarmImpl.callListenerMethod(AlarmImpl.ja
    va:427)
    at
    com.ibm.ws.asynchbeans.timer.GenericTimer.run(GenericTimer.java:
    228)
    at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1178)
    at
    com.ibm.ws.asynchbeans.AlarmImpl.runListenerAsCJWork(AlarmImpl.j
    ava:249)
    at com.ibm.ws.asynchbeans.am._Alarm.fireAlarm(_Alarm.java:333)
    at com.ibm.ws.asynchbeans.am._Alarm.run(_Alarm.java:230)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1659)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Service Registry and Repository V7.5
    
    ****************************************************************
    PROBLEM SUMMARY:
    When the system does not have security enabled certain tasks
    performed by the SubscriptionNotifier in WSRR will not work
    and will cause NullPointerExceptions to be thrown.
    

Problem conclusion

  • The SubscriptionNotifier was changed to detect whether
    security is enabled before performing tasks which require
    security to be enabled.
    
    This fix is targeted for inclusion in WSRR V7.5.0.4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV52034

  • Reported component name

    SERVICE REGISTR

  • Reported component ID

    5724N7200

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-14

  • Closed date

    2013-11-14

  • Last modified date

    2013-11-14

  • 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

    SERVICE REGISTR

  • Fixed component ID

    5724N7200

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 November 2013