KB-1632 Appian 18.2 fails to deploy on Weblogic with "appianHome cannot be null" error

Jordan Horwat — Fri, 22 Mar 2019 15:56:57 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 3/22/2019 3:56:57 PM

Symptoms

Installing Appian 18.2 with Weblogic 12.2.1.3 results in an error of the following type:

<User defined listener com.appiancorp.rdbms.datasource.BusinessDataSourceValidator failed: java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration.
java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
.
.
.
<Info> <ServletContext-/suite> <BEA-000000> <Closing Spring root WebApplicationContext> 
<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.config.PrimaryDataSourceShutdown failed: java.lang.IllegalArgumentException: appianHome cannot be null.
java.lang.IllegalArgumentException: appianHome cannot be null.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109591.
This issue may also occur if the suite.ear has been customized and the location of the file has been modified in the process. This affects the absolute paths set within the suite.ear directory leading to the observed issue.

Action

Instead of deploying Appian to a Managed Server in Weblogic, deploy Appian to the default AdminServer.
Ensure that the customization does not modify the location of suite.ear.

Affected Versions

This article applies to Appian 18.2.

Last Reviewed: March 2019

Tags: weblogic, known issues, application server, infrastructure, open issues

KB-1632 Appian 18.2 fails to deploy on Weblogic with "appianHome cannot be null" error

Parmida Borhani — Fri, 03 Aug 2018 01:34:05 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 8/3/2018 1:34:05 AM

Symptoms

Installing Appian 18.2 with Weblogic 12.2.1.3 results in an error of the following type:

<User defined listener com.appiancorp.rdbms.datasource.BusinessDataSourceValidator failed: java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration.
java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
.
.
.
<Info> <ServletContext-/suite> <BEA-000000> <Closing Spring root WebApplicationContext> 
<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.config.PrimaryDataSourceShutdown failed: java.lang.IllegalArgumentException: appianHome cannot be null.
java.lang.IllegalArgumentException: appianHome cannot be null.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109591.

Action

Instead of deploying Appian to a Managed Server in Weblogic, deploy Appian to the default AdminServer.

Affected Versions

This article applies to Appian 18.2.

Last Reviewed: August 2018

Tags: weblogic, known issues, application server, infrastructure, open issues

DRAFT KB-XXXX Appian 18.2 fails to deploy on Weblogic with "appianHome cannot be null" error

Tejas Kargutkar — Thu, 02 Aug 2018 10:48:17 GMT

Revision 7 posted to Appian Knowledge Base by Tejas Kargutkar on 8/2/2018 10:48:17 AM

Symptoms

Installing Appian 18.2 with Weblogic 12.2.1.3 results in an error of the following type:

<User defined listener com.appiancorp.rdbms.datasource.BusinessDataSourceValidator failed: java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration.
java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
.
.
.
<Info> <ServletContext-/suite> <BEA-000000> <Closing Spring root WebApplicationContext> 
<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.config.PrimaryDataSourceShutdown failed: java.lang.IllegalArgumentException: appianHome cannot be null.
java.lang.IllegalArgumentException: appianHome cannot be null.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109591.

Action

Instead of deploying Appian to a Managed Server in Weblogic, deploy Appian to the default AdminServer.

Affected Versions

This article applies to Appian 18.2.

Last Reviewed: August 2018

Tags: weblogic, known issues, application server, infrastructure, open issues

DRAFT KB-XXXX Appian 18.2 fails to deploy on Weblogic with "appianHome cannot be null" error

Tejas Kargutkar — Thu, 02 Aug 2018 10:45:02 GMT

Revision 6 posted to Appian Knowledge Base by Tejas Kargutkar on 8/2/2018 10:45:02 AM

Symptoms

Installing Appian 18.2 with Weblogic 12.2.1.3 results in an error of the following type:

<User defined listener com.appiancorp.rdbms.datasource.BusinessDataSourceValidator failed: java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration.
java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
.
.
.
<Info> <ServletContext-/suite> <BEA-000000> <Closing Spring root WebApplicationContext> 
<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.config.PrimaryDataSourceShutdown failed: java.lang.IllegalArgumentException: appianHome cannot be null.
java.lang.IllegalArgumentException: appianHome cannot be null.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109591.

Action

Instead of deploying Appian to a Managed Server in Weblogic, deploy Appian to the default Adminserver.

Affected Versions

This article applies to Appian 18.2.

Last Reviewed: August 2018

Tags: weblogic, known issues, application server, infrastructure, open issues

DRAFT KB-XXXX Appian 18.2 fails to deploy on Weblogic with "appianHome cannot be null" error

Tejas Kargutkar — Wed, 01 Aug 2018 21:21:10 GMT

Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 8/1/2018 9:21:10 PM

Symptoms

Installing Appian 18.2 with Weblogic 12.2.1.3 results in an error of the following type:

<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.datasource.BusinessDataSourceValidator failed: java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration. java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) .

<Jul 11, 2018 1:40:07,424 PM GMT> <Info> <ServletContext-/suite> <BEA-000000> <Closing Spring root WebApplicationContext> <Jul 11, 2018 1:40:07,450 PM GMT> <Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.config.PrimaryDataSourceShutdown failed: java.lang.IllegalArgumentException: appianHome cannot be null.. java.lang.IllegalArgumentException: appianHome cannot be null.

DRAFT KB-XXXX Appian 18.2 fails to deploy on Weblogic with "appianHome cannot be null" error

Parmida Borhani — Wed, 01 Aug 2018 20:35:33 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 8/1/2018 8:35:33 PM

Symptoms

Installing Appian 18.2 with Weblogic 12.2.1.3 results in an error of the following type:

<User defined listener com.appiancorp.rdbms.datasource.BusinessDataSourceValidator failed: java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration.
java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
.
.
.
<Info> <ServletContext-/suite> <BEA-000000> <Closing Spring root WebApplicationContext> 
<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.config.PrimaryDataSourceShutdown failed: java.lang.IllegalArgumentException: appianHome cannot be null.
java.lang.IllegalArgumentException: appianHome cannot be null.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109591.

Workaround

Instead of deploying Appian to a Managed Server in Weblogic, deploy Appian to the default Adminserver.

Affected Versions

This article applies to Appian 18.2.

Last Reviewed: August 2018

Tags: weblogic, known issues, application server, infrastructure

DRAFT KB-XXXX Appian 18.2 fails to deploy on Weblogic with "appianHome cannot be null" error

Parmida Borhani — Wed, 01 Aug 2018 20:35:03 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 8/1/2018 8:35:03 PM

Symptoms

Installing Appian 18.2 with Weblogic 12.2.1.3 results in an error of the following type:

<User defined listener com.appiancorp.rdbms.datasource.BusinessDataSourceValidator failed: java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration.
java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
.
.
.
<Info> <ServletContext-/suite> <BEA-000000> <Closing Spring root WebApplicationContext> 
<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.config.PrimaryDataSourceShutdown failed: java.lang.IllegalArgumentException: appianHome cannot be null..
java.lang.IllegalArgumentException: appianHome cannot be null.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109591.

Workaround

Instead of deploying Appian to a Managed Server in Weblogic, deploy Appian to the default Adminserver.

Affected Versions

This article applies to Appian 18.2

Last Reviewed: August 2018

Tags: weblogic, known issues, application server, infrastructure

DRAFT KB-XXXX Appian 18.2 fails to deploy on Weblogic with "appianHome cannot be null" error

Tejas Kargutkar — Wed, 01 Aug 2018 17:27:02 GMT

Revision 3 posted to Appian Knowledge Base by Tejas Kargutkar on 8/1/2018 5:27:02 PM

Symptoms

Installing Appian 18.2 with Weblogic 12.2.1.3 results in an error of the following type:

<User defined listener com.appiancorp.rdbms.datasource.BusinessDataSourceValidator failed: java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration.
java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
.
.
.
<Info> <ServletContext-/suite> <BEA-000000> <Closing Spring root WebApplicationContext> 
<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.config.PrimaryDataSourceShutdown failed: java.lang.IllegalArgumentException: appianHome cannot be null..
java.lang.IllegalArgumentException: appianHome cannot be null.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109591.

Workaround

Instead of deploying Appian to a Managed Server in Weblogic, deploy Appian to the default Adminserver.

Affected Versions

This article applies to Appian 18.2

Last Reviewed: August 2018

Tags: weblogic, known issues, application server, infrastructure

DRAFT KB-XXXX Appian 18.2 fails to deploy on Weblogic with "appianHome cannot be null" error

Tejas Kargutkar — Wed, 01 Aug 2018 17:25:16 GMT

Revision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 8/1/2018 5:25:16 PM

Symptoms

Installing Appian 18.2 with Weblogic 12.2.1.3 results in an error of the following type:

<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.datasource.BusinessDataSourceValidator failed: java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration. java.lang.NoClassDefFoundError: Could not initialize class com.appiancorp.suite.SuiteConfiguration at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 
.
.
.
<Info> <ServletContext-/suite> <BEA-000000> <Closing Spring root WebApplicationContext> 
<Warning> <HTTP> <BEA-101162> <User defined listener com.appiancorp.rdbms.config.PrimaryDataSourceShutdown failed: java.lang.IllegalArgumentException: 
appianHome cannot be null.. java.lang.IllegalArgumentException: 
appianHome cannot be null.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109591.

Workaround

Instead of deploying Appian to a Managed Server in Weblogic, deploy Appian to the default Adminserver.

Affected Versions

This article applies to Appian 18.2

Last Reviewed: August 2018

Tags: weblogic, known issues, application server, infrastructure