You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (Jira)" <ji...@apache.org> on 2019/10/01 14:49:00 UTC
[jira] [Created] (GEODE-7261) Geode V1 admin rest does not start
with Spring 5.x jars on the classpath
Jens Deppe created GEODE-7261:
---------------------------------
Summary: Geode V1 admin rest does not start with Spring 5.x jars on the classpath
Key: GEODE-7261
URL: https://issues.apache.org/jira/browse/GEODE-7261
Project: Geode
Issue Type: Bug
Components: rest (admin)
Reporter: Jens Deppe
The geode-web war includes several spring jars, but does not include {{spring-core}}. With Jetty debug logging enabled we can see the following error:
{noformat}
[vm0] 07:30:50.469 [RMI TCP Connection(1)-127.0.0.1] DEBUG org.eclipse.jetty.servlet.ServletHandler - EXCEPTION
[vm0] java.lang.NoClassDefFoundError: org/springframework/core/ErrorCoded
[vm0] at java.lang.ClassLoader.defineClass1(Native Method)
[vm0] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
[vm0] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
[vm0] at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
[vm0] at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
[vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
[vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
{noformat}
In addition, the war file also include {{commons-logging}} which causes the war logging to be redirected to stderr when various slf4j bridging libraries are also on the classpath (pulled in transitively through spring-geode-starter).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)