Note that there are some explanatory texts on larger screens.

plurals
  1. POjava.io.EOFException with paho
    primarykey
    data
    text
    <p>i want to make stress test on mosquitto, so i create some code as below</p> <pre><code>for (int i = 0; i &lt; 800; i++) { final int j = i; Thread t = new Thread(new Runnable() { @Override public void run() { System.out.println(j + " : ************"); try { MqttClient client = new MqttClient("tcp://192.168.88.203", SERVER_CLIENTID_PREFIX + j); client.connect(); MqttMessage message = new MqttMessage((j + ":me").getBytes()); message.setQos(2); client.publish(TOPIC_PREFIX + j, message); } catch (MqttSecurityException e) { e.printStackTrace(); } catch (MqttException e) { e.printStackTrace(); } } }); t.start(); } </code></pre> <p>But, I got some errors like <code>EOFException</code> during run and some client is disconnect. I want to know how many clients can publish messages at same time with one mosquitto server, and how can I make the stress test. Thanks!</p> <p>The detail exception is :</p> <pre><code> Connection lost (32109) - java.io.EOFException at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:162) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.EOFException at java.io.DataInputStream.readByte(DataInputStream.java:250) at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(MqttInputStream.java:51) at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:121) ... 1 more </code></pre> <p>And I found some log from mosquitto server: </p> <pre><code>1383736170: Socket read error on client Server-82, disconnecting. </code></pre> <p>Please help me, thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload