Our list of FAQs is compiled through feedbacks from our users
and customers. If your question is not answered here, ask
us.
1. What is JDbMonitor?
JDbMonitor is a tool that allows developers to monitor database
activities for any Java application that uses JDBC to connect to
databases.
It provides a GUI application to view SQL statements as they are
executed. It will also provide various timing information such as
total processing time, execution time, data transfer time and number
of records retrieved from each SQL statement.
The best part is, no code changes is required in existing applications
for this to work. |
2. What do you mean by no code changes required?
This solution works through a JDBC proxy driver. To monitor database
activities for existing applications, the only change required is
to reconfigure the JDBC driver used in the existing application. |
3. What is the system requirements?
JRE 1.5 and above is REQUIRED to use JDBMonitor Client. If you do
not have JRE 1.5 installed in your system, we recommend downloading
the JRE embedded version of JDbMonitor.
JDbMonitor Driver will work with JRE 1.4 and above. It has not
been tested with JRE 1.3 as we do not think there is a demand for
it. Let us know if you think otherwise.
This is a 100% Java based solution, so it should run on any operating
system (OS) platform. It has been tested on the following OS:
- Microsoft Windows XP
- Red Hat Enterprise Server 3
- Fedora Core 5
- Suse Linux 9
|
4. What JDBC driver is supported?
All standard JDBC drivers are supported. JDbMonitor is a proxy JDBC
driver that relys on the underlying JDBC driver for all database
interactions. |
5. What kind of SQL operations are monitored?
SQL operations generated from Statement and PreparedStatement are supported. However, batch and callable SQL operations are in
the current version. |
6. Will it slow down my Java application?
While there are some CPU overhead to monitor database activities,
you will not be able to notice it. That is, unless you use a Java
profiler to profile a database intensive application.
In some ways, it is as much overhead as logging an application
using APIs such as Jakarta Commons Logging (JCL).
When a client is monitoring remotely, additional overhead caused
by data transferred over the network will occur. |
7. What about security?
Only authorized users will be able to monitor database activities.
This is achieved through the following features:
- Password required to monitor application
- Restrict access to monitor application by specific IP addresses/range
(and to exclude specific IP addresses/range)
- Restrict number of concurrent connections allowed to monitor application
|
8. Why am I getting the message "Error
Launching JDbMonitor" during start up?
Most common reason for this is because JDbMonitor Client cannot
detect JRE 1.5 on your system. While you can can re-install JRE
1.5.0 and try again, we recommend installing JDbMonitor with "Embedded JRE" component. |
9. I notice JDbMonitor Driver uses Jakarta
Commons Logging. Is this dependency required?
There is no library dependency for JDbMonitor Driver. However, if
Jakarta Commons Logging (JCL) is available, it will be used by default.
You can also disable the use of JCL through the "system.useJcl"
property. When disabled, all logging will be routed to "System.out". |
10. Can I monitor applications that use javax.sql.DataSource object to make a connection?
This feature will only be available in a future release. |
[ 