SSL handshake timeout

Add the following line to the <chariot_install_dir>/conf/com.cirruslink.chariot.server configuration file.

Default is 20000 ms (20 secs)

The example below sets the timeout to 30000 ms (30 sec)

sslHandshakeTimeout=I"30000"

Maximum outbound queue size

The Chariot maximum outbound queue size can be configured in the <chariot_install_dir>/conf/com.cirruslink.chariot.server configuration file.

Default is 16384 messages

The example below sets the maximum outbound queue size to 20000

maxOutboundQueueSize = I"20000"

Max heap size

The Chariot max heap size is not configured and in prior to V2.2.3 defaulted to 1GB. In V2.2.3 onward the max heap size defaults to 2GB.

The Chariot max heap size can be configured on all version of Chariot in the <chariot_install_dir>/yajsw/conf/wrapper.conf file.

# Example 4GB Max Heap 2
wrapper.java.additional.6 = -Xmx4g

Note: a Chariot service restart is required for Chariot to pickup the configuration change.


Log files

The Chariot wrapper.log text files can be managed on all version of Chariot in the <chariot_install_dir>/yajsw/conf/wrapper.conf file.

wrapper.logfile.loglevel=INFO
 
wrapper.logfile=${wrapper_home}/../log/wrapper.log
 
wrapper.logfile.format=LPDTM
 
wrapper.logfile.maxsize=10m
 
wrapper.logfile.maxfiles=10
 
wrapper.logfile.rollmode=SIZE
 
wrapper.logfile.maxdays=60
 
wrapper.logfile.desc=true

Based on this, up to 10 files of 10MB is size each may be retained. However, this isn’t exact and if logging is very verbose these can surpass that size limit and end up being larger.

Note: a Chariot service restart is required for Chariot to pickup the configuration change.


The DB logfile can be managed in the com.cirruslink.chariot.persistence.h2-logging configuration file. In this is a config option:

tables.1.maxRows=I"262144"

When maxRows is set, there will actually be two tables of that size created. When one fills up it will truncate the other one, to clear all the data, and then switch to using it rotating between the two tables.

Note: a Chariot service restart is required for Chariot to pickup the configuration change.

  • No labels