Re: [paho-dev] Nullpointer in commsReceiver

[Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx>]

Hi Maarten,

James, who is looking after the Java client, is away at EclipseCon this 
week.  It might be best to open a bug.

Thanks

Ian

On 10/30/2015 10:31 AM, Maarten van Schouwenburg wrote:
> I very rarely encounter the following problem:
>
> Exception in thread "MQTT Rec: backend1" java.lang.NullPointerException
>          at
> org.eclipse.paho.client.mqttv3.internal.ClientState.notifyResult(ClientState.java:1001)
>          at
> org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:842)
>          at
> org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:119)
>          at java.lang.Thread.run(Thread.java:722)
>
>
> It seems like token can be NULL sometimes under high load. In the
> commsreceiver the token is actually checked to see it's not null, but
> when it's retrieved from the tokenstore in ClientState for the second
> time, it doesn't seem to be there anymore.
>
> Is this a race condition? Would it improve anything if I just pass the
> retrieved token to ClientState as a parameter instead of getting it from
> the tokenstore again?
>
> Thanks,
>
> Maarten van Schouwenburg
>
>
>
> _______________________________________________
> paho-dev mailing list
> paho-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/paho-dev

--
Ian Craggs
icraggs@xxxxxxxxxx                 IBM United Kingdom
Paho Project Lead; Committer on Mosquitto