Spring整合MongoDB的RestAPI部署Tomcat时初始化报错求助

Hey there, let's work through this deployment issue step by step. Since your app runs perfectly locally but throws errors when deployed to Tomcat, the problem almost always ties back to environment differences or deployment-specific MongoDB configuration hiccups. Here are the key areas to check:

1. Fix MongoDB Driver Version Compatibility #

The org.mongodb:mongo-java-driver:2.13.3 dependency you're using is extremely outdated (released in 2015). It’s likely conflicting with your Spring framework version, especially if you’re using Spring 5.x or newer.

Instead of manually adding the raw driver, switch to the Spring Data MongoDB starter dependency—it handles version alignment and integration automatically:

• For Gradle:

  implementation 'org.springframework.boot:spring-boot-starter-data-mongodb'
  

• For Maven:

  <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-data-mongodb</artifactId>
  </dependency>
  

2. Verify MongoDB Connection Configs for Tomcat Environment #

Your local setup probably uses a local MongoDB instance, but the Tomcat server might not have access to it, or your configs might be hardcoded for local use:

• Double-check your application.properties/application.yml for the MongoDB URI: ensure it uses the correct host (not localhost if MongoDB is on a remote server), port, username, and password. The format should be:

  spring.data.mongodb.uri=mongodb://<username>:<password>@<remote-host>:27017/<db-name>
  

• Confirm the Tomcat server can reach the MongoDB host (ping it) and that the 27017 port is open. If you’re using a cloud MongoDB service (like Atlas), make sure the server’s IP is whitelisted.

3. Resolve Tomcat Class Loading Conflicts #

Sometimes Tomcat’s built-in JARs clash with dependencies packaged in your WAR:

• Check if your WAR includes JARs that Tomcat already provides (like servlet-api). Mark these dependencies as provided (Maven) or providedRuntime (Gradle) to exclude them from the WAR:
  • Gradle example:

    providedRuntime 'javax.servlet:javax.servlet-api:4.0.1'
    

  • Maven example:

    <dependency>
        <groupId>javax.servlet</groupId>
        <artifactId>javax.servlet-api</artifactId>
        <version>4.0.1</version>
        <scope>provided</scope>
    </dependency>
    

4. Grab the Full Jenkins Error Stack Trace #

You mentioned a Jenkins deployment error, but the full stack trace is critical for pinpointing the root cause. Look for lines starting with Caused by:—these will tell you if it’s a connection timeout, authentication failure, missing class, or something else. For example:

Caused by: com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=localhost:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.ConnectException: Connection refused}}]}

This would immediately point to a connectivity issue between Tomcat and MongoDB.

5. Ensure Spring Context Initializes Correctly (For Spring Boot) #

If you’re using Spring Boot, make sure your main application class extends SpringBootServletInitializer to properly bootstrap the Spring context in Tomcat:

@SpringBootApplication
public class YourApiApplication extends SpringBootServletInitializer {
    @Override
    protected SpringApplicationBuilder configure(SpringApplicationBuilder application) {
        return application.sources(YourApiApplication.class);
    }

    public static void main(String[] args) {
        SpringApplication.run(YourApiApplication.class, args);
    }
}

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