I have modified the Java client to remove
the 10 sec restriction on both KeepAlive and Connect timeout. Will sync
across to the master repository in the next few days
All the best
discussions for paho project <paho-dev@xxxxxxxxxxx>,
PINGREQ from Eclipse Paho client ?
> do I specifically send out a PINGREQ
The client handles the PINGREQ internally - there is nothing you have
to do to trigger a PINGREQ to be sent.
> At run time, I get a IllegalArgumentException ! What is wrong ?
The javadoc for MqttConnectOptions.setKeepAliveInterval clearly says this:
@throws IllegalArgumentException if the interval is less than 10
.. which it is in your code.
That said, from a comment Arlen made (I've lost track where exactly..
perhaps over on the mqtt google group), I think we need to remove this
artificial restriction in keepAlive value in the client. I'll try to
figure out where/how to raise an issue on the paho bugzilla for this.
On 7 June 2012 18:26, ನಾಗೇಶ್ ಸುಬ್ರಹ್ಮಣ್ಯ
> I am experimenting with a client written in Paho.
> Suppose, after connecting to the broker, I do a for loop for a billion
> doing nothing. Let us say, the time taken for this loop is t1 and
> has been set to t2. If t1 < t2, then do I specifically send out
> after t2 seconds are over ? If t1 > t2, then the client would have
> PINGREQ automatically ?
> I am also facing this other peculiar issue. I wanted to change the
> value and so, I used the following. At run time, I get a
> IllegalArgumentException ! What is wrong ?
> MqttClient mc = new MqttClient(ipAddress, clientID) ;
> MqttConnectOptions connOptions = new MqttConnectOptions();
> paho-dev mailing list
paho-dev mailing list
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6