2 Spring WebApplicationInitializers detected on classpath

Question

i have a springboot webapp and when i deployed it on my server on tomcat 7.0.54 then i got following message in catalina.out

INFO: 2 Spring WebApplicationInitializers detected on classpath

and my application is deploying twice which casue Exception

org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [inbound] with key 'inbound'; nested exception is javax.management.InstanceAlreadyExistsException

but i tried the same war file on my local system with tomcat 7.0.37 and the application works fine

any suggestion?

Thanks.

I am facing same issue while using maven appengine plugin. Not able to identify what causes the issue.It works OK without appengine plugin. Any idea what could be wrong? — Vishakha, Nov 14 '17 at 13:04
I resolved this issue by reducing scaling instances to 1. It's not actually issue. It was initializing due to scaling specified in appengine-web.xml — Vishakha, Nov 15 '17 at 09:31
Facing the same issue when running my app via appengineRun (gradle plugin). Any ideas?! — Sebastian Ullrich, Jun 04 '18 at 21:05

score 1 · Answer 1 · edited Mar 17 '17 at 20:18

1

I had the same issue. I removed spring-boot-starter-thymeleaf from my pom.xml file and it worked. You may have a library in your classpath which has another WebApplicationInitializer.

edited Mar 17 '17 at 20:18

vich

11,836
13
49
66

answered Mar 17 '17 at 19:56

diver_cle

11
1

i tried with tomcat 7.0.75 and then started working thanks for the suggestion i will give a try – Rawat Mar 18 '17 at 04:35

score 1 · Answer 2 · answered Jun 29 '17 at 09:32

1

I had the same issue. I removed compile("org.springframework.boot:spring-boot-actuator-docs") from my gradle file and it worked.

answered Jun 29 '17 at 09:32

Kamil Nękanowicz

6,254
7
34
51

score 1 · Answer 3 · answered Jul 24 '18 at 20:44

I had an identical situation. Spring Boot + Tomcat + InstanceAlreadyExistsException on a remote server but worked perfectly on my local Tomcat.

The cause was the remote server having two Host elements in server.xml pointing to the same Tomcat appBase directory (webapps.) That caused all webapps to be loaded twice. For some webapps it wasn't a problem, but for mine it was because it tried to register MBeans twice.

My solution was to replace one of the Host elements with an Alias under the other Host element. Now I just have one Host element and apps are loaded only once each.

2 Spring WebApplicationInitializers detected on classpath

3 Answers3

Linked