Applications using a Startup Wrapper may not start properly when the application is instrumented with an agent. This is because the agent may add additional overhead to the startup, preventing the application from starting up in the time window allowed by the startup wrapper.
By default, many startup wrappers have a startup timeout of 30 seconds - if the application does not start within 30 seconds, it will fail with no messages written to the application or agent logs.
If the wrapper log is active, and the application is not starting up, examination of the wrapper log will show if the startup timeout was hit. If it is not active, then it can usually be activated in the wrapper.conf configuration file by adding in the line:
A location may need to be specified for this output log - controlled by the property
wrapper.logfile=<location of log> - for example, wrapper.logfile=../logs/wrapper.log