Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


Explain how to perform debugging when something doesn't work in Cargo. Indeed it can happen that the container does not start or stop as expected. Or that some deployable does not deploy fine. Or whatever else! Here is a short list of things you can do to try debugging the problem.

Redirecting container output to a file

The container.setOutput(File) API allows you redirect the container console (stdout) to a file. This is the first file you should check in case of problem.

Example: Starting Tomcat 4.x specifying an output console log file

Use the container.setAppend(true|false) method to decide whether the log file is recreated or whether it is appended to, keeping the previous execution logs.

Generating Cargo logs

Some Cargo classes support generation of logs. This is implemented through the notion of Monitor.

For example to turn on logging monitoring on a Container class, you can use:

There are several Monitors that are readily available in the Cargo distribution:

Turning on container logs

Cargo is able to configure containers to generate various levels logs. There are 3 levels defined: "low", "medium" and "high". They represent the quantity of information you wish in the generated log file. You can turn on container logging by using the following API:

The generated log files will then be found in the Working directory you have specified on the container (through the container.setWorkingDir() call).

When using the Ant tasks, you can specify the log file by using the log attribute. For example:

  • No labels