# Running eXo Platform in Debug and Dev modes
Dev and Debug modes are turned off by default and are not recommended in production because of performance impact. They should be turned on only for debugging in development environment.
If you are debugging against eXo Platform Tomcat, use the following start command:
./start_eXo.sh --dev --debug
This section will introduce more details about Debug Mode and Dev Mode and their effects.
# Debug mode
The Debug mode in eXo Platform is generally like other Java applications using JDWP (opens new window) that enables debugging by IDE.
In eXo Platform Tomcat, the Debug mode is turned on by appending
--debug to the startup command:
This parameter adds the following JVM option:
# Dev mode
In eXo Platform, the Dev mode is turned on by appending
--dev to the startup command:
This parameter will add the following system properties:
Effects of Dev mode
Hereafter are effects of the Dev mode:
- Hot re-loading of configuration : You can modify container configuration without restarting the server. The hot re-loading can be done via JMX clients, such as JConsole, as follows:
- Connect JConsole to the eXo Platform process.
- Find an MBean with object name:
- Run the
- Unpacking .war files (Tomcat) - Particularly to eXo Platform Tomcat in the Dev mode, the startup scripts also set
EXO_TOMCAT_UNPACK_WARS=truethat results in decompressing .war archives in webapps folder.