Documentation / Community Edition / User Guide / Appendix / Troubleshooting

This section describes some hints to solve common problems which may occur during deployment of the MyARM agent.

Tracing initialisation and configuration

It is possible to enable a tracing mechanism which helps you to identify the deployment problem you might have. This can be enables using the MYARM_TRACE environment variable. For detailed description of the options you can enable (See Appendix Environment) .

MyARM manager does not work with SQLite database

SQLite database is a file based SQL database engine which sometimes has problems of concurrent access especially under Windows. If you encounter the problem that the MyARM manager seems to working have a look into the log files. There might be error messages about locking problems. Make sure that no instrumented application is running while you want to analyse measurement data.

Some transactions are missing

MyARM limits its resource usage (memory) to work properly even if the instrumented application uses the ARM API in a wrong way. Therefore it is possible that some transaction measurements are missing due to resource shortage. If more transaction response time measurements are active at a time than the configured transaction instances some response time measurements are dropped. This situation is logged with log message to notify about the lost data.

The ARM data buffer pool size (basic.armdata.buffer.pool.size) and the size of each ARM data buffer (basic.armdata.buffer.size) can be configured (See ARM data buffer configuration ).