SpringCloud微服务负载均衡_Ribbon技术

最新推荐文章于 2024-03-17 12:37:35 发布
最新推荐文章于 2024-03-17 12:37:35 发布
阅读量1.5k 收藏 1
点赞数
分类专栏： SpringCloud 文章标签： java spring
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/DreamsArchitects/article/details/109525194
版权

Spring Cloud Ribbon

一、介绍

Spring Cloud Ribbon是基于Netflix Ribbon实现的一套客户端的负载均衡的工具。

简单的说，Ribbon是Netflix发布的开源项目，主要功能是提供客户端的软件负载均衡算法，将Netflix的中间层服务连接在一起。Ribbon客户端组件提供一系列完善的配置项如连接超时，重试等。简单的说，就是在配置文件中列出Load Balancer（简称LB）后面所有的机器，Ribbon会自动的帮助你基于某种规则（如简单轮询，随机连接等）去连接这些机器。我们也很容易使用Ribbon实现自定义的负载均衡算法。

   		<dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-netflix-ribbon</artifactId>
        </dependency>

yml

server:
  port: 8001 #服务端口
eureka:
  instance:
    hostname: user8001
    instance-id: user8001
    prefer-ip-address: true
  client:
    service-url:
       defaultZone: http://localhost:7000/eureka
spring:
  application:
    name: user8001

RestTemplate

服务间的访问就需要使用RestTemplate, 它是专门用于服务间访问的

@Configuration
public class RestTemplateConfig {

    @Bean
    public RestTemplate getRestTemplate(){
        return new RestTemplate();
    }
}

Controller

@RestController
@RequestMapping("/user")
public class UserController {

    @Autowired
    RestTemplate restTemplate;

    /**
     *  getForObject(String url,Object.class);   get方式访问url指定的微服务,Object.class 返回的数据类型
     *  getForEntry(String url,Object.class)
     *  getForObject(String url, Class<T> responseType, Map<String, ?> uriVariables)  这三个参数分别代表 REST请求地址、HTTP响应转换被转换成的对象类型、请求参数
     *  postForObject(String url,Object.class)
     *  postForEntry(String url,Object.class)
     */

    @GetMapping("/callDept")
    public Object callDept(){
        String msg = "访问Dept服务";
          return restTemplate.getForObject("http://localhost:8002/dept/called",Object.class);
    }
  }

三、Dept微服务模块

yml

server:
  port: 8002 #服务端口
eureka:
  instance:
    hostname: dept8002
    instance-id: dept8002
    prefer-ip-address: true
  client:
    service-url:
       defaultZone: http://localhost:7000/eureka
spring:
  application:
    name: dept

Controller

@RestController
@RequestMapping("/dept")
public class DeptController {

   @GetMapping("/called")
   public Object beCall() {
        System.out.println("dept : 被访问了");
        return "{\"code\":\"200\"}";
    }
}

测试User服务调用Dept服务

将两个服务启动起来，使用User模块调用Dept模块

报错

2020-11-06 10:01:06.929 ERROR 10253 --- [nio-8001-exec-1] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.web.client.RestClientException: Error while extracting response for type [class java.lang.Object] and content type [application/xml;charset=UTF-8]; nested exception is org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Unexpected character '{' (code 123) in prolog; expected '<'
 at [row,col {unknown-source}]: [1,1]; nested exception is com.fasterxml.jackson.core.JsonParseException: Unexpected character '{' (code 123) in prolog; expected '<'
 at [row,col {unknown-source}]: [1,1]] with root cause

com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '{' (code 123) in prolog; expected '<'
 at [row,col {unknown-source}]: [1,1]
	at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:666) ~[woodstox-core-5.3.0.jar:5.3.0]
	at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2130) ~[woodstox-core-5.3.0.jar:5.3.0]
	at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1179) ~[woodstox-core-5.3.0.jar:5.3.0]
	at com.fasterxml.jackson.dataformat.xml.XmlFactory._initializeXmlReader(XmlFactory.java:685) ~[jackson-dataformat-xml-2.10.1.jar:2.10.1]
	at com.fasterxml.jackson.dataformat.xml.XmlFactory._createParser(XmlFactory.java:568) ~[jackson-dataformat-xml-2.10.1.jar:2.10.1]
	at com.fasterxml.jackson.dataformat.xml.XmlFactory._createParser(XmlFactory.java:29) ~[jackson-dataformat-xml-2.10.1.jar:2.10.1]
	at com.fasterxml.jackson.core.JsonFactory.createParser(JsonFactory.java:972) ~[jackson-core-2.10.1.jar:2.10.1]
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3258) ~[jackson-databind-2.10.1.jar:2.10.1]
	at org.springframework.http.converter.json.AbstractJackson2HttpMessageConverter.readJavaType(AbstractJackson2HttpMessageConverter.java:239) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.http.converter.json.AbstractJackson2HttpMessageConverter.read(AbstractJackson2HttpMessageConverter.java:227) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.client.HttpMessageConverterExtractor.extractData(HttpMessageConverterExtractor.java:104) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:744) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:677) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.client.RestTemplate.getForObject(RestTemplate.java:318) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at com.lsh.controller.UserController.callDept(UserController.java:32) ~[classes/:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_211]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_211]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_211]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_211]
	at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:106) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:888) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:793) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:634) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) ~[tomcat-embed-websocket-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:93) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:526) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:860) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1591) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_211]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_211]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_211]

在这里插入图片描述
我们看到Dept模块已经被访问到了，但是User报错了。
在这里插入图片描述

解决办法1：

将restTemplate.getForObject的返回数据类型修改给String
在这里插入图片描述

解决办法2：

对调用方法设置对返回值的格式为json即可解决

 public <T> ResponseEntity<T> getJson(String url, String requestJson, Class<T> responseType) {
        HttpHeaders headers = new HttpHeaders();
        headers.setContentType(MediaType.APPLICATION_JSON_UTF8);

        //设置接收返回值的格式为json
        List<MediaType> mediaTypeList = new ArrayList<>();
        mediaTypeList.add(MediaType.APPLICATION_JSON_UTF8);
        headers.setAccept(mediaTypeList);

        HttpEntity<String> entity = new HttpEntity<>(requestJson, headers);

        ResponseEntity<T> responseEntity;

        System.out.println(requestJson);

        responseEntity = restTemplate.exchange(url, HttpMethod.GET, entity, responseType);

        return responseEntity;
    }

完整的的UserController代码：

package com.lsh.controller;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.http.*;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;
import org.springframework.web.client.RestTemplate;

import java.util.ArrayList;
import java.util.List;

/**
 * @author ：LiuShihao
 * @date ：Created in 2020/11/6 9:45 上午
 * @desc ：
 */
@RestController
@RequestMapping("/user")
public class UserController {

    @Autowired
    RestTemplate restTemplate;

    /**
     *  getForObject(String url,Object.class);   get方式访问url指定的微服务,Object.class 返回的数据类型
     *  getForEntry(String url,Object.class)
     *  getForObject(String url, Class<T> responseType, Map<String, ?> uriVariables)  这三个参数分别代表 REST请求地址、HTTP响应转换被转换成的对象类型、请求参数
     *  postForObject(String url,Object.class)
     *  postForEntry(String url,Object.class)
     */

    @GetMapping("/callDept")
    public Object callDept(){
        String msg = "访问Dept服务";
//          return restTemplate.getForObject("http://localhost:8002/dept/called",Object.class);
           return getJson("http://localhost:8002/dept/called",msg,Object.class);
    }


    public <T> ResponseEntity<T> getJson(String url, String requestJson, Class<T> responseType) {
        HttpHeaders headers = new HttpHeaders();
        headers.setContentType(MediaType.APPLICATION_JSON_UTF8);

        //设置接收返回值的格式为json
        List<MediaType> mediaTypeList = new ArrayList<>();
        mediaTypeList.add(MediaType.APPLICATION_JSON_UTF8);
        headers.setAccept(mediaTypeList);

        HttpEntity<String> entity = new HttpEntity<>(requestJson, headers);

        ResponseEntity<T> responseEntity;

        System.out.println(requestJson);

        responseEntity = restTemplate.exchange(url, HttpMethod.GET, entity, responseType);

        return responseEntity;
    }
//    public <T> ResponseEntity<T> postJson(String url, String requestJson, Class<T> responseType) {
//
//        HttpHeaders headers = new HttpHeaders();
//        headers.setContentType(MediaType.APPLICATION_JSON_UTF8);
//
//        //设置接收返回值的格式为json
//        List<MediaType> mediaTypeList = new ArrayList<>();
//        mediaTypeList.add(MediaType.APPLICATION_JSON_UTF8);
//        headers.setAccept(mediaTypeList);
//
//        HttpEntity<String> entity = new HttpEntity<>(requestJson, headers);
//
//        ResponseEntity<T> responseEntity;
//
//        System.out.println(requestJson);
//
//        responseEntity = restTemplate.exchange(url, HttpMethod.POST, entity, responseType);
//
//        return responseEntity;
//    }
}

User服务调用Dept服务带参数

在这里插入图片描述

UserController：

    @GetMapping("/callDeptAndParam")
    public String callDeptAndParam(){
        String msg = "访问Dept服务  带参数";
        HashMap<String, String> map = new HashMap<>();
        map.put("id","1");
        String forObject = restTemplate.getForObject("http://localhost:8002/dept/called/{id}", String.class, map);
        System.out.println("forObject:"+forObject);
        return forObject;
    }

DeptController:

   @GetMapping("/called/{id}")
   public Object beCallById(@PathVariable("id") String id) {
        System.out.println("dept : 被访问了");
        return "{\"code\":\"8002\",\"id\":\""+id+"\"}";
    }

User模块调用Dept模块Post请求，带参数

UserController：

    @PostMapping("/CallDeptPost")
    public String userCallDeptPost () {
        /**
         * url : 要调用的其他服务端的地址
         * responseType : 被调用服务的方法的返回数据类型
         */
        Map<String,String> map = new HashMap<>();
        map.put("id","2");
        map.put("name","招生部");
        /**
         * uri : 其他微服务地址
         * request : 请求中的数据
         * responseType :响应回的数据类型
         * @ return : ResponseEntity --> 所有响应数据
         *      响应消息头
         *      响应消息行
         *      响应正文  --> 有dept返回的ResultObject数据
         */
        ResponseEntity<String> stringResponseEntity = restTemplate.postForEntity("http://localhost:8002/dept/beCalledPost", map, String.class);
        // getBody 获取其中的响应正文
        String body = stringResponseEntity.getBody();
        return body;
    }

注意：被调用的方法必须使用@RequestBody注解接收
DeptController：

    @PostMapping("/beCalledPost")
    public Object beCalledPost(@RequestBody Map<String,String> map){
        System.out.println("dept  beCalledPost : 被访问了");
        return "{\"code\":\"8002\",\"id\":\""+map.get("id")+"\",\"name\":\""+map.get("name")+"\"}";
    }

四 、创建第二个Dept微服务模块

yml配置文件

注意： 项目的名称不变 ，
spring:
application:
name: dept

server:
  port: 8003 #服务端口
eureka:
  instance:
    hostname: dept8003
    instance-id: dept8003
    prefer-ip-address: true
  client:
    service-url:
       defaultZone: http://localhost:7000/eureka
spring:
  application:
    name: dept

五、开启Ribbon负载均衡

1.Ribbon的pom依赖

在User模块的pom文件添加Ribbon的pom依赖

   		<dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-netflix-ribbon</artifactId>
        </dependency>

2.@LoadBalanced

在User微服务模块的RestTemplateConfig加@LoadBalanced //开启负载均衡
在这里插入图片描述

3.调用的URL

在User模块的调用Dept服务的方法中，url不能使用IP+RORT来访问，需要使用Dept的项目名称。
在这里插入图片描述

在这里插入图片描述

测试负载均衡

默认为轮询访问
在这里插入图片描述
在这里插入图片描述

Liu_Shihao
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
SpringCloud微服务-客户端负载Ribbon
02-24
什么是客户端负载我们在做服务集群的时候，经常会听到负载均衡这个词，比如下图的一个架构：客户端在访问服务器的时候，中间一般会用一些硬件（F5）或软件（nginx）来作负载均衡，从而实现后端各服务器分摊请求压力...
Spring Cloud微服务架构学习之Ribbon负载均衡（六）
01-20
理解Ribbon对于我们使用Spring Cloud来讲非常的重要，因为负载均衡是对系统的高可用、网络压力的缓解和处理能力扩容的重要手段之一。在上节的例子中，我们采用了声明式的方式来实现负载均衡。实际上，内部调用维护了...
RestTemplate 调用exchange方法 请求参数 和返回 值都为json 数据，http请求报错
执笔成念的博客
02-26 6691
RestTemplate 调用exchange 请求 发送 和返回 json 数据，报错 报错信息 org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Unexpected character '{' (code 123) in prolog; expected '<' at [row,col {unknown-source}]: [1,1]; nested exception
“JSON parse error: Unexpected character (‘\“‘ (code 34)): was expecting comma to separate Object ent
weixin_43997319的博客
03-09 1万+
报错"JSON parse error: Unexpected character ('\"' (code 34)): was expecting comma to separate Object entries; nested exception is com.fasterxml.jackson.core.JsonParseExc 只需要看这个'\"'，代表换行符报错，缺少换行分隔符的含义 JSON parse error: Unexpected end-of-input: expected cl
报错：Unexpected character (‘}‘ (code 125)): was expecting double-quote to start field name
RosLu的博客
08-18 6126
报错信息：org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Unexpected character ('}' (code 125)): was expecting double-quote to start field name;nested exception is com.fasterxml.jackson.core.JsonParseException: Unexpected .
curl执行请求报错Unexpected character (‘‘‘ (code 39)): expected a valid value
猴戏浅滩的博客
10-21 4408
Unexpected character (''' (code 39)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')\n at [Source: (org.elasticsearch.common.io.stream.InputStreamStreamInput); line: 1, column: 2]
java调用PHP接口时，遇到问题
ni_hao_ya的专栏
11-13 4592
org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireF ault: Unexpected character 'S' (code 83) in epilog; expected '  at [row,col {
Spring Cloud 微服务权限系统搭建教程 脚手架
07-21
6. Ribbon 负载均衡器。 7. Hystrix 熔断器。 8. Turbine 监控中心。 9. Nacos 配置中心。 10. Sentinel 流控组件。 本系统的架构图如下： FEBS Cloud FEBS Prometheus APM FEBS Skywalking APM 系统的 License ...
73-Spring Cloud客户端负载均衡Ribbon笔记1
08-08
总的来说，Ribbon是Spring Cloud中实现客户端负载均衡的重要工具，它与`RestTemplate`的结合使得在微服务架构中能够轻松地在多个服务实例间进行负载分布，提高了系统的稳定性和可扩展性。理解并掌握Ribbon的工作原理...
hive异常及处理办法汇总
weixin_39690956的博客
04-15 1198
异常1： Exception in thread “main” java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative path in absolute URI: KaTeX parse error: Expected '}', got 'EOF' at end of input: …a.io.tmpdir%7D/%7Bhive.session.id%7D_resources 修复办法： 创建目录：/Users/ke
【Maxwell】Maxwell监听日志时报错：Unexpected character (‘‘‘ (code 39)): expected a valid value
一只野生的小黑猫的博客
10-24 385
Caused by: java.sql.SQLException: com.fasterxml.jackson.core.JsonParseException: Unexpected character (''' (code 39)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
部署hadoop大数据报错如何解决
最新发布
weixin_70099460的博客
03-17 946
首次启动 HDFS 时，必须对其进行格式化操作。
解决JSON传参报错问题
程序小白的博客
08-21 6055
解决JSON传参报错问题
cxf3.2 wsdl2java异常_cxf工具wsdl2java生成客户端代码错误，，急，遇到过的给看看麻烦各位大神了...
weixin_42252435的博客
02-27 892
使用cxf的工具wsdl2java工具命令如下C:\Users\Administrator>e:E:\>cd E:\zkr.code\weather\srcE:\zkr.code\weather\src>wsdl2java -all http://ws.webxml.com.cn/WebServices/WeatherWS.asmx?wsdlWSDLToJava Error: h...
java开发错误JsonParseException: Unexpected character ('?' (code 255)): was expecting comma to separate
热门推荐
xiaoxing91094947的博客
10-14 4万+
在java后端的开发中，我们会经常遇到一个错误就是：JsonParseException: Unexpected character (’?’ (code 255)): was expecting comma to separate OBJECT entries， 当我们遇到这错误后别担心，去看看请求参数格式和符号是否正确，一般这个错误是由于请求参数的json格式错误引起的。比如一个英文",“写成...
JSON.parse: unexpected character的排查
架构设计
04-06 1198
近发现Javascript+json+php开发有点意思，于是做了个小查询功能“通过IP查询用户信息”. 一、先创建三个文件：一个js（实现对主表单对象和php结果的操作），一个后台取数据的php文件和一个index.php，index.php中调用到了自定义js 和www.json.org的json2.js &lt;script src="/json/json2.js" type="te...
Confluence 文档保存不了arser message: Unexpected character '=' (code 61) (expected a name start character)
xiaobeizi1的博客
10-31 3357
Parser message: Unexpected character '=' (code 61) (expected a name start character)   有些不是链接的设置成链接文本了，点击取消链接即可。仔细查看一下文档的蓝色部分...
Springcloud微服务自定义负载均衡策略
05-21
在Spring Cloud中，我们可以通过自定义负载均衡策略来实现对服务的自定义路由。下面是自定义负载均衡策略的步骤： 1. 创建一个自定义的负载均衡器 ```java public class MyLoadBalancer implements LoadBalancer { private final AtomicInteger position; public MyLoadBalancer() { this.position = new AtomicInteger(0); } @Override public ServiceInstance choose(String serviceId) { List<ServiceInstance> instances = discoveryClient.getInstances(serviceId); if (instances.isEmpty()) { return null; } int index = position.getAndIncrement() % instances.size(); return instances.get(index); } } ``` 2. 在配置文件中定义自定义负载均衡器 ```yaml my-loadbalancer: ribbon: NFLoadBalancerClassName: com.example.MyLoadBalancer ``` 3. 在RestTemplate中使用自定义负载均衡器 ```java @Configuration public class MyConfig { @Autowired private IClientConfig config; @Bean public RestTemplate restTemplate() { return new RestTemplate(new MyLoadBalancerClient(config)); } } ``` 以上就是自定义负载均衡策略的实现方式。需要注意的是，该方式需要自己实现负载均衡器，并且在配置文件中进行定义和使用。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

Liu_Shihao

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值