将简易Spring应用从Tomcat迁移至Liberty后无法正常运行求助

Hey there, let's walk through getting your Spring Boot app up and running on Liberty smoothly. First, let's recap what you've already accomplished successfully:

• Built a small Spring project using Gradle without issues
• Ran your generated UserSettingController.war via the command:

  java -jar UserSettingController.war
  

• Confirmed the app starts correctly by seeing the Spring Boot startup logs:

  . ____ _ __ _ _
  /\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
  ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
  \/ ___)| |_)| | | | | || (_| | ) ) ) )
  ' |____| .__|_| |_|_| |_\__, | / / / /
  =========|_|==============|___/=/_/_/_/
  :: Spring Boot :: (v2.1.0.BUILD-SNAPSHOT)
  

Now let's tackle the migration to Liberty with targeted troubleshooting steps:

1. Confirm Liberty Version Compatibility #

Your app uses Spring Boot v2.1.0.BUILD-SNAPSHOT, so you need a Liberty version that supports this release. For Spring Boot 2.1.x, Liberty 18.0.0.3 or later is required. Older versions won't have the necessary Spring Boot integration features.

2. Adjust Gradle Configuration for Liberty Packaging #

Spring Boot's executable WAR is optimized for standalone runs, but Liberty expects a standard WAR structure (or integration via the Liberty Spring Boot starter). Here's how to update your Gradle setup:

• Add the Liberty Spring Boot starter and mark Tomcat dependencies as provided (since Liberty will handle the servlet container):

  plugins {
      id 'org.springframework.boot' version '2.1.0.BUILD-SNAPSHOT'
      id 'io.spring.dependency-management' version '1.0.10.RELEASE'
      id 'war'
  }
  
  dependencies {
      implementation 'org.springframework.boot:spring-boot-starter-web'
      // Mark Tomcat as provided since Liberty is our container
      providedRuntime 'org.springframework.boot:spring-boot-starter-tomcat'
      // Add Liberty's Spring Boot starter for seamless integration
      providedRuntime 'io.openliberty.springboot:liberty-spring-boot-starter:3.0.0'
  }
  

• Ensure your main application class extends SpringBootServletInitializer—this lets Liberty bootstrap your Spring Boot app correctly:

  @SpringBootApplication
  public class UserSettingControllerApplication extends SpringBootServletInitializer {
      @Override
      protected SpringApplicationBuilder configure(SpringApplicationBuilder application) {
          return application.sources(UserSettingControllerApplication.class);
      }
  
      public static void main(String[] args) {
          SpringApplication.run(UserSettingControllerApplication.class, args);
      }
  }
  

3. Configure Liberty's server.xml #

You need to enable the right features in Liberty's server configuration to support Spring Boot. Create or update your server.xml with these entries:

<server description="Spring Boot Liberty Server">
    <!-- Enable required features for Spring Boot 2.x -->
    <featureManager>
        <feature>springBoot-2.0</feature>
        <feature>servlet-4.0</feature>
    </featureManager>

    <!-- Deploy your WAR file -->
    <webApplication id="UserSettingController" location="UserSettingController.war" contextRoot="/"/>
</server>

Note: The springBoot-2.0 feature covers all Spring Boot 2.x versions, including your 2.1.0 snapshot.

4. Dig Into Liberty's Logs for Errors #

When deployment fails, Liberty's logs will tell you exactly what's wrong. Check these files in your Liberty server directory (wlp/usr/servers/[your-server-name]/logs/):

• messages.log: Contains general server and application startup messages—look for exceptions like missing dependencies or context initialization failures
• trace.log: If you enable tracing (add <traceSpecification>com.ibm.ws.spring.boot.*=all</traceSpecification> to server.xml), it will show detailed debug info about Spring Boot integration

5. Validate Your WAR Structure #

Unzip your generated WAR and confirm these key details:

• WEB-INF/lib has all required Spring Boot dependencies except Tomcat jars (we marked those as provided, so they shouldn't be included)
• WEB-INF/classes contains all your compiled application classes and configuration files
• META-INF/MANIFEST.MF has correct classpath entries pointing to your dependencies

内容的提问来源于stack exchange，提问作者Mark Lavin