KB-1990 Tomcat fails to start on Linux when heap is specified in custom.properties

Parmida Borhani — Tue, 10 Sep 2019 02:28:04 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 9/10/2019 2:28:04 AM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

There may be syntax issues with the following lines in custom.properties:
```
conf.appserver.minHeapSize= 
conf.appserver.maxHeapSize=
```
Windows line endings are being parsed by a Linux script. This occurs when the custom.properties file is edited in a Windows environment, and then moved onto a Linux server that will host Appian.

Action

Update custom.properties with the heap properties as needed, and with proper syntax. For example:
```
conf.appserver.minHeapSize=2048M 
conf.appserver.maxHeapSize=4096M
```
Run the command dos2unix custom.properties on the Linux server hosting Appian.
Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later on Linux.

Last Reviewed: September 2019

Tags: Tomcat, heap, linux, application server, infrastructure

KB-1990 Tomcat fails to start on Linux when heap is specified in custom.properties

Rebecca Jonas — Fri, 06 Sep 2019 21:35:20 GMT

Revision 15 posted to Appian Knowledge Base by Rebecca Jonas on 9/6/2019 9:35:20 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

There may be syntax issues with the following lines in custom.properties:
```
conf.appserver.minHeapSize= 
conf.appserver.maxHeapSize=
```
Windows line endings are being parsed by a Linux script. This occurs when the custom.properties file is edited in a Windows environment, and then moved onto a Linux server that will host Appian.

Action

Update custom.properties with the heap properties as needed, and with proper syntax. For example:
```
conf.appserver.minHeapSize=2048M 
conf.appserver.maxHeapSize=4096M
```
Run the command dos2unix custom.properties on the Linux server hosting Appian.
Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later on Linux.

Last Reviewed: September 2019

Tags: Tomcat, linux, application server, infrastructure

KB-1990 Tomcat fails to start on Linux when heap is specified in custom.properties

James Lee — Fri, 06 Sep 2019 21:34:00 GMT

Revision 14 posted to Appian Knowledge Base by James Lee on 9/6/2019 9:34:00 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

There may be syntax issues with the following lines in custom.properties:
```
conf.appserver.minHeapSize= 
conf.appserver.maxHeapSize=
```
Windows line endings are being parsed by a Linux script. This occurs when the custom.properties file is edited in a Windows environment, and then moved onto a Linux server that will host Appian.

Action

Update custom.properties with the heap properties as needed, and with proper syntax. For example:
```
conf.appserver.minHeapSize=2048M 
conf.appserver.maxHeapSize=4096M
```
Run the command dos2unix custom.properties on the Linux server hosting Appian.
Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later on Linux.

Last Reviewed: September 2019

Tags: Tomcat, linux, application server, infrastructure

KB-1990 Tomcat fails to start on Linux when heap is specified in custom.properties

Rebecca Jonas — Fri, 06 Sep 2019 21:14:31 GMT

Revision 13 posted to Appian Knowledge Base by Rebecca Jonas on 9/6/2019 9:14:31 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

There may be syntax issues with the following lines in custom.properties:
```
conf.appserver.minHeapSize= 
conf.appserver.maxHeapSize=
```
Windows line endings are being parsed by a Linux script. This occurs when the custom.properties file is edited in a Windows environment, and then moved onto a Linux server that will host Appian.

Action

Update custom.properties with the heap properties as needed, and with proper syntax. For example:
```
conf.appserver.minHeapSize=2048M 
conf.appserver.maxHeapSize=4096M
```
Run the command dos2unix custom.properties on the Linux server hosting Appian.
Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later on Linux.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start on Linux when heap is specified in custom.properties

James Lee — Wed, 04 Sep 2019 15:17:01 GMT

Revision 12 posted to Appian Knowledge Base by James Lee on 9/4/2019 3:17:01 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

There may be syntax issues with the following lines in custom.properties:
```
conf.appserver.minHeapSize= 
conf.appserver.maxHeapSize=
```
Windows line endings are being parsed by a Linux script. This occurs when the custom.properties file is edited in a Windows environment, and then moved onto a Linux server that will host Appian.

Action

Update custom.properties with the heap properties as needed, and with proper syntax. For example:
```
conf.appserver.minHeapSize=2048M 
conf.appserver.maxHeapSize=4096M
```
Run the command dos2unix custom.properties on the Linux server hosting Appian.
Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later on Linux.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start on Linux when heap is specified in custom.properties

James Lee — Wed, 04 Sep 2019 15:15:21 GMT

Revision 11 posted to Appian Knowledge Base by James Lee on 9/4/2019 3:15:21 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

There may be syntax issues with the following lines in custom.properties:
```
conf.appserver.minHeapSize= 
conf.appserver.maxHeapSize=
```
This issue occurs because Windows line endings are being parsed by a Linux script. This occurs when the custom.properties file is edited in a Windows environment, and then moved onto a Linux server that will host Appian.

Action

Update custom.properties with the heap properties as needed, and with proper syntax. For example:
```
conf.appserver.minHeapSize=2048M 
conf.appserver.maxHeapSize=4096M
```
Run the command dos2unix custom.properties on the Linux server hosting Appian.
Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later on Linux.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start on Linux when heap is specified in custom.properties

James Lee — Wed, 04 Sep 2019 15:15:07 GMT

Revision 10 posted to Appian Knowledge Base by James Lee on 9/4/2019 3:15:07 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

There maybe syntax issues with the following lines in custom.properties:
```
conf.appserver.minHeapSize= 
conf.appserver.maxHeapSize=
```
This issue occurs because Windows line endings are being parsed by a Linux script. This occurs when the custom.properties file is edited in a Windows environment, and then moved onto a Linux server that will host Appian.

Action

Update custom.properties with the heap properties as needed, and with proper syntax. For example:
```
conf.appserver.minHeapSize=2048M 
conf.appserver.maxHeapSize=4096M
```
Run the command dos2unix custom.properties on the Linux server hosting Appian.
Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later on Linux.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start on Linux when heap is specified in custom.properties

James Lee — Tue, 03 Sep 2019 16:04:53 GMT

Revision 9 posted to Appian Knowledge Base by James Lee on 9/3/2019 4:04:53 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

This issue occurs because Windows line endings are being parsed by a Linux script. This occurs when the custom.properties file is edited in a Windows environment, and then moved onto a Linux server that will host Appian.

Action

Update custom.properties with the heap properties as needed. For example:
```
conf.appserver.minHeapSize=2048M 
conf.appserver.maxHeapSize=4096M
```
Run the command dos2unix custom.properties on the Linux server hosting Appian.
Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later on Linux.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start on Linux when heap is specified in custom.properties

James Lee — Tue, 03 Sep 2019 15:57:13 GMT

Revision 8 posted to Appian Knowledge Base by James Lee on 9/3/2019 3:57:13 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

Action

Update custom.properties with the heap properties as needed. For example:
```
conf.appserver.minHeapSize=2048M 
conf.appserver.maxHeapSize=4096M
```
Run the command dos2unix custom.properties on the Linux server hosting Appian.
Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start on Linux when heap is specified in custom.properties

James Lee — Tue, 03 Sep 2019 15:51:51 GMT

Revision 7 posted to Appian Knowledge Base by James Lee on 9/3/2019 3:51:51 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

Action

1. Update custom.properties with the heap properties as needed. For example:

conf.appserver.minHeapSize=2048M
conf.appserver.maxHeapSize=4096M

2. Run the command dos2unix custom.properties on the Linux server hosting Appian.

3. Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start when heap is specified in custom.properties

James Lee — Tue, 03 Sep 2019 15:51:39 GMT

Revision 6 posted to Appian Knowledge Base by James Lee on 9/3/2019 3:51:39 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the tomcat-stdOut.log:

========================================================================= 
YYYY-MM-DD HH:MM:SS Beginning to start Appian in Tomcat Invalid initial heap size: -XmsXXXXm Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
YYYY-MM-DD HH:MM:SS Appian in Tomcat is stopped nohup: ignoring input

Cause

Action

1. Update custom.properties with the heap properties as needed. For example:

conf.appserver.minHeapSize=2048M
conf.appserver.maxHeapSize=4096M

2. Run the command dos2unix custom.properties on the Linux server hosting Appian.

3. Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start when heap is specified in custom.properties

James Lee — Tue, 03 Sep 2019 15:09:00 GMT

Revision 5 posted to Appian Knowledge Base by James Lee on 9/3/2019 3:09:00 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the Tomcat stdOut log:

========================================================================= 
2019-01-23 03:51:34 Beginning to start Appian in Tomcat Invalid initial heap size: -Xms2048m Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 
2019-01-23 03:51:34 Appian in Tomcat is stopped nohup: ignoring input

Cause

Action

1. Update custom.properties with the heap properties as needed. For example:

conf.appserver.minHeapSize=2048M
conf.appserver.maxHeapSize=4096M

2. Run the command dos2unix custom.properties on the Linux server hosting Appian.

3. Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start when heap is specified in custom.properties

James Lee — Tue, 03 Sep 2019 15:07:50 GMT

Revision 4 posted to Appian Knowledge Base by James Lee on 9/3/2019 3:07:50 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the Tomcat stdOut log:

========================================================================= 2019-01-23 03:51:34 Beginning to start Appian in Tomcat Invalid initial heap size: -Xms2048m Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 2019-01-23 03:51:34 Appian in Tomcat is stopped nohup: ignoring input

Cause

Action

1. Update custom.properties with the heap properties as needed. For example:

conf.appserver.minHeapSize=2048M
conf.appserver.maxHeapSize=4096M

2. Run the command dos2unix custom.properties on the Linux server hosting Appian.

3. Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start when heap is specified in custom.properties

James Lee — Tue, 03 Sep 2019 15:07:27 GMT

Revision 3 posted to Appian Knowledge Base by James Lee on 9/3/2019 3:07:27 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the Tomcat stdOut log:

========================================================================= 2019-01-23 03:51:34 Beginning to start Appian in Tomcat Invalid initial heap size: -Xms2048m Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. 2019-01-23 03:51:34 Appian in Tomcat is stopped nohup: ignoring input

Cause

Action

1. Update custom.properties with the heap properties as needed. For example:

conf.appserver.minHeapSize=2048M
conf.appserver.maxHeapSize=4096M

2. Run the command dos2unix custom.properties on the Linux server hosting Appian.

3. Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start when heap is specified in custom.properties

James Lee — Tue, 03 Sep 2019 15:02:39 GMT

Revision 2 posted to Appian Knowledge Base by James Lee on 9/3/2019 3:02:39 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the Tomcat stdOut log:

=========================================================================
2019-01-23 03:51:34 Beginning to start Appian in Tomcat
Invalid initial heap size: -Xms2048m
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
2019-01-23 03:51:34 Appian in Tomcat is stopped
nohup: ignoring input

Cause

Action

1. Update custom.properties with the heap properties as needed. For example:

conf.appserver.minHeapSize=2048M
conf.appserver.maxHeapSize=4096M

2. Run the command dos2unix custom.properties on the Linux server hosting Appian.

3. Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2019

DRAFT KB-XXXX Tomcat fails to start when heap is specified in custom.properties

James Lee — Tue, 03 Sep 2019 14:36:08 GMT

Revision 1 posted to Appian Knowledge Base by James Lee on 9/3/2019 2:36:08 PM

Symptoms

Tomcat fails to start when the app server heap parameters are defined in custom.properties. The following error is seen in the Tomcat stdOut log:

=========================================================================
2019-01-23 03:51:34 Beginning to start Appian in Tomcat
Invalid initial heap size: -Xms2048m
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
2019-01-23 03:51:34 Appian in Tomcat is stopped
nohup: ignoring input

Cause

Action

1. Update custom.properties with the heap properties as needed.

2. Run the command dos2unix custom.properties on the Linux server hosting Appian.

3. Restart the application server.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2019