Class not found exception in web.log for the GeocoderServiceManager

Description

When you install OpenNMS Horizon and start it up you get the following exception in our Jetty web.log:

It seem like we have a fix in but haven't pushed the fix upstream.

Environment

Debian 11: Installation from our Debian package repository. Cent 8: Install from Yum package repository.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Chandra Gorantla March 30, 2022 at 6:13 PM

Mark Mahacek January 27, 2022 at 12:34 AM

Replicated on a brand new 2021.1.10.

However, after going to the Geocoder config web UI and then to another page a few times, the page started rendering properly.

Dino Yancey December 7, 2021 at 4:15 PM

It is my understanding that this happens because the geocoder feature ships unconfigured, and this exception goes away once the geocoder feature is configured.

Fixed

Details

Assignee

Reporter

HB Grooming Date

HB Backlog Status

FD#

Story Points

Sprint

Fix versions

Priority

PagerDuty

Created December 7, 2021 at 3:51 PM
Updated March 30, 2022 at 8:18 PM
Resolved March 30, 2022 at 8:18 PM