IT08003: NULLPOINTEREXCEPTION SEEN WHEN USING JAXWS BINDINGS AND ENDPOINTREFERENCE TYPES

8.5.6.0-WS-BPM-IFIT08003
bpm.8560.cf1.delta.repository.1
bpm.8560.cf1.delta.repository.2
Version 8.5 Refresh Pack 7 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• If a number of flows that use JAXWS Bindings and
  Endpointreference types are started at application start-up then
  a concurrency issue may occur that results in the address of the
  EndpointReference being null and a NullPointerException is seen.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of Business Process Manager v8.5 who use JAX-WS bindings
  with mediation flows.
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  At start-up, if multiple threads are initially invoked, a
  NullPointerException may be seen with the additional description
  that the property argument passed into the method 'set(Property
  prop, Object value)' is null. This is due to a concurrency issue
  with the a property of the flow.
  

Problem conclusion

• The concurrency issue has been resolved.
  
  This code fix was targeted to be included in the following fix
  packs:
  
  BPM v8.5.7.0
  

Temporary fix

Comments

APAR Information

• 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

  WESB IN BPM

• Fixed component ID

  AIMCMFC00

Applicable component levels