Troubleshoot my RET Adapter

If you have trouble running an adapter, you can use the Liberator status page (http://<liberator-host>:<http-port>/status) to determine whether the adapter is up or down.

Log files

Logs help to troubleshoot an Adapter blade. More information can be found in 'Troubleshoot an Adapter blade'.

The logs for the Liberator can be found on <Liberator:

<Liberator> in servers/Liberator/var

The logs for the Transformer can be found on <Transformer>:

<Transformer> in servers/Transformer/var

The logs for the RET Adapters can be found on <Adapters>:

<Adapter_name> in /active_blades/<adapter name>/DataSource/var

Log Name Usage
all-<Adapter Name>.log  Contains all customised code, event and trapi logs.
<Adapter Name>.log Contains logs for the underlying Caplin DataSource.
event-<Adapter Name>.log Contains logs for the Adapter only.
trapi-<Adapter Name>.log Contains logs for the retIntegrationAPI layer that integrates with RET only.
packet-<Adapter Name>.log

Contains packet data logs for the underlying DataSource.

jmx-<Adapter Name>.log Contains adapters JMX logs.
blotter-<Adapter Name>.log Contains adapters blotter API specific logs.

RET API specific log. Switched off by default.


Enabled ret logs in global-config/overrides/<Adapter_name>/etc/

  • ret_log_enabled=true
  • Run ./dfw start

Note: ret.log file is needed by RET support to investigate issues with their RET-AD system. 

AdminAPI.log RET Admin API specific log. 
 Note: To view the packet-*.log logs, first they will need to be processed by the logcat tool found in servers/Liberator/bin/logcat

Configure logs with log4j

The log level default is set to INFO for all adapters in the RET Adapter Suite. One exception is the PricingAdapter, which is set to DEBUG level, as the logs would grow to fast for price updates.

If you want to change the log configuration of your Adapters follow these steps: 

  • Copy the log4j.xml file from activate_blades/<Adapter>/Blade/Datasource/etc/log4j.xml into global_config/overrides/<Adapter>/etc
  • Change the log level of the log4j.xml in global_config/overrides/<Adapter>/etc
  • Restart the adapter ./dfw start <Adapter>
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN">
     <!-- This logs all log messages -->
    <RollingFile name="all" fileName="var/all-<Adapters>.log" filePattern="var/all-<Adapters>-%i.log.gz">
      <PatternLayout pattern="%d{yyyy MMM dd HH:mm:ss.SSS Z}  -  [%t] %-5p %c - %m%n"/>
       <Policies><SizeBasedTriggeringPolicy size="50 MB"/></Policies>
      <DefaultRolloverStrategy max="50"/>
    <!-- This logs only trapi-layer logs -->
    <RollingFile name="trapi" fileName="var/trapi-<Adapters>.log" filePattern="var/trapi-<Adapters>-%i.log.gz">
      <PatternLayout pattern="%d{yyyy MMM dd HH:mm:ss.SSS Z}  -  [%t] %-5p %c - %m%n"/>
       <Policies><SizeBasedTriggeringPolicy size="50 MB"/></Policies>
      <DefaultRolloverStrategy max="50"/>
    <!-- This logs only adapter logs -->
    <RollingFile name="event" fileName="var/event-<Adapters>.log" filePattern="var/event-<Adapters>.log-%i.log.gz">
      <PatternLayout pattern="%d{yyyy MMM dd HH:mm:ss.SSS Z}  -  [%t] %-5p %c - %m%n"/>
       <Policies><SizeBasedTriggeringPolicy size="50 MB"/></Policies>
      <DefaultRolloverStrategy max="50"/>
   <!--This logs only jmx logs -->
   <RollingFile name="jmx" fileName="var/jmx-<Adapters>.log" filePattern="var/jmx-<Adapters>-%i.log.gz">
    <PatternLayout pattern="%d{yyyy MMM dd HH:mm:ss.SSS Z}  -  [%t] %-5p %c - %m%n"/>
      <Policies><SizeBasedTriggeringPolicy size="500 MB"/></Policies>
  <DefaultRolloverStrategy max="50"/>

    <Root level="info">
      <AppenderRef ref="all"/>
    <Logger name="com.caplin.motif" level="info">
      <AppenderRef ref="event"/>
    <Logger name="com.caplin.ret.trapi" level="info">
      <AppenderRef ref="trapi"/>
    <Logger name="com.caplin.ret.trapi.connection.pool" level="info" additivity="false">
      <AppenderRef ref="jmx"/>