You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2016/02/05 21:50:39 UTC

[jira] [Commented] (ARTEMIS-391) Connection Limit doesn't log when over the limit

    [ https://issues.apache.org/jira/browse/ARTEMIS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134950#comment-15134950 ] 

clebert suconic commented on ARTEMIS-391:
-----------------------------------------

[~jbertram] I am assigining this to you just as I know you wrote this. If you can't do now assign it to null.

> Connection Limit doesn't log when over the limit
> ------------------------------------------------
>
>                 Key: ARTEMIS-391
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-391
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: clebert suconic
>            Assignee: Justin Bertram
>             Fix For: 1.3.0
>
>
> The current security limit doesn't log anything when going beyond the limit:
> there is a Log.DEBUG, and an empty exception that is not shown anywhere.
>        else {
>             if (ActiveMQServerLogger.LOGGER.isDebugEnabled()) {
>                ActiveMQServerLogger.LOGGER.debug(new StringBuilder().append("Connection limit of ").append(connectionsAllowed).append(" reached. Refusing connection from ").append(ctx.channel().remoteAddress()));
>             }
>             throw new Exception();
>          }
> The conneciton should be closed, and proper log should be printed. I think this is a situation for log.warn as the admins will need to be aware of it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)