Direct links to fixes
APAR status
Closed as program error.
Error description
The data binding namespace could be incorrect when it is generated in IBM Business Process Manager (BPM) V8.0.1.3 and later versions. If so, you might experience runtime environment errors similar to the following errors: com.ibm.websphere.sca.ServiceRuntimeException: DataBinding Exception thrown in J2CMethodBindingImpl.invoke() commonj.connector.runtime.DataBindingException: Failed in population return object In the ffdc logs, the following exception can be found: Caused by: com.ibm.despi.exception.DESPIException: The metadata object is null! at com.ibm.j2ca.base.WBIStructuredRecord.validateMetadata(WBIStruct uredRecord.java:472) at com.ibm.j2ca.base.WBIStructuredRecord.initializeOutput(WBIStruct uredRecord.java:485) at com.ibm.j2ca.dbadapter.core.emd.databinding.DBDataBinding.getDat aObject(DBDataBinding.java:108)
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM BPM Advanced * **************************************************************** * PROBLEM DESCRIPTION: The data binding namespace could be * * incorrect when it is generated in IBM * * Business Process Manager (BPM) * * V8.0.1.3 and later versions. If so, * * you might experience runtime * * environment errors similar to the * * following errors: * * com.ibm.websphere.sca.ServiceRuntimeExc * * eption: DataBinding Exception thrown * * in J2CMethodBindingImpl.invoke() * * commonj.connector.runtime.DataBindingEx * * ception: Failed in population return * * object * * In the ffdc logs, the following * * exception can be found: * * Caused by: * * com.ibm.despi.exception.DESPIException: * * The metadata object is null! * * at * * com.ibm.j2ca.base.WBIStructuredRecord.v * * alidateMetadata(WBIStructuredRecord.jav * * a:472) * * at * * com.ibm.j2ca.base.WBIStructuredRecord.i * * nitializeOutput(WBIStructuredRecord.jav * * a:485) * * at * * com.ibm.j2ca.dbadapter.core.emd.databin * * ding.DBDataBinding.getDataObject(DBData * * Binding.java:108). * **************************************************************** * RECOMMENDATION: * **************************************************************** The generator of the data binding might miss the .xsd files, which are necessary to generate the data binding namespace in some directories.
Problem conclusion
A fix is available for IBM BPM V8.0.1.3 that ensures the data binding generator can access the .xsd files in all required directories. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR53208: 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 Con-tinue. 2. Select APAR or SPR, enter JR53208, 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.
Temporary fix
Comments
APAR Information
APAR number
JR53208
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-04-24
Closed date
2016-01-04
Last modified date
2016-01-04
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 October 2021