[hueemulation] Requesting /api/v1/settings/notifications logs errors

[Flole998]

For some reason the openHAB Android App requests a URL that doesn't exist. Anyways, this causes some errors in the log on the server which shouldn't be there in my opinion:

2021-01-06 18:38:51.306 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class org.apache.cxf.jaxrs.impl.ResponseImpl
2021-01-06 18:38:51.314 [ERROR] [org.apache.cxf.jaxrs.JAXRSInvoker   ] - No subresource locator found for path /

This is on the latest openHAB 3.0 release.

[digitaldan]

FYi the URL its hitting is trying to reach the myopenhab cloud notification endpoint, but the mobile apps don't really know if the are going through the cloud service or not (pro and con), i agree it should not be throwing a WARN or ERROR message, as its not harmful to a system.

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/warn-apache-cxf-jaxrs-utils-resourceutils-no-resource-methods-have-been-found-for-resource-class-javax-ws-rs-core-response/112417/13

[J-N-K]

Is this still the case with latest code? I don't see these messages when requesting the URL from PAW (I don't have a android device to check with the app)

[Flole998]

I only have the latest Milestone available for testing and when requesting /api/v1/settings/notifications it is still logging the message mentioned above.

[J-N-K]

Very interesting. If you request that from a browser, do you see it, too?

[Flole998]

Yes, I just checked it with a browser.

[J-N-K]

We are talking about a GET request to http://localhost:8080/api/v1/settings/notifications, correct? With or without credentials? I don't see it, neither on my production system (Debian Linux) nor on my development machine (MacOS).

Can you show your log settings?

[Flole998]

Sorry, totally forgot about this: Yes, GET request to that URL. I am doing it with credentials through a reverse proxy.

My log settings:

openhab> log:get
Logger                                             │ Level
───────────────────────────────────────────────────┼──────
ROOT                                               │ WARN
javax.jmdns                                        │ ERROR
javax.mail                                         │ ERROR
openhab.event                                      │ INFO
openhab.event.AddonEvent                           │ ERROR
openhab.event.ChannelDescriptionChangedEvent       │ ERROR
openhab.event.InboxUpdatedEvent                    │ ERROR
openhab.event.ItemAddedEvent                       │ ERROR
openhab.event.ItemChannelLinkAddedEvent            │ ERROR
openhab.event.ItemChannelLinkRemovedEvent          │ ERROR
openhab.event.ItemRemovedEvent                     │ ERROR
openhab.event.ItemStateEvent                       │ ERROR
openhab.event.RuleAddedEvent                       │ ERROR
openhab.event.RuleRemovedEvent                     │ ERROR
openhab.event.RuleStatusInfoEvent                  │ ERROR
openhab.event.StartlevelEvent                      │ ERROR
openhab.event.ThingAddedEvent                      │ ERROR
openhab.event.ThingRemovedEvent                    │ ERROR
openhab.event.ThingStatusInfoEvent                 │ ERROR
openhab.event.ThingUpdatedEvent                    │ ERROR
org.apache.cxf.jaxrs.sse.SseEventSinkImpl          │ ERROR
org.apache.karaf.jaas.modules.audit                │ INFO
org.apache.karaf.kar.internal.KarServiceImpl       │ ERROR
org.apache.karaf.shell.ssh.SshUtils                │ ERROR
org.apache.karaf.shell.support                     │ OFF
org.apache.sshd                                    │ ERROR
org.eclipse.lsp4j                                  │ OFF
org.jupnp                                          │ ERROR
org.openhab                                        │ INFO
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime                  │ OFF
su.litvak.chromecast.api.v2.Channel                │ ERROR

[J-N-K]

This is not a core issue. It only happens if hueemulation is installed (and that is also why I had issues reproducing it, I don't use that add-on). This needs to be fixed in the hueemulation add-on. Moving the issue to openhab-addons.

[lsiepel]

@Flole998 thi sis an older issue, but might look into fixing this. Would you be able to provide a debug log of the hueemulation binding with openHAB 4.2.0 when calling this url?