A fix is available
APAR status
Closed as program error.
Error description
When using wsn-br:RegisterPublisher and leaving wsn-br:Demand element blank the following NullPointerException occurs: [11/15/12 11:39:16:205 EST] 000000a8 WebServiceExc E org.apache.axis2.jaxws.WebServiceExceptionLogger log A java.lang.NullPointerException throwable was caught. The detail message is: at com.ibm.ws.sib.wsn.webservices.impl.inbound.targets.Notification BrokerImpl.registerPublisher(NotificationBrokerImpl.java:395) at com.ibm.ws.sib.wsn.webservices.impl.inbound.provider.NBInvokerIm pl.invoke(NBInvokerImpl.java:190) at com.ibm.ws.sib.wsn.webservices.impl.inbound.provider.NBProviderI mpl.invokeTargetService(NBProviderImpl.java:142) at com.ibm.ws.sib.wsn.webservices.impl.inbound.provider.WSNProvider Impl.invoke(WSNProviderImpl.java:140) at com.ibm.ws.sib.wsn.webservices.impl.inbound.provider.NBProviderI mpl.invoke(NBProviderImpl.java:108) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) .... A SOAPFault is returned to the client.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server WS-Notification * **************************************************************** * PROBLEM DESCRIPTION: NullPointerException when not * * specifying wsn-br:Demand element for a * * wsn-br:RegisterPublisher request. * **************************************************************** * RECOMMENDATION: The wsn-br:Demand element is optional for * * the wsn-br:RegisterPublisher request. The * * WS-Notification implementation should * * handle the case when it is not specified. * **************************************************************** The WS-Notification specification states that "Demand" is an optional element in "RegisterPublisher" and defaults to "false" if not specified. The WebSphere Application Server WS-Notification immplementation should therefore handle "RegisterPublisher" messages with no "Demand" element.
Problem conclusion
This APAR resolves the problem by anticipating that the "Demand" element may not be specified. If it is not specified, it defaults to "false". The fix for this APAR is currently targeted for inclusion in fix pack 8.5.0.2. 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
PM78450
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-12-05
Closed date
2013-01-10
Last modified date
2013-01-10
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
R850 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 November 2021