com.alibaba.dubbo.remoting.TimeoutException异常的解决方法

今天写商品分类和规格使用redis进行缓存的时候碰到一个头疼的BUG,早上刚开机的时候运行没有任何问题,电脑运行的东西多了之后,突然就给我报了个bug,头疼了一下午,后来找到个大牛解决了,原来是调用SpringDataRedis对数据进行存储到redis的时间过长,结果页面请求的超时时间过了,报了这个BUG ....

 

 解决方法:在@Service注解这里设置timeout

@Service(timeout = 5000),我的电脑设置为5000就好了,这个时间设置,看个人电脑配置吧。不够就多写点。
(ps:最后吐槽一句:CPU以U结尾的笔记本是真的垃圾,这辈子不会再买低压笔记本了。。。)
12月 11, 2018 8:37:08 下午 org.apache.catalina.core.StandardWrapperValve invoke
严重: Servlet.service() for servlet [springmvc] in context with path [] threw exception [Request processing failed; nested exception is com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method findByParentId in the service com.pinyougou.sellergoods.service.ItemCatService. Tried 3 times of the providers [192.168.32.1:20881] (1/1) from the registry 192.168.25.128:2181 on the consumer 192.168.32.1 using the dubbo version 2.8.4. Last error is: Invoke remote method timeout. method: findByParentId, provider: dubbo://192.168.32.1:20881/com.pinyougou.sellergoods.service.ItemCatService?anyhost=true&application=pinyougou-manager-web&check=false&dubbo=2.8.4&generic=false&interface=com.pinyougou.sellergoods.service.ItemCatService&methods=add,findByParentId,findOne,update,findPage,delete,findAll&pid=23056&revision=0.0.3-SNAPSHOT&side=consumer&timestamp=1544531824798, cause: Waiting server-side response timeout by scan timer. start time: 2018-12-11 20:37:07.649, end time: 2018-12-11 20:37:08.651, client elapsed: 2 ms, server elapsed: 1000 ms, timeout: 1000 ms, request: Request [id=2, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=findByParentId, parameterTypes=[class java.lang.Long], arguments=[0], attachments={path=com.pinyougou.sellergoods.service.ItemCatService, interface=com.pinyougou.sellergoods.service.ItemCatService, version=0.0.0}]], channel: /192.168.32.1:49225 -> /192.168.32.1:20881] with root cause
com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2018-12-11 20:37:07.649, end time: 2018-12-11 20:37:08.651, client elapsed: 2 ms, server elapsed: 1000 ms, timeout: 1000 ms, request: Request [id=2, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=findByParentId, parameterTypes=[class java.lang.Long], arguments=[0], attachments={path=com.pinyougou.sellergoods.service.ItemCatService, interface=com.pinyougou.sellergoods.service.ItemCatService, version=0.0.0}]], channel: /192.168.32.1:49225 -> /192.168.32.1:20881
	at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.returnFromResponse(DefaultFuture.java:188)
	at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:110)
	at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96)
	at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144)
	at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74)
	at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
	at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
	at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91)
	at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)
	at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77)
	at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227)
	at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)
	at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)
	at com.alibaba.dubbo.common.bytecode.proxy5.findByParentId(proxy5.java)
	at com.pinyougou.manager.controller.ItemCatController.findByParentId(ItemCatController.java:116)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:564)
	at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:222)
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969)
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
	at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
	at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:115)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:112)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:169)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:206)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:121)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.header.HeaderWriterFilter.doFilterInternal(HeaderWriterFilter.java:66)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:56)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:106)
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
	at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:214)
	at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177)
	at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
	at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:262)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:121)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1041)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:603)
	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.base/java.lang.Thread.run(Thread.java:844)

 

  • 5
    点赞
  • 11
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
### 回答1: com.alibaba.dubbo.remoting.remotingexceptionDubbo框架中的一个异常类,表示远程通信异常。在Dubbo框架中,服务提供者和服务消费者之间的通信是通过网络进行的,如果在通信过程中出现异常,就会抛出该异常。通常情况下,这种异常可能是由于网络故障、服务提供者宕机、服务消费者请求超时等原因引起的。在使用Dubbo框架时,需要对该异常进行处理,以保证系统的稳定性和可靠性。 ### 回答2: com.alibaba.dubbo.remoting.remotingexceptionDubbo框架中经常出现的一个异常Dubbo是一款高性能、分布式的RPC框架,提供了远程调用、负载均衡、集群容错、服务化治理等功能,而remotingexception则是Dubbo在远程调用过程中出现错误时抛出的异常。 在Dubbo框架中,服务提供方和服务消费方通过网络进行通信,远程调用请求会经过多个组件,如序列化组件、网络传输组件、集群容错组件等。如果在这个过程中出现了异常,就会抛出com.alibaba.dubbo.remoting.remotingexception。 常见引起com.alibaba.dubbo.remoting.remotingexception异常的原因包括: 1. 网络通信异常:包括网络延迟、网络中断、请求超时等情况。 2. 序列化异常Dubbo使用的是自定义的序列化方式,如果传输对象没有实现Serializable接口,或者序列化过程中出现了异常,就会导致com.alibaba.dubbo.remoting.remotingexception异常的抛出。 3. 服务提供方和消费方不匹配:服务提供方的接口和消费方的接口不匹配,或者参数类型、数量、顺序等不匹配,会导致com.alibaba.dubbo.remoting.remotingexception异常的抛出。 4. 其他异常Dubbo框架内部实现出现了其它异常,如调用的方法不存在、连接池满、线程池满等,也会抛出com.alibaba.dubbo.remoting.remotingexception异常。 为了解决com.alibaba.dubbo.remoting.remotingexception异常,可以通过以下方式进行优化: 1. 优化网络通信:包括优化网络质量、增加网络带宽、修改Dubbo配置等方式。 2. 合理使用AKKA:AKKA是一个支持并发编程的框架,通过Actor模型实现对并发操作的封装。Dubbo中也可以使用AKKA来进行并发控制,提高程序性能,减少网络通信时间。 3. 优化序列化:可以选用更快速的序列化方式,如Protobuf、Kryo等。 4. 常见问题排查:在出现com.alibaba.dubbo.remoting.remotingexception异常时需要对出现异常的节点进行排查,遵循排错的基本原则,逐个排查各个组件,找出异常原因并进行相应的解决。 总之,com.alibaba.dubbo.remoting.remotingexceptionDubbo框架中经常遇到的错误类型,需要我们在使用Dubbo框架时注意避免出现此类错误,并进行优化和排查。 ### 回答3: com.alibaba.dubbo.remoting.remotingexceptionDubbo分布式服务框架中的异常类之一,主要是用来表示网络通讯方面的异常。 在Dubbo框架中,远程方法调用是基于网络通信的,因此在通信过程中出现的各种异常都会抛出com.alibaba.dubbo.remoting.remotingexception异常,以便于开发者捕获并处理这些异常。该异常类的定义如下: public class RemotingException extends RpcException { private static final long serialVersionUID = -5565366231695911316L; public RemotingException(Channel channel, String message) { super(channel, message); } public RemotingException(Channel channel, Throwable cause) { super(channel, cause); } public RemotingException(Channel channel, String message, Throwable cause) { super(channel, message, cause); } } 这个异常类继承自RpcException,其中包含了通信异常的相关信息和原因。在Dubbo框架中,Dubbo服务提供者和消费者之间通过网络通信进行数据传输,如果出现网络不可访问、传输数据包被损坏等情况,都会抛出com.alibaba.dubbo.remoting.remotingexception异常。 为了避免这种异常的出现,Dubbo框架通过多种机制来保证通信的可靠性和稳定性,例如使用心跳检测机制来检测网络连接状态、使用Netty超时机制来避免超时等。另外,应用开发者也可以在代码中加入合适的异常处理机制,在出现异常时及时处理,避免异常的进一步扩散。 总之,com.alibaba.dubbo.remoting.remotingexceptionDubbo框架中一个重要的异常类,它主要用来表示网络通信方面的异常。了解它的特点和出现原因,对于准确诊断并解决Dubbo框架中的问题是有帮助的。

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

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

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

打赏作者

木子丶Li

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

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

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

打赏作者

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

抵扣说明:

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

余额充值