The application can now be run by simply executing
bin/myapp console.
Because of the way the Wrapper script sets its current directory,
it is not necessary to run this script from within the
bin directory.
/usr/lib/myapp/bin/myapp console
Running My Application...
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.x.x)
jvm 1 |
|
When running using the console
command, output from the JVM will be visible in the console.
The application can be terminated by hitting CTRL-C in the command
window. This will cause the Wrapper to shut down the application
cleanly.
As you will see if you omit a command, the scripts shipped
with the wrapper are fairly standard daemon scripts. They
accept console,
start,
stop,
restart,
status, and
dump commands.
The start,
stop, and
restart commands are common
to most daemon scripts and are used to control the wrapper and
its application as a daemon process. The
status command
can be used to find out whether or not the wrapper is currently
running. The console command
will launch the wrapper in the current shell, making it
possible to kill the application with CTRL-C. The final
command, dump, will send a
kill -3 signal to the wrapper
causing the its JVM to do a full thread dump.
|