The JProfiler Profiler Framework contributes JProfiler configuration to the application at runtime.
| Detection Criterion | enabled set in the config/jprofiler_profiler.yml file |
| Tags | jprofiler-profiler=<version> |
For general information on configuring the buildpack, including how to specify configuration values through environment variables, refer to Configuration and Extension.
The framework can be configured by creating or modifying the config/jprofiler_profiler.yml file in the buildpack fork. The framework uses the Repository utility support and so it supports the version syntax defined there.
| Name | Description |
|---|---|
enabled |
Whether to enable the JProfiler Profiler |
port |
The port that the JProfiler Profiler will listen on. Defaults to 8849. |
nowait |
Whether to start process without waiting for JProfiler to connect first. Defaults to true. |
repository_root |
The URL of the JProfiler Profiler repository index (details). |
version |
The version of the JProfiler Profiler to use. Candidate versions can be found in this listing. |
After starting an application with the JPorfiler Profiler enabled, an SSH tunnel must be created to the container. To create that SSH container, execute the following command:
$ cf ssh -N -T -L <LOCAL_PORT>:localhost:<REMOTE_PORT> <APPLICATION_NAME>The REMOTE_PORT should match the port configuration for the application (8849 by default). The LOCAL_PORT can be any open port on your computer, but typically matches the REMOTE_PORT where possible.
Once the SSH tunnel has been created, your JProfiler Profiler should connect to localhost:<LOCAL_PORT> for debugging.
