Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1095809 - Unwanted and misleading SSL info messages on qpidd service startup [NEEDINFO]
Unwanted and misleading SSL info messages on qpidd service startup
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
Development
Unspecified Unspecified
medium Severity low
: 3.0
: ---
Assigned To: Andrew Stitcher
Frantisek Reznicek
: Regression
Depends On: 1092621
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-08 10:54 EDT by Justin Ross
Modified: 2015-01-21 07:52 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
It was discovered that misleading SSL messages appeared in logs if the HA Module was loaded into the Broker and logging was turned up to INFO or higher. Messages similar to the following are displayed: "2014-04-29 10:17:34 [Security] info SSL connector not enabled, you must set QPID_SSL_CERT_DB to enable it." This message is harmless. The message is not referring to the regular SSL functionality of the broker: it is referring to the outgoing client functionality of the HA client. There is no workaround to this issue, except to disregard this message if it appears in the logs.
Story Points: ---
Clone Of: 1092621
Environment:
Last Closed: 2015-01-21 07:52:28 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
freznice: needinfo? (jmorgan)


Attachments (Terms of Use)

  None (edit)
Comment 6 Petr Matousek 2014-08-20 12:12:52 EDT
Release note added. the defect is tracked as Bug 1092621.

Red Hat Enterprise Messaging 3.0 Release Notes (Mon Aug 18 2014)
Built from Content Specification: 22896, Revision: 699608

-> VERIFIED
Comment 8 Petr Matousek 2014-09-09 04:51:36 EDT
Hello Justin, Andrew,
  may I possibly ask you for creating doctext (CCFR form), please? This defect is private and as Jared pointed out in comment 7 it would be optimal to have complete doctext.
Comment 13 Frantisek Reznicek 2014-09-22 03:53:50 EDT
We reached acceptance criteria for this defect, defect is now public and listed in release notes.

-> VERIFIED

Note You need to log in before you can comment on or make changes to this bug.