Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Executing a command line plugin operation yields ClassNotFoundException: com.ibm.db2.jcc.DB2Driver

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.3
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ-server 4.3.0-EE-1396 running on CentOS 5.4
    HQ-agent 4.3.0-EE-1396 running on CentOS 5.3
     - WebSphere 7.0 running with HQ-agent
  • Case Links:
    none
  • Regression:
    No

Description

Executing a command line plugin operation yields ClassNotFoundException: com.ibm.db2.jcc.DB2Driver.

Since we no longer package specific third party JDBC drivers, the messaging is correct. However with Sybase (we also do not provide the driver), no similar messaging is reported. There should be consistency between products when we do not provide the third party JDBC driver.

When executing a command line operation and displaying debug information, it is not helpful to see a missing driver message for something that is known does not exist on the system or the user is not concerned about.

For example, running a command line discover for websphere (java -jar hq-product.jar -p websphere -m discover -Dlog=debug) , I would be only interested in information for websphere and not about the missing DB2 driver.

Expected Result:
When running a command line operation and there are no problems, no extraneous messaging should be reported.

Actual Result:
Messaging for invalid items (DB2) are being reported when not needed.

Steps to reproduce:
1. Go to a server with no DB2 and hq-agent is running
2. Within a terminal, change to <hq-agent_install_path>/bundles/<hq-agent_version>/pdk/lib directory
3. Execute a command line operation with debugging (i.e. java -jar hq-product.jar -m discover -Dlog=debug)
2. Note the debugging information about missng JDBC driver

Work around:
N/A - extraneous messaging only

Additional Notes:
See attached was7lin-discover.log for display of all DB2 related messaging.

This issue did not exist previously in earlier builds (i.e. 1382)

Activity

Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks, 2 days ago