Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash - The queue for a subscriber of EventLogger exceeds 5000 elements #4580

Open
xsherlockpl opened this issue Jan 28, 2025 · 0 comments
Open
Labels
bug An unexpected problem or unintended behavior of the Core

Comments

@xsherlockpl
Copy link

clean install of 4.3.2 with just Modbus and MQTT bindings. does not last more then 5 days with about 70 items updated every 5-10 seconds.
x86 Ubuntu 24.04
openjdk version "21.0.5" 2024-10-15
OpenJDK Runtime Environment (build 21.0.5+11-Ubuntu-1ubuntu124.04)
OpenJDK 64-Bit Server VM (build 21.0.5+11-Ubuntu-1ubuntu124.04, mixed mode, sharing)

Expected Behavior

It should not crash

Current Behavior

2025-01-28 02:53:48.550 [INFO ] [b.core.io.websocket.log.LogWebSocket] - WebSocket error: java.util.concurrent.TimeoutException: Idle timeout expired: 10001/10000 ms
2025-01-28 02:57:12.711 [WARN ] [ab.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.openhab.core.io.monitor.internal.EventLogger@24203be2' takes more than 5000ms.
2025-01-28 02:59:57.711 [INFO ] [b.core.io.websocket.log.LogWebSocket] - WebSocket error: <null>
2025-01-28 04:03:59.446 [WARN ] [ab.core.internal.events.EventHandler] - The queue for a subscriber of type 'class org.openhab.core.io.monitor.internal.EventLogger' exceeds 5000 elements. System may be unstable.

Possible Solution

Tried to double the java heap, with no sucess

Steps to Reproduce (for Bugs)

I see quite a lot of failed reads from the Modbus binding, as the Solis inverted tends not to return data reliably

Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint [slaveId=1, functionCode=READ_INPUT_REGISTERS, start=33161, length=20, maxTries=3]). Will try again soon. Error was I/O error, so resetting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: SocketTimeoutException Read timed out [operation ID 2e68ba34-d7f8-432f-852c-569b983ae928]

@xsherlockpl xsherlockpl added the bug An unexpected problem or unintended behavior of the Core label Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of the Core
Projects
None yet
Development

No branches or pull requests

1 participant