This is a sample of an HP-UX JDBC monitor log file. The beginning
of the file shows when the monitor was started, as well as the monitor configuration
settings. The left-hand column shows the UNIX process id number
(PID) of the process that is logging the information.
27152 ==========================================================27152 JDBC Monitor starting up at Wed Oct 7 09:25:00 199827152 Configuration file: moncfg 27152 Socket has port: 3170027152 JDBC Monitor PID: 2715227152 Max logfile size (bytes): 10000027152 Max number of sessions: 12827152 alias set: [JDBCSERV.JDBC.SYS] /opt/allbase/jdbc/bin/jdbcserv |
(0 PUTENVs)27152 27152 [15.0.121.172 Wed Oct 7 09:25:47 199827426 PID: 27426 assigned.27426 Login successful, user: subo27426 Service 'JDBCSERV.JDBC.SYS'.27426 Matched to 'JDBCSERV.JDBC.SYS'. 27426 Service to exec: /opt/allbase/jdbc/bin/jdbcserv 27152 PID: 27426 died. 0 left.27152 [15.0.121.172 Wed Oct 7 09:26:20 199827545 PID: 27545 assigned.27545 E Invalid userid, user: joebob127545 Exiting.]27152 PID: 27545 died. 0 left.27152 [15.0.121.172 Wed Oct 7 09:26:39 199827578 PID: 27578 assigned.27578 E Invalid password, user: subo27578 Exiting.]27152 PID: 27578 died. 0 left. |
The sample log file shows three client connections. For each
connection, the client IP address is logged, along with the time
of the connection. If there the user validation fails, the cause
of the failure is logged (note the "E" in the
second column denoting an error condition). If the user validation
succeeds, the connection to the JDBC Server is logged.
