Remove reference to JDOM from JMS Cluster (as JDOM is no longer in use)

Description

We’re running Geoserver with the JMS Cluster extension in a Cloud environment. When adding a style we didn’t get the message through to the other instances, and we got an error message saying that we were missing the class org.jdom2.JDOMException.

The extension zip-file that we’re pulling in, doesn’t have the appropriate jar file, but when I added this manually things seems to work.

So the easiest solution would probably be to add this jar to the release script for the extension, but then I saw this issue: Remove dependency on jdom. Indicating that we rather should look at why this class was tried constructed.

Environment

None

Activity

Jody Garnett 
May 29, 2024 at 5:27 PM

I have updated the title to reflect the solution for the release notes.

Jody Garnett 
May 28, 2024 at 5:34 PM

Thanks for untangling this!

Fixed

Details

Assignee

Reporter

Affects versions

Components

Priority

Created May 23, 2024 at 2:12 PM
Updated May 29, 2024 at 5:27 PM
Resolved May 28, 2024 at 5:59 PM