Messages stop arriving after a while

[matheusfillipe]

Thanks for the great plugin!

I've been trying it out in the latest versions of minecraft but I noticed I the messages stop arriving into minecraft after a while, while they are still sent. Meaning users in the gateway receive incoming messages from the plugin but the plugin doesn't show the messages over the gateway to the minecraft chat nor logs them.

I found out that if I restart matterbridge it gets fixed for a while after this crashes and restarts:

minecraft-mc-1  | [10:20:27 ERROR]: [MatterBukkit] org.apache.http.ConnectionClosedException: Premature end of chunk coded message body: closing chunk expected
minecraft-mc-1  | org.apache.http.ConnectionClosedException: Premature end of chunk coded message body: closing chunk expected
minecraft-mc-1  |       at org.apache.http.impl.io.ChunkedInputStream.getChunkSize(ChunkedInputStream.java:263) ~[httpcore-4.4.16.jar:4.4.16]
minecraft-mc-1  |       at org.apache.http.impl.io.ChunkedInputStream.nextChunk(ChunkedInputStream.java:222) ~[httpcore-4.4.16.jar:4.4.16]
minecraft-mc-1  |       at org.apache.http.impl.io.ChunkedInputStream.read(ChunkedInputStream.java:183) ~[httpcore-4.4.16.jar:4.4.16]
minecraft-mc-1  |       at org.apache.http.impl.io.ChunkedInputStream.read(ChunkedInputStream.java:210) ~[httpcore-4.4.16.jar:4.4.16]
minecraft-mc-1  |       at org.apache.http.impl.io.ChunkedInputStream.close(ChunkedInputStream.java:312) ~[httpcore-4.4.16.jar:4.4.16]
minecraft-mc-1  |       at org.apache.http.impl.execchain.ResponseEntityProxy.streamClosed(ResponseEntityProxy.java:142) ~[httpclient-4.5.14.jar:4.5.14]
minecraft-mc-1  |       at org.apache.http.conn.EofSensorInputStream.checkClose(EofSensorInputStream.java:228) ~[httpclient-4.5.14.jar:4.5.14]
minecraft-mc-1  |       at org.apache.http.conn.EofSensorInputStream.close(EofSensorInputStream.java:172) ~[httpclient-4.5.14.jar:4.5.14]
minecraft-mc-1  |       at java.base/java.util.zip.InflaterInputStream.close(Unknown Source) ~[?:?]
minecraft-mc-1  |       at java.base/java.util.zip.GZIPInputStream.close(Unknown Source) ~[?:?]
minecraft-mc-1  |       at org.apache.http.client.entity.LazyDecompressingInputStream.close(LazyDecompressingInputStream.java:94) ~[httpclient-4.5.14.jar:4.5.14]
minecraft-mc-1  |       at MatterBukkit.jar/com.selfcoders.matterbukkit.APIMessageReader.lambda$start$0(APIMessageReader.java:93) ~[MatterBukkit.jar:?]
minecraft-mc-1  |       at java.base/java.lang.Thread.run(Unknown Source) ~[?:?]
minecraft-mc-1  | [10:20:28 WARN]: Exception in thread "MatterBridge-API-Listener" java.lang.IllegalArgumentException: Illegal group reference
minecraft-mc-1  | [10:20:28 WARN]:      at java.base/java.util.regex.Matcher.appendExpandedReplacement(Unknown Source)
minecraft-mc-1  | [10:20:28 WARN]:      at java.base/java.util.regex.Matcher.appendReplacement(Unknown Source)
minecraft-mc-1  | [10:20:28 WARN]:      at java.base/java.util.regex.Matcher.replaceAll(Unknown Source)
minecraft-mc-1  | [10:20:28 WARN]:      at java.base/java.lang.String.replaceAll(Unknown Source)
minecraft-mc-1  | [10:20:28 WARN]:      at MatterBukkit.jar//com.selfcoders.matterbukkit.APIMessageReader.lambda$start$0(APIMessageReader.java:78)
minecraft-mc-1  | [10:20:28 WARN]:      at java.base/java.lang.Thread.run(Unknown Source)
minecraft-mc-1  | [10:20:30 INFO]: [MatterBukkit] Restarting API listener
minecraft-mc-1  | [10:20:30 INFO]: [MatterBukkit] Starting API listener thread

At least that used to work but now I found out user messages are no longer getting sent at all even if I restart everything. No error logs for that.

[Programie]

I guess this could be caused by some network timeout or MatterBridge closing the connection due to inactivity. Usually, the plugin should automatically reconnect to the MatterBridge API. But in this case, it looks like the HTTP client in MatterBukkit doesn't even see that there was a timeout and just endless waits there.

I will have a look whether there is some way to keep the stream active.

[Programie]

I found a better way to keep the connection alive. MatterBridge also exposes a Websocket server at /api/websocket additionally to the existing /api/stream and /api/message endpoints.

I've updated the plugin to use a Websocket client connecting to /api/websocket instead of a raw HTTP client waiting for messages to arrive at /api/stream. This should hopefully fix the issue as Websockets are more reliable in case of network issues, restarts of the server, etc.