You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem occurs while stress testing some brokers like Bevywise MQTT Route and HiveMq as they support only 25 clients to be connected in their evaluation versions.
MQTT Route keeps a client connection count which works based on the Clean Session. Hence what happens while connecting to the Broker Server(using MQTT Stresser) the second connection request from the same client (MQTT Stresser ) to publish/subscribe some msgs is being treated as a New client and client counter gets increased by 1 and thus exceeds 25.
If we could initiate a client connection to the MQTTRoute setting the Clean session as false ( 0 ), It will treats the second connection request with the same unique Client ID as a re-connection and will not increase the connected client count and I can conduct some fare stress test keeping all the testing parameters constant for all the brokers that I put for evaluation of performace.
The text was updated successfully, but these errors were encountered:
Biswajeeban
changed the title
Is there anyway any configurational option in MQTT Stresser to initiate a client collection keeping the clean session "False" ?
Is there anyway any configurational option in MQTT Stresser to initiate a client connection keeping the clean session "False" ?
Jun 8, 2018
arnisoph
changed the title
Is there anyway any configurational option in MQTT Stresser to initiate a client connection keeping the clean session "False" ?
initiate a client connection clean_session=false
Jun 11, 2018
sure, there's an option to set CleanSession to false. we would just have to make it configurable while keeping "true" as default and make all MQTT client IDs (WorkerId) the same.
The problem occurs while stress testing some brokers like Bevywise MQTT Route and HiveMq as they support only 25 clients to be connected in their evaluation versions.
MQTT Route keeps a client connection count which works based on the Clean Session. Hence what happens while connecting to the Broker Server(using MQTT Stresser) the second connection request from the same client (MQTT Stresser ) to publish/subscribe some msgs is being treated as a New client and client counter gets increased by 1 and thus exceeds 25.
If we could initiate a client connection to the MQTTRoute setting the Clean session as false ( 0 ), It will treats the second connection request with the same unique Client ID as a re-connection and will not increase the connected client count and I can conduct some fare stress test keeping all the testing parameters constant for all the brokers that I put for evaluation of performace.
The text was updated successfully, but these errors were encountered: