[
https://issues.apache.org/jira/browse/AMQ-7444?focusedWorklogId=535890&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-535890
]
ASF GitHub Bot logged work on AMQ-7444:
---------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jan/21 05:29
Start Date: 14/Jan/21 05:29
Worklog Time Spent: 10m
Work Description: jbonofre merged pull request #611:
URL: https://github.com/apache/activemq/pull/611
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 535890)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
