MQTT broker with ACL, try to connect using bad credential sends first connection event and next disconnect event to client

Configure broker with :

<amq:broker useJmx="false" persistent="false">
<amq:transportConnectors>
<amq:transportConnector name="mqtt" uri="${jms.brokerurl}">
</amq:transportConnectors>
<amq:networkConnectors/>

<amq:plugins>
<amq:simpleAuthenticationPlugin>
<amq:users>
<amq:authenticationUser username="test" password="test" groups="admins,guests,users" />
</amq:users>
</amq:simpleAuthenticationPlugin>
<amq:authorizationPlugin>
<amq:map>
<amq:authorizationMap>
<amq:authorizationEntries>
<amq:authorizationEntry queue=">" read="admins" write="admins" admin="admins" />
<amq:authorizationEntry topic=">" read="admins" write="admins" admin="admins" />
<amq:authorizationEntry topic="ActiveMQ.Advisory.>" read="admins" write="admins" admin="admins"/>
</amq:authorizationEntries>
</amq:authorizationMap>
</amq:map>
</amq:authorizationPlugin>
</amq:plugins>
</amq:broker>

Connecting with mosquittolib (C) with bad credential rise first "on_connection" event as the connection is OK, and next "on_disconnection" event. Expected behavior is failed connection with BAD CREDENTIAL reported error form broker.