Bug #6012
d1_libclient_java printing 'checkServerTrusted - RSA' to stderr
100%
Description
d1_libclient_java prints 'checkServerTrusted - RSA' anytime anything is done with a certificate making any error log virtually useless since it mostly contains trace messages instead of error messages.
Related issues
Associated revisions
refs #6012: refactored all Syste.err.println statements in CertificateManager: keeping only those in catch blocks, and converting those to trace level log statements.
refs #6012: refactored all Syste.err.println statements in CertificateManager: keeping only those in catch blocks, and converting those to trace level log statements.
refs #6012: refactored all Syste.err.println statements in CertificateManager: keeping only those in catch blocks, and converting those to trace level log statements.
refs #6012 merged CertificateManager bugfix to v1.3 branch
refs #6012 merged CertificateManager bugfix to v1.3 branch
refs #6012 merged CertificateManager bugfix to v1.3 branch
refs #6012: merge CertificateManager bug fix (polluting system err with System.err.println's) from trunk to branch 1.4
refs #6012: merge CertificateManager bug fix (polluting system err with System.err.println's) from trunk to branch 1.4
refs #6012: merge CertificateManager bug fix (polluting system err with System.err.println's) from trunk to branch 1.4
History
#1 Updated by Rob Nahf over 10 years ago
that was done to get "logging" from an anonymous class when we were having lots of certificate issues. The fix is removal of one line.
It can be done as a point release (libclient_java v1.3.1) that can be included in CCI-1.4 release, or wait for next major / minor release.
#2 Updated by Rob Nahf over 10 years ago
- % Done changed from 0 to 50
- Status changed from New to In Progress
- Assignee changed from Robert Waltz to Rob Nahf
removed trace level statements, converted sys err statements in exception handler to log statements - needed to remove the private scope from the logger in the enclosing CertificateManager class, so the anonymous inner TrustManager class can access it.
Need to merge into v1.3 and v1.4 branches
#3 Updated by Robert Waltz over 10 years ago
- Product Version changed from 1.4.0 to *
#4 Updated by Robert Waltz about 10 years ago
- Due date changed from 2014-08-02 to 2014-09-24
- Target version changed from 2014.30-Block.4.3 to CCI-1.5.0
#5 Updated by Robert Waltz about 10 years ago
- Target version changed from CCI-1.5.0 to CCI-1.4.1
#6 Updated by Robert Waltz about 10 years ago
- Target version changed from CCI-1.4.1 to CCI-1.4.2
#7 Updated by Rob Nahf about 10 years ago
- Due date changed from 2014-09-24 to 2014-09-25
- % Done changed from 50 to 90
- Status changed from In Progress to Testing
the fix was rolled into V1.3 and V1.4 branches 8/28/2014, but never recorded.
#8 Updated by Robert Waltz about 10 years ago
- Due date changed from 2014-09-25 to 2014-10-02
- Target version changed from CCI-1.4.2 to CCI-1.4.1
#9 Updated by Rob Nahf about 10 years ago
- Due date changed from 2014-10-02 to 2014-10-17
- Product Version changed from * to 1.3.1
#10 Updated by Robert Waltz about 10 years ago
- Due date changed from 2014-10-17 to 2014-10-07
- Target version changed from CCI-1.4.1 to CCI-1.5.0
#11 Updated by Rob Nahf about 10 years ago
- Milestone changed from CCI-1.4 to None
- % Done changed from 90 to 100
- Status changed from Testing to Closed
- Due date changed from 2014-10-07 to 2014-12-15
tested in beta and stage as part of CCI-1.5.0 release, and encountered no problems.
