Domenico Briganti
unread,Jun 28, 2022, 6:02:08 AM6/28/22Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to SmallRye
Hi Team!
I'm experiencing a strange behavior using smallrye-reactive-messaging-mqtt with Quarkus 2.10.0. It's about the famous reconnecting features...
I notice that, if I get a "java.net.SocketException: Connection reset", the underline VertX Mqtt Client reconnects, but on smallrye messaging I didn't get any message.
If I get a "Connection closed: io.vertx.core.VertxException: Connection closed", on reconnecting, it works as aspected.
The stacktrace of both exceptions are attached.
In the first case, after the reconnection, I see that messages arrive to the client, but it stops here:
2022-06-28 11:23:37,894 DEBUG [io.sma.rea.mes.mqt.ses.imp.MqttClientSessionImpl] (vert.x-eventloop-thread-0) notifySubscriptionState - topic: in, state: SUBSCRIBED, grantedQoS: 0
2022-06-28 11:23:38,027 DEBUG [io.ver.mqt.imp.MqttClientImpl] (vert.x-eventloop-thread-0) Incoming packet MqttPublishMessage[fixedHeader=MqttFixedHeader[messageType=PUBLISH, isDup=false, qosLevel=AT_MOST_ONCE, isRetain=false, remainingLength=8], variableHeader=MqttPublishVariableHeader[topicName=in, packetId=-1], payload=PooledSlicedByteBuf(ridx: 0, widx: 4, cap: 4/4, unwrapped: PooledUnsafeDirectByteBuf(ridx: 10, widx: 10, cap: 1024))]
2022-06-28 11:23:38,027 DEBUG [io.sma.rea.mes.mqt.ses.imp.MqttClientSessionImpl] (vert.x-eventloop-thread-0) Server published: io.vertx.mqtt.messages.impl.MqttPublishMessageImpl@158d8989
2022-06-28 11:23:38,953 DEBUG [io.ver.mqt.imp.MqttClientImpl] (vert.x-eventloop-thread-0) Incoming packet MqttPublishMessage[fixedHeader=MqttFixedHeader[messageType=PUBLISH, isDup=false, qosLevel=AT_MOST_ONCE, isRetain=false, remainingLength=8], variableHeader=MqttPublishVariableHeader[topicName=in, packetId=-1], payload=PooledSlicedByteBuf(ridx: 0, widx: 4, cap: 4/4, unwrapped: PooledUnsafeDirectByteBuf(ridx: 10, widx: 10, cap: 1024))]
2022-06-28 11:23:38,953 DEBUG [io.sma.rea.mes.mqt.ses.imp.MqttClientSessionImpl] (vert.x-eventloop-thread-0) Server published: io.vertx.mqtt.messages.impl.MqttPublishMessageImpl@46409360
2022-06-28 11:23:39,894 DEBUG [io.ver.mqt.imp.MqttClientImpl] (vert.x-eventloop-thread-0) Incoming packet MqttPublishMessage[fixedHeader=MqttFixedHeader[messageType=PUBLISH, isDup=false, qosLevel=AT_MOST_ONCE, isRetain=false, remainingLength=8], variableHeader=MqttPublishVariableHeader[topicName=in, packetId=-1], payload=PooledSlicedByteBuf(ridx: 0, widx: 4, cap: 4/4, unwrapped: PooledUnsafeDirectByteBuf(ridx: 10, widx: 10, cap: 512))]
I'm going to try to understand better the problem...
Regards,
Domenico