Closed macjunk-ie closed 4 years ago
@macjunk-ie , i think it would be better if you create a sample application with steps to replicate the issue.
I believe it is a fair point and we should configure the underlying NetSocket
to always use event-loop delivered events and then in the MQTT layer handle the worker delegation when going in the application
@macjunk-ie the SSL handshake is performed by Netty and will always be done on the event loop independently of using Vert.x client as a worker or as an event-loop verticle
When using a client from a worker verticle, then the verticle and the actual client code communicate using message passing so it's normal to have this
Scenario: I have a SSL enabled Active MQ broker. There are two types of clients: 1) A verticle that publishes a single message to the broker 2) A worker verticle that publishes a single message to the broker
Issue:
Log when run as a standard verticle:
Log when run as a worker verticle:
The client code: