KB-1165 "An error occurred while trying to initialize the config object com.appiancorp.process.common.util.EmailAddressConfig" thrown while starting WebLogic with Appian 16.2
| This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. |
Symptoms
When starting WebLogic application server with Appian 16.2, the deployment fails and the following error can be seen in the logs:
<Notice> <Stdout> <BEA-000000> <2016-05-17 13:25:43,854 [[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config object com.appiancorp.process.common.util.EmailAddressConfig using the following resources: /WEB-INF/conf/process/email-address-config.xml
org.springframework.beans.factory.UnsatisfiedDependencyException:
Error creating bean with name 'smartServiceBridgeRegistry' defined in class com.appiancorp.core.expr.reaction.smartservicebridge.SmartServiceBridgeSpringConfig: Unsatisfied dependency expressed through constructor argument with index 1 of type [com.appiancorp.core.expr.reaction.ReactionFunctionProvider]:
: Error creating bean with name 'reactionFunctionProvider' defined in class com.appiancorp.core.expr.reaction.ReactionSpringConfig: Unsatisfied dependency expressed through constructor argument with index 0 of type [java.util.List]:
: Error creating bean with name 'setAdministeredConfigurationPropertiesReaction' defined in class com.appiancorp.suite.cfg.adminconsole.AdminConsoleSpringConfig: Unsatisfied dependency expressed through constructor argument with index 0 of type [com.appiancorp.suite.cfg.adminconsole.ConfigurationMappingService]:
: Error creating bean with name 'configurationMappingService' defined in class com.appiancorp.suite.cfg.adminconsole.AdminConsoleSpringConfig: Unsatisfied dependency expressed through constructor argument with index 1 of type [com.appiancorp.suite.cfg.adminconsole.AdminConsoleConfigObject]:
: Error creating bean with name 'adminConsoleConfigObject' defined in class com.appiancorp.suite.cfg.adminconsole.AdminConsoleSpringConfig: Bean instantiation via factory method failed;
...
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSourceTransactionManager' defined in class com.appiancorp.rdbms.datasource.DataSourceFactorySpringConfig: Bean instantiation via factory method failed;
nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.transaction.TransactionManager]: Factory method 'dataSourceTransactionManager' threw exception; nested exception is java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
...
Caused by: java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
Cause
This issue has been addressed via AN-70210 in the following hotfixes/versions:
- Appian 16.2 Hotfix Package B
- Appian 16.3
Action
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.
Action
To work around this issue, follow the steps below:
- Stop the application server.
- In
<APPIAN_HOME>/ear/suite.ear/lib, add the .bak extension to jboss-logging-spi-2.2.0.CR1.jar - Start the application server
Affected Versions
This article applies to Appian 16.2.
Last Reviewed: February 2017
