portzone.blogg.se

1. #Abstract queue java full
2. #Abstract queue java android
3. #Abstract queue java code
4. #Abstract queue java plus

This was taken from my Nokia 7 Plus (Android 9 Pie). It’s probably due to queued up SMs not being acknowledged (especially over WiFi).

#Abstract queue java code

The same code runs fine (sending messages) on a different phone (Samsung Note 3, running Lollipop) over WiFi as well as mobile data - it does not get the same crash / exception. It crashes consistently over WiFi but very rarely over mobile data. As long as I’m using mobile data and not WiFi, everything’s OK. There’s also no problem sending out messages when it’s on mobile (LTE) connection. There’s no problem accessing the internet otherwise. On this particular phone, messages (stanzas) do not reach the server when running over WiFi.

((XMPPTCPConnection) connection).setUseStreamManagementResumption(true) Ĭrash log : Queue fullĪt (AbstractQueue.java:98)Īt .add(ArrayBlockingQueue.java:296)Īt .XMPPTCPConnection$PacketWriter.drainWriterQueueToUnacknowledgedStanzas(XMPPTCPConnection.java:1519)Īt .XMPPTCPConnection$PacketWriter.init(XMPPTCPConnection.java:1298) Stream Management is enabled (does not crash if SM is disabled) ((XMPPTCPConnection) connection).setUseStreamManagement(true)

#Abstract queue java android

This crash has been encountered on Android with smack 4.1.9 as well as older versions.Īccording to the Java documentation, it is preferable to use Queue#offer instead of Collection#add to avoid this kind of exception… java:855)Īt .connect(AbstractXMPPConnection.ja va:364)Īt $2.run(ReconnectionManager.java:242)

#Abstract queue java full

Fatal Exception: : Queue full at (AbstractQueue.java:69)Īt .add(ArrayBlockingQueue.java:282)Īt .XMPPTCPConnection$PacketWriter.drainWriterQueueToUna cknowledgedStanzas(XMPPTCPConnection.java:1456)Īt .XMPPTCPConnection$PacketWriter.init(XMPPTCPConnectio n.java:1233)Īt .XMPPTCPConnection.initConnection(XMPPTCPConnection.j ava:645)Īt .nnectInternal(XMPPTCPConnection.