Luis Barrios 1f1bfff4f7 Improve logging: ...

- When a MQTT message is received, we should only log it in debug level. It is better to log the actions performed in the protocol processor at the info level (they are more meaningful).
- Capture and log every exception raised while processing the message (including RuntimeExceptions).

2017-01-11 15:33:23 +01:00

..

config

MQTT3.1.3-6 stated that the client can connect without giving up an client identifier. However, the broker should generate one for the client id as of the client gave the identifier to broker. The client will now disconnect if the client hasn't given up an identifier with clean session set to 0. Done this regarding issue #190

2016-08-07 13:17:41 +02:00

src

Improve logging:

2017-01-11 15:33:23 +01:00

pom.xml

Move log4j dependency from broker to dist - otherwise it is propagated transitively to projects using moquette as a library. Also removed redundant logback-core dependency from OSGi tests (it already has logback-classic).

2016-12-28 00:45:56 +02:00