This represents the standard HP-UX JDBC monitor configuration
file. This is a text file that resides on the server host in the
same directory as the monitor executable file and can be used to
alter some of the monitor's behavior. The name of the monitor
configuration file is moncfg, and it is located in /opt/allbase/jdbc/bin.
MLOGPATH /opt/allbase/jdbc/logsMAXLOGSIZE 500000MAXSESSIONS 128[JDBCSERV.JDBC.SYS]SERVICE /opt/allbase/jdbc/bin/jdbcserv |
The first configuration option MLOGPATH refers to the path for the monitor log file. Normally
this is set to /opt/allbase/jdbc/logs. The log file name for the monitor is called monlog.
The second configuration option MAXLOGSIZE specifies the maximum size of the monitor log
file, before the file is backed up to the name monlog.old, and the log file reset to zero length. This prevents
the log file from growing without bounds. The maximum amount of
disk space that will be used for the monitor log is twice the amount
specified by this option (total size of the log file and the backup
log file).
The third configuration option MAXSESSIONS sets the limit on the maximum number of concurrent
sessions that is allowed by the monitor. Limiting the number of
active connections can increase performance of the server host and
prevent overload of the system. Client connections are rejected
with a java.sql.SQLException if the number of sessions are exceeded. It means
that the server is busy, and that they should try again later. If
this number is not set or set to 0, then the number of sessions is unlimited.
The last two lines of the configuration file above provide
the mapping to the JDBC Server executable. The service name of the
JDBC Server is "JDBCSERV.JDBC.SYS". The SERVICE line after the service name gives the full path
and filename of the JDBC Server.
Normally, there is no reason to edit the monitor configuration
file. If for some reason it is edited, the monitor must be reset
using the monctrl command to trigger the monitor to re-read the configuration
file. The syntax for this command is:
monctrl reset [portnumber]
where portnumber is the port number on which the monitor to be reset is
running. If the port number is not specified, the default port number is
assumed. The reset of the monitor occurs "on the fly," without affecting
any of the current established client connections.
