JVM Errors MQTT I/O Server - Printable Version +- Ewon Technical Forum (https://techforum.ewon.biz) +-- Forum: Development (https://techforum.ewon.biz/forum-50.html) +--- Forum: Java (https://techforum.ewon.biz/forum-53.html) +--- Thread: JVM Errors MQTT I/O Server (/thread-2713.html) |
JVM Errors MQTT I/O Server - berntjb - 04-02-2025 Hello I've written an IO-Server that publishes tags over MQTT. I've had this installed on my Flexy 205 for 3 years now without any problems. Today I installed it on a Flexy 201 with newer fw 19 vs 16, and I'm getting some weird errors. Firstly I wasn't able to write new config using the textbox field in the IO-Server list. It just gave me an error saying "Board does not exists". Then I added the config directly through the Setup - System - Storage - Edit System cfg and rebooted the unit. It then picked up the config and connected to the MQTT broker and keeps pushing values... until it doesn't. It disconnects without any errors. But I keep seeing this in the logs, not sure if it's related: Time Source Event Clock EventID 04/02/2025 22:00:55 JVM ABORT Wonka: tryPutFifo 655: Could not push [B@0x0070e1e8 onto fifo 0x0044e8f8! 210793 28 04/02/2025 22:00:55 JVM 210793 27 04/02/2025 22:00:55 JVM Failed to allocate 4096 bytes 210792 26 The IO-server.jar was build 3 years ago. Here are the docs I've made for the installation: https://docs.clarify.io/developers/hardware/ewon-flexy Looking forward to any help ? RE: JVM Errors MQTT I/O Server - simon - 07-02-2025 Hi, Very nice job !! :-) Indeed these errors are weird... I suggest you open a support ticket for that on https://support.hms-networks.com/hc/en-us We would need the full backup of the Ewon : Maybe it is a hardware issue... (there should be no problem to use a Flexy 201) RE: JVM Errors MQTT I/O Server - simon - 12-03-2025 I have got the same issue recently and it seems it is caused by the object StringBuffer that cannot be created. I added str.ensureCapacity(10000); after the declaration of the StringBuffer. and the System/gc() at the end of the function and it seems to work better but nothing 100 % sure |