You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2020/11/23 05:31:00 UTC
[jira] [Updated] (AMQ-7444) Invalid certificate warnings should
include client IP information
[ https://issues.apache.org/jira/browse/AMQ-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated AMQ-7444:
--------------------------------------
Fix Version/s: (was: 5.15.14)
5.15.15
> Invalid certificate warnings should include client IP information
> -----------------------------------------------------------------
>
> Key: AMQ-7444
> URL: https://issues.apache.org/jira/browse/AMQ-7444
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.15.12
> Reporter: Lionel Cons
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.16.1, 5.15.15
>
>
> Note: this is a followup of AMQ-7301.
> In ActiveMQ 5.15.12, invalid certificate warnings look like this:
> {code}
> 2020-03-18 09:39:43,977 [ActiveMQ BrokerService[foo.acme.com] Task-23] WARN TransportConnector - Could not accept connection from null: javax.net.ssl.SSLHandshakeException: General SSLEngine problem (unable to find valid certification path to requested target)
> {code}
> This does not to find the culprit client. ActiveMQ should (also) log the client IP address (and port), like it is done for instance in case of invalid credentials.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)