IT44662: USING NAMESPACE PREFIX WITHOUT DEFINING IT IN THE WSDL FILE RESULTS IN NULL POINT EXCEPTION IN ACE V12.

APAR status

• Closed as program error.

Error description

• Error while deploying the bar file after migrating the
  applications from IIB V10 to ACE V12 with the flows using SOAP
  functionality.
  
  Error:
  
  BIP3701E: A Java exception was thrown whilst calling the Java
  JNI method
  'method_com_ibm_broker_axis2_Axis2NodeRegistrationUtil_registerS
  yncRequestNode'. The Java exception was
  'java.lang.NullPointerException'. The Java stack trace was
  'Frame : 0 java.lang.NullPointerException: null| @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager$SearchableImportList.
  getData(WSDLDefinitionsManager.java:2862)| @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager.bindingShred(WSDLDefi
  nitionsManager.java:1896)| @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager.refreshBindingsFromWS
  DL(WSDLDefinitionsManager.java:1166)| @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager.refreshBindings(WSDLD
  efinitionsManager.java:1045)| @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager.getBinding(WSDLDefini
  tionsManager.java:749)| @:
  com.ibm.broker.axis2.Axis2NodeRegistered$SOAPConfig.setupSOAPPip
  eline(Axis2NodeRegistered.java:603)| @:
  com.ibm.broker.axis2.Axis2NodeRegistered$SOAPConfig.<init>(Axis2
  NodeRegistered.java:326)| @:
  com.ibm.broker.axis2.Axis2NodeRegistered.<init>(Axis2NodeRegiste
  red.java:164)| @:
  com.ibm.broker.axis2.Axis2EngineManager.registerNode(Axis2Engine
  Manager.java:91)| @:
  com.ibm.broker.axis2.Axis2NodeRegistrationUtil.registerSyncReque
  stNode(Axis2NodeRegistrationUtil.java:357)|'.
  
  The above error resulted due to usage of namespace prefix "xsi"
  without defining it in the WSDL file.
  
  Error captured in server console.txt:
  
  [Fatal Error] :12:188: The prefix "xsi" for attribute
  "xsi:schemaLocation" associated with an element type "part" is
  not bound.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All Users of IBM App Connect Enterprise v12 who uses the
  namespace prefix without defining it in the WSDL file.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Deploying a bar file after migrating the applications from IBM
  Integration Bus V10 to App Connect Enterprise V12 with the flows
  using SOAP functionality may result into following errors:
  
  BIP3701E: A Java exception was thrown whilst calling the Java
  JNI method
  'method_com_ibm_broker_axis2_Axis2NodeRegistrationUtil_registerS
  yncRequestNode'. The Java exception was
  'java.lang.NullPointerException'. The Java stack trace was
  'Frame : 0 java.lang.NullPointerException: null|
  @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager$SearchableImportList.
  getData(WSDLDefinitionsManager.java:2862)|
  @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager.bindingShred(WSDLDefi
  nitionsManager.java:1896)|
  @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager.refreshBindingsFromWS
  DL(WSDLDefinitionsManager.java:1166)|
  @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager.refreshBindings(WSDLD
  efinitionsManager.java:1045)|
  @:
  com.ibm.broker.wsdl.WSDLDefinitionsManager.getBinding(WSDLDefini
  tionsManager.java:749)|
  @:
  com.ibm.broker.axis2.Axis2NodeRegistered$SOAPConfig.setupSOAPPip
  eline(Axis2NodeRegistered.java:603)|
  @:
  com.ibm.broker.axis2.Axis2NodeRegistered$SOAPConfig.<init>(Axis2
  NodeRegistered.java:326)|
  @:
  com.ibm.broker.axis2.Axis2NodeRegistered.<init>(Axis2NodeRegiste
  red.java:164)|
  @:
  com.ibm.broker.axis2.Axis2EngineManager.registerNode(Axis2Engine
  Manager.java:91)|
  @:
  com.ibm.broker.axis2.Axis2NodeRegistrationUtil.registerSyncReque
  stNode(Axis2NodeRegistrationUtil.java:357)|'.
  
  The above error resulted due to usage of namespace prefix "xsi"
  without defining it in the WSDL file.
  
  Error captured in server console.txt:
  
  [Fatal Error] :12:188: The prefix "xsi" for attribute
  "xsi:schemaLocation" associated with an element type "part" is
  not bound.
  

Problem conclusion

• The product has been modified to handle the Null Pointer
  Exception so that the original WSDL file works as expected.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v12.0      12.0.11.0
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  APP CONNECT ENT

• Fixed component ID

  5724J0560

Applicable component levels