After applying AMX BPM 4.2.0 HF 2 or or 4.1.0 HF 8 or 4.0.0 HF 4, process instance creation fails with the below message and stack trace -
Error creating a process instance . . com.tibco.pvm.api.exceptions.PmModelException: PVM-MODEL-102104: Get Value 'com.tibco.pvm.infra.support.compiled.impl.IpmCmpDefAttrImpl@235bec8b' failed. . . Caused by: java.lang.NullPointerException at com.tibco.pvm.db.common.bridge.model.impl.IdbCompiledObjectBridgeImpl._getAttrValue(IdbCompiledObjectBridgeImpl.java:97) at com.tibco.pvm.db.common.bridge.model.impl.IdbCompiledObjectBridgeImpl.getAttrValue(IdbCompiledObjectBridgeImpl.java:69) at com.tibco.pvm.infra.support.compiled.impl.IpmCmpDefAttrImpl.getValue(IpmCmpDefAttrImpl.java:95) ... 30 more
The following defect has been fixed in AMX BPM 4.2.0 HF 2, 4.1.0 HF 8 and 4.0.0 HF 4 -
WRM-9244 (CN-01251784, CN-01249908) ----------------------------------- After upgrading from a pre-4.0 version of ActiveMatrix BPM, no process definitions were visible when trying to create a new Process View in Workspace.
This fix adds an internal attribute to each process stored in the BPM database to indicate whether it is a service process or not. When persisting this attribute in the database, the data serializer is always chosen as 14. In few environments, it has been found that the serializer id can be a different value.
Run the below query to detect this issue -
select ID from PVM_DATA_SERIALIZER where CLASS_NAME='com.tibco.pvm.db.common.serializers.java.IdbDsjBooleanSerializer';
If this returns 14, then you will NOT run into this issue.
If this returns any other number, then please contact TIBCO Support.
Issue/Introduction
This article describes an issue that can occur after applying TIBCO ActiveMatrix (AMX) BPM hotixes (HF) 4.2.0 HF 2 or 4.1.0 HF 8 or 4.0.0 HF 4