After installation of the hotfix for the Apache Cassandra plugin, the application gets stopped.
book
Article ID: KB0079018
calendar_today
Updated On:
Products
Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for Apache Cassandra
6.3.x
Description
After installation of the hotfix for the Apache Cassandra plugin the below error message can be observed in appnode log,that can also be observed on bwadmin console: ============ com.tibco.bw.thor.runtime.model.Constituent - TIBCO-BW-FRWK-600000: com.tibco.bx.core.faults.BxException: BX-600037: Init module failed for module [com.mafretail.erceipts.provider.cassandra.module] version [1.0.0.20190320114256] application [com.mafretail.erceipts.provider.cassandra.module.application 1.0]. <CausedBy> com.tibco.bx.core.faults.BxException: BX-600037: Init module failed for module [com.mafretail.erceipts.provider.cassandra.module] version [1.0.0.20190320114256] application [com.mafretail.erceipts.provider.cassandra.module.application 1.0]. <CausedBy> com.tibco.bw.core.runtime.ActivityCreationException: TIBCO-BW-CORE-500612: Failed to create the activity [Update] in process [com.mafretail.erceipts.provider.cassandra.module.logic.CallCassandra], module [com.mafretail.erceipts.provider.cassandra.module] due to exception [com.tibco.neo.exception.BaseException]. <CausedBy> com.tibco.neo.exception.BaseException: WARNING: exception with message ***TIBCO-BW-FRWK-600001: No ComponentFactory found for activity type bw.cassandra.Update. The palette with this activity may not be installed.*** has not been localized ============
This issue occurred when bwagent is running then that time application config data locked by bwagent.When bwagent running if the user has installed a hotfix or upgrade plugin then config data is getting updated correctly.
Issue/Introduction
After installation of the hotfix for the Apache Cassandra plugin, the application gets stopped.
Environment
Product: TIBCO ActiveMatrix BusinessWorks Plug-in for Apache Cassandra
Version:6.3.x
OS: All Supported Operating Systems
Resolution
To resolve this issue make sure that bwagent, bwadmin or appnode process are in the stopped during installation/upgrading the plugin then follow the below steps:
1) Un-deploy all applications from the appspace. 2) Stop bwagent, bwadmin and appnode process. 3) Delete the 'configstorage' and 'org.eclipse.osgi' folder in the domains/<domain_name>/appnodes/<space_name>/<node_name>/config folder. 4) Start bwagent, appnode and bwadmin(for command line deployment) 5) Again deploy the applications