HP Driver for JDBC User's Manual

Chapter 3 29
Installation
Starting and Stopping HP JDBC Monitor
Starting and Stopping HP JDBC Monitor
HP JDBC Monitor is the server-side counterpart of HP Driver for
JDBC, present on the client-side. For a JDBC application to connect to a
database, the JDBC Monitor must be running on the database server.
JDBC Monitor can be started manually or automatically at system
startup by including the JDBC Monitor start commands in the system
startup scripts.
HP-UX Monitor Startup and Shutdown
The startup and shutdown of the HP-UX JDBC Monitor is normally
controlled by the system startup and shutdown scripts. Thus as long as
the machine is up and running, the JDBC Monitor will also be up.
The only time the Monitor should ever be brought down is to install a
newer version. In this case, use the monctrl command to kill the
Monitor process. Do not use the UNIX kill command, as this could
render the server unable to start a new Monitor process. The monctrl
command to shut down the monitor is:
monctrl kill [
portnumber ]
The
portnumber parameter is necessary only if the monitor you wish to
shut down is not running on the default port number 31700.
To restart the monitor after it has been accidentally terminated or was
shut down, use the monctrl command to start it up:
monctrl start [ portnumber ]
Again, the
portnumber parameter is necessary only if you wish to start
the monitor on a port number other than the default port number
31700.
You cannot start a monitor on the same port number as a currently
running monitor. You also can not re-start a monitor on its original port
number until all child processes that were spawned by the previous
monitor process are terminated, and the port released. If the monitor is
intentionally terminated or accidentally terminates, all of its child
processes must be terminated before it can be restarted. For this
reason, the monitor must not be terminated by using the UNIX kill
command. Always use the monctrl tool to kill the monitor. The tool will
search out all the child processes and kill them first, before killing the
monitor.