How to Set Application Initialization Options
Last updated
Was this helpful?
Note: This feature is available in Capstorm application versions 10.56.6 and above.
Capstorm applications allows you to add supplementary Java options. These options serve to dynamically alter the operational parameters of the application prior to its initiation. One frequent utilization, which serves as an example throughout this article, is the facilitation of user-driven control over memory allocation for any of Capstorm’s applications. This capability gives users the control to finely calibrate the memory resources dedicated to the operation of Capstorm’s applications.
Note: Application must be restarted for these configuration files to be applied.
First create a XML file named “AppLoader.xml”
Two recommended placement options:
Option 1: If you followed CopyStorm’s Best Practice Directory Structure then we recommend placing this configuration file in CapstormConfig directory.
Option 2: Inside of one of Capstorm’s application installation directory there should be a directory called “config”. You can also place this configuration file in the “config” directory.
Note: For versions older than 10.56.6 please visit: out-of-memory-java-heap-space-error on how to configure memory settings.
Once you have completed “Configuration File Creation and Placement” steps you can simply copy the snippet below into the AppLoader.xml configuration file.
The example below shows how to set the min and max memory allocations to 300 and 1000 megabytes, respectively.
The AppLoader also allows for custom Java Properties. Below is an example of setting the HTTPS Protocols to TLSv1.1 and TLSv1.2.
Last updated
Was this helpful?
Was this helpful?
<AppLoader>
<JavaArgument arg="-Xms300m" />
<JavaArgument arg="-Xmx1000m" />
</AppLoader><AppLoader>
<SystemProperty name="https.protocols" value="TLSv1.1,TLSv1.2" />
</AppLoader>