I\'ve been developing an application to tomcat during development phase. As we\'re moving forward, my client wants to be deployed to websphere. I\'m attempting to do so on
I had similar issue. The Websphere has some default limit on the number of classes that can be scanned. And this SpringBoot main class was probably not within that range. In my case, the issue was resolved when I set this JVM property -Dclassinfocachesize=10000 (Application servers > server1 > Process definition > Java Virtual Machine> Generic JVM arguments >) and restart WAS