JR43943: TeamWorksException invoking BPM decision service on WODM app

Version 8.0 Refresh Pack 1 for the IBM Business Process Manager products
Version 7.5.1 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• Problem Description : Invoking BPM decision service connected
  to an application deployed on a WebSphere Operational Decision
  Manager server causes a
  com.lombardisoftware.core.TeamWorksException
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Applications utilizing JAX-WS web services  *
  *                  to communicate with external services.      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When submitting a request the           *
  *                      exception                               *
  *                      com.lombardisoftware.core.TeamWorksExce *
  *                      ption is seen in the logs.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When mapping variables to the input variables of the outgoing
  web services object, it is possible to have an empty value for
  those variables.  The property mapped to the object is
  expected to have a value but does not find one
  as it is set to null by default. During serialization when the
  property is serialized an exception is thrown to indicate
  there is an empty value for one of the properties.
  An exception similar to this will be seen in the logs:
  Caused by: com.lombardisoftware.core.TeamWorksException
  at
  com.ibm.bpm.ws.jaxws.serialize.SerializationDocDelegateImpl.mars
  hal(SerializationDocDelegateImpl.java:184)
  at
  com.ibm.bpm.ws.jaxws.serialize.DocLiteralMessage.marshalRequest(
  DocLiteralMessage.java:319)
  at
  com.ibm.bpm.ws.jaxws.connector.SOAPConnector.processDocLiteralOp
  eration(SOAPConnector.java:280)
  

Problem conclusion

• A workaround for this issue is to assign a value to the mapped
  variable, even if it's a blank "". Code has been integrated to
  handle the exception accordingly and not interupt the process.
  By JAX-WS specification a value is expected for each property.
  Hence, even though the exception is no longer seen the
  properties with null values will be excluded from the request.
  To ensure each mapped property of the input variable is sent
  with the request a value must be set.
  The fix will be included in the next fix pack. It has been
  targeted for inclusion in v8.0.1.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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R800 PSY

     UP