If you are upgrading to BPM 4.3.x from BPM 4.2.0 or a prior version and are not installing 3.4.0 HF 4 prior to the upgrade, please review the pre-checks listed in the resolution section. 
 

Here is the defect description from AMX Platform 3.4.0 HF 4 readme - 

==================

AMX-18090

Previously during the TIBCO ActiveMatrix 3.4.0 product upgrade, there were some

shared resource product features that were ignored and not upgraded to 3.4.0.

Due to this incomplete 3.4.0 platform upgrade there will be some BPM 4.3 upgrade

issue.

With this fix, all those previously ignored product features now get upgraded to

3.4.0, and both TIBCO ActiveMatrix 3.4.0 platform and BPM 4.3 can be upgraded

successfully.

==================

If 3.4.0 HF 4 is not installed, all the following symptoms are observed when upgrading BPM to confirm the cause is due to AMX-18090 - 

i. During BPM upgrade - TCT will timeout at the task - "Deploying AMX BPM Application on BPM Node" 

ii. After TCT times out, one or more BPM Nodes will be stuck at Starting state. The node logs will not have any entries. The last log entry in host logs is along the lines of - 

[JMXConnectingThread-BPMNode1] [DEBUG] com.tibco.amx.hpa.JMXConnection.BPMNode1 - initializing JMX client endpoint connection to JMXConfiguration{name="BPMNode1",protocol="jmxmp",host="localhost",port="6031",address="service:jmx:jmxmp://localhost:6031"}, SSL is disabled

iii. node-stdout.log will have a number of error's along the lines of - 

org.osgi.framework.BundleException: The bundle "com.tibco.bx.n2.de_1.15.4.001 [824]" could not be resolved. Reason: Missing Constraint: Import-Package: com.tibco.bx.api; version="[1.13.100,2.0.0)"

If you have already observed the above symptoms and confirmed the cause is AMX-18090, then please revert back to a pre-upgrade backup. Please install 3.4.0 HF 4 on all servers prior to the AMX upgrade step. 

./tibcohost describeInstalledProductFeatures | egrep "com.tibco.amf.sharedresource|com.tibco.amx.platform.product.feature"

There should only be 1 version of the listed features installed. For example - an output of the host where the issue will not occur  - 

com.tibco.amf.sharedresource.core.runtime.tibcohost.product.feature 3.3.7.000

com.tibco.amf.sharedresource.extensions.runtime.tibcohost.product.feature 3.3.7.000

com.tibco.amf.sharedresource.orm.runtime.tibcohost.product.feature 3.3.7.000

com.tibco.amf.sharedresource.trinity.runtime.tibcohost.product.feature 3.3.7.000

com.tibco.amx.platform.product.feature 1.3.7.000

Following example is from a host where this issue will occur - 

-- Here the same features are listed for v3.3.7 and v3.3.17 (the versions may vary based on the environment)

com.tibco.amf.sharedresource.core.runtime.tibcohost.product.feature 3.3.7.000

com.tibco.amf.sharedresource.core.runtime.tibcohost.product.feature 3.3.17.000

com.tibco.amf.sharedresource.extensions.runtime.tibcohost.product.feature 3.3.7.000

com.tibco.amf.sharedresource.extensions.runtime.tibcohost.product.feature 3.3.17.000

com.tibco.amf.sharedresource.orm.runtime.tibcohost.product.feature 3.3.7.000

com.tibco.amf.sharedresource.orm.runtime.tibcohost.product.feature 3.3.17.000

com.tibco.amf.sharedresource.trinity.runtime.tibcohost.product.feature 3.3.7.000

com.tibco.amf.sharedresource.trinity.runtime.tibcohost.product.feature 3.3.17.000

com.tibco.amx.platform.product.feature 1.3.7.000