JR44357: CWLLG0594E DUE TO NULLPOINTEREXCETION IN SOAPCONNECTORCACHEDATA WHEN THE STORED PORTNAME IS NOT FOUND IN THE ACTUAL WSDL.

Version 7.5.1 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• SOAPConnectorCacheData needs to guard against
  java.lang.NullPointerException (NPE) when the stored portName
  is not found in the actual WSDL.
  
  A variable that contains the port value of ILOG environments
  (development/test and production). The definition has been based
  on the link:
  
  http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/c
  om.ibm.wbpm.wle.editor.doc/topics/building_rule_service_C.html
  
  Development/test env port: 8879
  Production env port: 8880
  
  Application runs fine while calling rules from ILOG test server
  (port 8879) but is fails while calling the rule ILOG from
  prodution server (port 8880).
     The cause is that there was an inconsistency between the
  WSDL being loaded at runtime and the metadata stored for that
  WSDL.
  
  [7/27/12 12:24:06:906 BRT] 00000070 wle E CWLLG0594E: An
  exception occurred while initializing the runnable thread.
  Error:
  com.lombardisoftware.component.common.workflow.WorkflowProcessIt
  emException: java.lang.NullPointerException
  com.lombardisoftware.component.common.workflow.WorkflowProcessIt
  emException: java.lang.NullPointerException
  at
  com.lombardisoftware.component.common.workflow.ExecutionJob.doJo
  b(ExecutionJob.java:415)
  at
  com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
  doResumeWorkflowEngine(EJBWorkflowManagerBean.java:1009)
  at
  com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
  resumeTask(EJBWorkflowManagerBean.java:296)
  ...
  Caused by: java.lang.NullPointerException
  at
  teamworks.connector.SOAPConnectorCacheData.<init>(SOAPConnectorC
  acheData.java:50)
  at
  teamworks.connector.SOAPConnector.executeInternal(SOAPConnector.
  java:352)
  at
  teamworks.connector.SOAPConnector.execute(SOAPConnector.java:238
  )
  at
  com.lombardisoftware.component.wsconnector.worker.WSConnectorWor
  ker.doJob(WSConnectorWorker.java:110)
  at
  com.lombardisoftware.component.common.workflow.ExecutionJob.doJo
  b(ExecutionJob.java:403)
  ... 34 more
  
  [7/27/12 12:24:06:912 BRT] 00000070 wle E CWLLG1338E: An error
  occurred
  while running a service. ExecutionContext:
  ExecutionStack(ExecutionJob(worker(com.lombardisoftware.componen
  t.wsconnector.worker.WSConnectorWorker@ba40ba4), processItemId
  =
  ProcessItem.9c9ac2f5-7953-4ae6-b225-896d75674726, processTiming
  = N, saveExecutionContextBehaviour =
  EXECUTION_CONTEXT_DO_NOT_SAVE)), SymbolTable(SymbolTable(...)),
  sharedData = null
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users utilizing web services and SOAP       *
  *                  connection to invoke external services.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: NullPointerException occurs when        *
  *                      portName value in WSDL is incorrect.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When changing the connection portName of the external service
  in your web services integration component and using a WSDL
  file which does not have the matching portName, a
  NullPointerException occurs.  When importing process
  applications across environments (ie. prod, QA, dev) the WSDL
  file may be reused but when configuring your web
  services component with the updated external port name, a
  mismatch occurs.
  The following exception may be seen:
  [1/7/13 15:26:07:128 CST] 000000df wle           E
  CWLLG0594E: An exception occurred while initializing the
  runnable thread. Error:
  com.lombardisoftware.component.common.workflow.WorkflowProcessIt
  emException: java.lang.NullPointerException
  com.lombardisoftware.component.common.workflow.WorkflowProcessIt
  emException: java.lang.NullPointerException
  at
  com.lombardisoftware.component.common.workflow.ExecutionJob.doJo
  b(ExecutionJob.java:415)
  at
  com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
  doResumeWorkflowEngine(EJBWorkflowManagerBean.java:1003)
  at
  com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
  resumeTask(EJBWorkflowManagerBean.java:295)
  at
  com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
  resumeTask(EJBWorkflowManagerBean.java:259)
  at
  com.lombardisoftware.server.ejb.workflow.EJSRemoteStatefulEJBWor
  kflowManager_82478d70.resumeTask(Unknown Source)
  

Problem conclusion

• Code changes have been made to handle the exception
  accordingly and output a more meaningful error message to
  properly communicate the issue to the user. The following
  error message can be seen with the code changes:
  
  [1/8/13 17:24:31:727 CST] 000000eb wle           E
  CWLLG0594E: An exception occurred while initializing the
  runnable thread. Error:
  com.lombardisoftware.component.common.workflow.WorkflowProcessIt
  emException: Message: teamworks.connector.port_name_not_found
  Arguments: OrderServiceHttpPort
  
  com.lombardisoftware.component.common.workflow.WorkflowProcessIt
  emException: Message: teamworks.connector.port_name_not_found
  Arguments: OrderServiceHttpPort
      at
  com.lombardisoftware.component.common.workflow.ExecutionJob.doJo
  b(ExecutionJob.java:415)
      at
  com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
  doResumeWorkflowEngine(EJBWorkflowManagerBean.java:1003)
      at
  com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
  resumeTask(EJBWorkflowManagerBean.java:295)
      at
  com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
  resumeTask(EJBWorkflowManagerBean.java:259)
      at
  com.lombardisoftware.server.ejb.workflow.EJSRemoteStatefulEJBWor
  kflowManager_82478d70.resumeTask(Unknown Source)
  
  The fix will be available in the next fix pack and an Interim
  Fix will be available on v7.5.1.0.
  
  Install/Dependency information is available in the readme.txt
  on FixCentral. When the user goes to the download files page
  in FixCentral, the readme will be available with the fix
  package as a separate download.
  

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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R750 PSY

     UP