The springcloud project (eureka service discovery + zuul gateway) is deployed to tomcat in docker

It is the first time to deploy springcloud to the test server docker in recent days. The following are some deployment tips and some error solutions, so as not to forget.

1. First, the springcloud project needs to be modified to deploy to tomcat:

1. Modify the tomcat import in the pom file and add the jar package of the servlet. In addition, if there is a reference to jetty in the pom file, comment or delete it. Modify the packaging type to war package.

2. The startup class of Application needs to be modified. If you use the @ComponentScan annotation, it is recommended to modify the application startup class directly.

3. If there is no database link in the project, the @SpringBootApplication of the application startup class should add parameters, namely @SpringBootApplication(exclude={DataSourceAutoConfiguration.class,HibernateJpaAutoConfiguration.class})

After completing these 3 points, you can basically package and deploy.

details as follows:

1. Since tomcat is built in spring-boot-start-web, you need to exclude the tomcat reference and add the servlet jar package

<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
<exclusions>
<exclusion>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-tomcat</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
</dependency>

If there is a reference to jetty, you need to comment or delete it.

2. Application startup class, which can directly inherit SpringBootServletInitializer and override the configure method

@SpringBootApplication
@EnableEurekaServer
public class UserApplication extends SpringBootServletInitializer{

@Override
protected SpringApplicationBuilder configure(SpringApplicationBuilder builder) {
return builder.sources(UserApplication.class);
}

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

3. If the database link is not configured in the project, you need to add the @SpringBootApplication parameter, namely

@SpringBootApplication(exclude={DataSourceAutoConfiguration.class,HibernateJpaAutoConfiguration.class})
@EnableEurekaServer
public class DiscoveryApplication extends SpringBootServletInitializer{

@Override
protected SpringApplicationBuilder configure(SpringApplicationBuilder builder) {
return builder.sources(DiscoveryApplication.class);
}

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

At this point, the project can be packaged and deployed to tomcat.

Second, the eureka service discovery deployment requires special attention to the access address

During the development process, the eureka-service address is generally (taking 8001 as an example): http://localhost:8001/eureka, and in the eureka-client configuration file: eureka.client.serviceUrl.defaultZone=http://localhost:8001 /eureka, if spring.application.name in the eureka-service configuration is not empty (take discovery as an example), that is, spring.application.name=discovery, then the eureka.client.serviceUrl.defaultZone path of eureka-client should be configured as: http ://localhost:8001/discovery/eureka.

That is, eureka-service is configured as:

spring.application.name=discovery
server.port=8001
eureka.client.register-with-eureka=false
eureka.client.fetch-registry=false
eureka.client.serviceUrl.defaultZone=http://localhost:${server.port}/eureka

The eureka-client configuration should be:

spring.cloud.config.discovery.enabled=true
eureka.instance.prefer-ip-address=true
eureka.client.serviceUrl.defaultZone=http://localhost:8001/discovery/eureka

At this point, eureka service discovery can discover services.

Three, pay attention to the configuration when deploying the zuul project

server.port=8000
server.contextPath=/mall
spring.application.name=api
eureka.client.serviceUrl.defaultZone=http://localhost:8001/discovery/eureka

endpoints.restart.enabled=true
endpoints.shutdown.enabled=true

spring.zipkin.enabled=false

hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds= 10000
ribbon.ConnectTimeout= 1000000
ribbon.ReadTimeout= 1000000

ribbon.MaxAutoRetries= 0
ribbon.MaxAutoRetriesNextServer= 0
ribbon.OkToRetryOnAllOperations= false

eureka.instance.prefer-ip-address=true

zuul.semaphore.max-semaphores=10000
zuul.host.maxTotalConnections=10000
zuul.host.max-per-route-connections=1000

# routes to serviceId
zuul.routes.user-srv.path=/user/**
zuul.routes.user-srv.service-id=user

zuul.routes.user-srv.stripPrefix=false

If the server.contextPath is used in the configuration, there is no problem in development, but there will be problems when deployed to tomcat. It is recommended to directly remove the server.contextPath configuration.

The springcloud project (eureka service discovery + zuul gateway) is deployed to tomcat in docker

Guess you like