| Re: [paho-dev] Maximum number of inflight messages exceeded |
Are there any thoughts about making that number flexible or settable by the programmer?
Marc L Cohen
Sent from my iPad
On Nov 23, 2013, at 5:21 AM, "Ian Craggs" <icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Hi Tito,
>
> in the Java client, there is an internal setting of 10 QoS 1 or 2
> messages that can be "in-flight" (unfinished protocol exchanges) at one
> time. It is a temporary condition that will be resolved once the
> sending of at least one message has been completed.
>
> So the application should try again in a short period of time. If you
> are using the async API, you could wait until a callback is made telling
> you that the next message has been sent.
>
> It does not apply to QoS 0 messages as there are no ACKs nor message ids
> in that case.
>
> Ian
>
> On 23/11/13 00:33, Tito Cheriachan wrote:
> > Hi all,
> >
> > I am using the paho mqtt java client and I was sending out a lot of messages every second , but the mqtt connection was not established , then I encountered an exception like maximum number of in flight messages exceeded.
> >
> > 1. Does this happen if the mqtt is not able to push out messages to the broker ?
> >
> > 2.will it happen on all qos levels ?
> >
> > 3.On what all scenarios will this occur.
> > _______________________________________________
> > paho-dev mailing list
> > paho-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/paho-dev
>
> _______________________________________________
> paho-dev mailing list
> paho-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/paho-dev
>