CAS-management-webapp spring boot/beans version compatibility with mongo/json service registry

109 views

Skip to first unread message

Duncan Brannen

unread,

Mar 29, 2019, 7:57:34 AM3/29/19

to cas-...@apereo.org

Afternoon All,

We’re having some issues upgrading from Cas 5.2 to 5.3 (or 6.x) in that while we can get CAS up and running ok,

as soon as we try to run the management webapp with either mongo or json service registries then they won’t deploy in tomcat.

The error in the tomcat logs is

“More than one fragment with the name [spring_web] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering.”

and seems to be due to having 2 copies or spring boot and/or beans libraries.

After 5.3.0-RC4 I can’t find any version of the management webapp with the same boot/beans version pair as any of the CAS mongo/json service registry plugins.

I’ve tried adding in <excludes> to the pom.xml file but still can’t seem to get that compiled war to just have one version of the spring libraries.

Strangely, despite not including the mongo dependency, as soon as I create a management.properties file the cas-management app starts looking for a mongo database.

(without complaining about spring_web) is this normal?

Thanks,

Duncan

Jeremiah Garmatter

unread,

Jul 15, 2020, 3:45:29 PM7/15/20

to CAS Community, d...@st-andrews.ac.uk

Duncan,

I know this thread is over a year old, but I have been tasked with upgrading a (very old) CAS deployment to 5.3 and have run into the same issue.

"Caused by: java.lang.IllegalArgumentException: More than one fragment with the name [spring_web] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering."