[
https://issues.apache.org/jira/browse/AMQ-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957579#comment-15957579
]
ASF subversion and git services commented on AMQ-6638:
------------------------------------------------------
Commit 6fe437a3d63f94da74f9bb169e8095198592ded5 in activemq's branch
refs/heads/activemq-5.14.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=6fe437a ]
https://issues.apache.org/jira/browse/AMQ-6638
Adds some additional logging to the connection validation code, adds
some additional tests as well.
(cherry picked from commit 0752d840b90a5acdb04410362fb16c943f09dc2f)
> isHeaderValid doesn't log reasons
> ---------------------------------
>
> Key: AMQ-6638
> URL: https://issues.apache.org/jira/browse/AMQ-6638
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Ben Boo
> Fix For: 5.15.0, 5.14.5
>
>
> AmqpWireFormat#isHeaderValid has four branches in which it returns 'false' ==
> 'not valid'.
> There's no logging in any of these four cases. As a beginner user it's nearly
> impossible to guess what exactly the problem is.
> Some logging including reasons would go a long way, make things more
> accessible, and save time.
> Related items:
> *
> https://stackoverflow.com/questions/43038083/activemq-vs-amqp-net-lite-versions
> * https://github.com/Azure/amqpnetlite/issues/201
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
