Direct links to fixes
APAR status
Closed as program error.
Error description
After you migrate from IBM Business Process Manager (BPM) V7.5.x or earlier releases to IBM BPM V8.0.1.x and later releases, you might see the following exceptions: com.lombardisoftware.core.TeamWorksException:Type mismatch. Value TWObject[(Active: Y), (Type: 1), (TWClassID:TWClass.<ID>), (Property names: <Name>, <NameDescription>), (MetaData:objectID=<ID>, dirty=true,invalid=false, shared=false, key=null, version=null,rootVersionContextID=<ID>,className=<TWObject_Name> )] must be of type <TWObject_Name>' java.lang.NumberFormatException for input string: ""
Local fix
Problem summary
The Teamworks exception occurs because there are business object definitions with same namespace and name. During an upgrade, the web service integration updated its engine and algorithms. As a result, that different business object, instead of the one you assigned in output mapping, is selected and the error occurs. The number format exception occurs because the new engine in IBM BPM V8.0.1 and later releases follows the web service specifications. If the web service returns an empty number field, you receive the exception because there is nothing to convert into a valid number value. In the old engine, an empty number field was considered unset. PRODUCTS AFFECTED IBM Business Process Manager (BPM) Advanced IBM BPM Standard IBM BPM Express
Problem conclusion
A fix is available for IBM BPM V8.5.7 cumulative fix 2016.06 that adds the backward-compatible functions on web service integration. If you don't already have IBM BPM V8.5.7.0 cumulative fix 2016.06 installed, go to http://www.ibm.com/support/docview.wss?uid=swg24042266. After IBM BPM V8.5.7.0 cumulative fix 2016.06 is installed, search for JR56629 on Fix Central (http://www.ibm.com/support/fixcentral: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. 2. Select APAR or SPR, enter JR56629, and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix. This interim fix introduces the following configuration properties: allow-empty-response-for-numeric-format - Use this configuration property to control the behavior on parsing numeric responses. and use-advanced-response-type-mapping - Use this configuration property to control how the TWObject type response is found. You can set these configuration properties in the 100Custom.xml, for example <common merge="mergeChildren"> <webservices merge="mergeChildren"> <allow-empty-response-for-numeric-format merge="replace">true</allow-empty-response-for-numeric-format> <use-advanced-response-type-mapping merge="replace">true</use-advanced-response-type-mapping> </webservices> </common>
Temporary fix
Comments
APAR Information
APAR number
JR56629
Reported component name
BPM STANDARD
Reported component ID
5725C9500
Reported release
857
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-08
Closed date
2016-10-13
Last modified date
2016-10-17
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 STANDARD
Fixed component ID
5725C9500
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
15 October 2021