[SOLVED?] org.glassfish.jersey.media.sse.OutboundEvent errors when using BasicUI

Since upgrading to openHAB 2.5.0~S1493-1, I frequently see the following on my log when I have the BasicUI open and I issue a command to one of my devices:

2019-01-10 06:09:28.938 [ERROR][        items-1][e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/event-stream, type=class org.glassfish.jersey.media.sse.OutboundEvent, genericType=class org.glassfish.jersey.media.sse.OutboundEvent.

I occasionally saw these errors with 2.5.0-S1491, but they seemed to have stopped at some point. I am trying a restart to see if these errors reoccur.

1 Like

I had the same issue when upgrading from 2.3 to 2.4, cleaning the cache and rebooting worked for me.

Interesting, after restarting OH, I am not seeing the error when using the BasicUI. Must be an OH startup issue. Qualitatively, OH startup has been much improved since the later 2.4.0 snapshots, but it still needs improvement. I am running openHABian on an RPi 3B here.

1 Like

For some time now,

sudo rm -rf /var/lib/openhab2/{cache,tmp}/*

is part of my OH upgrade sequence, so cache and tmp had already been cleared the first time I started the system after upgrading to 2.5.0-S1493-1. I just wish it wasn’t necessary to restart after an initial start following an upgrade, or sometimes well after an upgrade has been installed.

1 Like

Same here.

For me a restart didn’t work but the reboot did.

Didn’t know that, thanks for the info.:+1:

Hello,

I have the same behaviour in release 2.4 - 1, this started after clearing the cache

sudo systemctl stop openhab2
sudo openhab-cli clean-cache
sudo reboot

and my error log

2019-08-23 09:20:36.958 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/event-stream, type=class org.glassfish.jersey.media.sse.OutboundEvent, genericType=class org.glassfish.jersey.media.sse.OutboundEvent.

This error logs periodically when the Browser Basic UI sitemaps is open and only once at the Android openHAB app when starting lunching it.

I posted this because it may help to repeat or debug this behaviour. Now I will try to solve it with recommendations.

bye

NOTE: ERROR gone after rebooting once…

Reproducing the ERROR log:

sudo systemctl stop openhab2
sudo openhab-cli clean-cache
sudo reboot

ERROR log returned

sudo reboot

ERROR log gone…

conclusion: in my version OH 2.4 the ERROR log described before and the continuous disconnects of basic UI sitemaps started after “openhab-cli clean-cache” and was solved with a single “reboot”.

I am seeing this error when running Basci UI in the browser (firefox) on Debian 9
OpenHAB version 2.5M3

16:08:05.776 [ERROR] [ge.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/event-stream, type=class org.glassfish.jersey.media.sse.OutboundEvent, genericType=class org.glassfish.jersey.media.sse.OutboundEvent.

openhab is running on a battery backup powered system and only gets restarted when I do so. At this point the host system has been running for over 6 weeks.

Dear Community,

i am receiving also those errors on the actual openHAB 2.5.0-1 (Release Build):

==> /var/log/openhab2/openhab.log <==

2019-12-31 09:53:06.377 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/event-stream, type=class org.glassfish.jersey.media.sse.OutboundEvent, genericType=class org.glassfish.jersey.media.sse.OutboundEvent.

I already cleared the cache several times with
sudo systemctl stop openhab2
sudo openhab-cli clean-cache
sudo reboot

and also with
sudo systemctl stop openhab2
sudo rm -rf /var/lib/openhab2/{cache,tmp}/*
sudo reboot

the rest of the system seems stable to me - like it was before my upgrade from the last snapshot build

… and i cant seem to find the cause for the “e.internal.WriterInterceptorExecutor/MessageBodyWriter” to do something.

my system is doing normal stuff like processing temperature updates.

2019-12-31 10:09:05.118 [vent.ItemStateChangedEvent] - network_pingdevice_04d7542d_latency changed from 184.0 to 2064.0

2019-12-31 10:09:05.133 [vent.ItemStateChangedEvent] - network_pingdevice_04d7542d_lastseen changed from 2019-12-31T10:08:02.992+0100 to 2019-12-31T10:09:05.107+0100

2019-12-31 10:09:07.083 [vent.ItemStateChangedEvent] - Temperature_Kaum_ZR changed from 8.2 to 8.3

2019-12-31 10:09:07.087 [vent.ItemStateChangedEvent] - jeelink_lacrosse_28_temperature changed from 8.2 °C to 8.3 °C

2019-12-31 10:09:25.810 [vent.ItemStateChangedEvent] - systeminfo_computer_openHABianPi_cpu_uptime_inhours changed from 59.4 to 60.4

==> /var/log/openhab2/openhab.log <==

2019-12-31 10:10:00.961 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/event-stream, type=class org.glassfish.jersey.media.sse.OutboundEvent, genericType=class org.glassfish.jersey.media.sse.OutboundEvent.

==> /var/log/openhab2/events.log <==

2019-12-31 10:10:00.970 [vent.ItemStateChangedEvent] - Temperature_Kaum_HT changed from -1.1 to -1.0

2019-12-31 10:10:00.986 [vent.ItemStateChangedEvent] - jeelink_lacrosse_56_temperature changed from -1.1 °C to -1.0 °C

2019-12-31 10:10:01.220 [vent.ItemStateChangedEvent] - network_device_192_168_5_1_time changed from 11.0 to 17.0

2019-12-31 10:10:01.715 [vent.ItemStateChangedEvent] - network_pingdevice_c038870b_lastseen changed from 2019-12-31T10:09:01.591+0100 to 2019-12-31T10:10:01.681+0100

2019-12-31 10:10:02.301 [vent.ItemStateChangedEvent] - jeelink_lacrosse_8_temperature changed from 9.5 to 9.7

2019-12-31 10:10:02.326 [vent.ItemStateChangedEvent] - Temperature_Kaum_WZ changed from 9.5 to 9.7

2019-12-31 10:10:03.370 [vent.ItemStateChangedEvent] - jeelink_lacrosse_11_temperature changed from 9.1 °C to 9.0 °C

Those errors occur around every minute. sometimes half a minute. These are the only errors i get.

thanks already in advance

after two more clean attempts and reboots i got rid of the message. I did exactly the same again. Dont know why this was so stubborn