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

WebSphere message 'SEVERE: ssl.client.config.parse.CWPKI0019E' received running command line discover

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.4
     - WebSphere 6.1 running with HQ-agent
  • Case Links:
    none
  • Regression:
    No

Description

When executing a discover command for websphere, the following is returned as part of output:

WARNING: WSVR0073W
Apr 2, 2010 12:33:37 PM null null
SEVERE: ssl.client.config.parse.CWPKI0019E
Apr 2, 2010 12:33:37 PM null null
WARNING: ssl.default.password.in.use.CWPKI0041W
Apr 2, 2010 12:33:37 PM null null
INFO: ssl.disable.url.hostname.verification.CWPKI0027I

The command executed is:
java -jar hq-product.jar -p websphere -m discover -Dusername=wasadmin -Dpassword=wasadmin -Dlog=debug

Expected Result:
No Errors or SEVERE Warning returned during execution of command

Actual Result:
SEVERE Warning result from execution

Steps to reproduce:
1. Connect to server running WebSphere
2. Within terminal, direct to <hq-agent_install-path>/bundles/<hq-agent_version>/pdk/lib directory
3. Execute command line discover for websphere:
java -jar hq-product.jar -p websphere -m discover -Dusername=wasadmin -Dpassword=wasadmin -Dlog=debug
4. Note result returns reported warning

Work around:
N/A - discover results stil execute

Additional Notes:
Reproducible on both Linux and Windows for WebSphere 7.0

If redirecting ouput to file.log, the reported warning will not write to output.log but the reported warning will show at the command line.

Activity

Hide
German Laullon added a comment -

These messages are generated by WebSphere classes, so there is nothing to do...

Show
German Laullon added a comment - These messages are generated by WebSphere classes, so there is nothing to do...
Hide
Frederic Calindas added a comment -

According to IBM Extended Deployment Messages:

CWPKI0019E
ssl.client.config.parse.CWPKI0019E=CWPKI0019E: Error parsing the SSL client configuration file {0}. The error returned is {1}.

Explanation
There may be a problem with the syntax of the ssl.client.props file or the location of the file is invalid.

User response
Review the error returned and check the syntax and location of the ssl.client.props file.

Are we doing anything with the ss.client.props file???

Show
Frederic Calindas added a comment - According to IBM Extended Deployment Messages: CWPKI0019E ssl.client.config.parse.CWPKI0019E=CWPKI0019E: Error parsing the SSL client configuration file {0}. The error returned is {1}. Explanation There may be a problem with the syntax of the ssl.client.props file or the location of the file is invalid. User response Review the error returned and check the syntax and location of the ssl.client.props file. Are we doing anything with the ss.client.props file???
Hide
German Laullon added a comment -
Show
German Laullon added a comment - this link could help.... http://mresetar.blogspot.com/2009/09/setup-javautillogging-in-was-client.html I,m working on it...
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, 6 days ago