[
https://issues.apache.org/jira/browse/AMQ-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264609#comment-17264609
]
ASF subversion and git services commented on AMQ-7444:
------------------------------------------------------
Commit 0c1b3e9240dbda0aee0426bfcef5e9cc628af7c7 in activemq's branch
refs/heads/master from jbonofre
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=0c1b3e9 ]
[AMQ-7444] Fallback to remote location for remote address when socket has not
been created yet
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
