com.weibo.api.motan.exception.MotanServiceException

error_message: NettyResponseFuture request timeout: serverPort=192.168.1.73:8002 requestId=1545439090469502977 interface=com.csf.api.fund.service.IFundService method=getDetail(java.lang.String) cost=500, status: 503, error_code: 10003,r=null

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web25

  • error_message: NettyResponseFuture request timeout: serverPort=192.168.1.73:8002 requestId=1545439090469502977 interface=com.csf.api.fund.service.IFundService method=getDetail(java.lang.String) cost=500, status: 503, error_code: 10003,r=null
  • error_message: NettyResponseFuture request timeout: serverPort=10.74.203.138:8002 requestId=1551237145914507265 interface=matan.FooService method=hello(java.lang.String) cost=201, status: 503, error_code: 10003,r=null
  • via GitHub by zhbgs2000
    , 1 year ago
    error_message: NettyResponseFuture request timeout: serverPort=127.0.0.1:8002 requestId=146466761543200001 interface=com.bob.soa.api.SOAServiceI method=sendsms(java.lang.String,java.lang.String,java.lang.String,java.lang.String) cost=10001, status: 503, error_code: 10003,r=
  • Stack trace

    • com.weibo.api.motan.exception.MotanServiceException: error_message: NettyResponseFuture request timeout: serverPort=192.168.1.73:8002 requestId=1545439090469502977 interface=com.csf.api.fund.service.IFundService method=getDetail(java.lang.String) cost=500, status: 503, error_code: 10003,r=null at com.weibo.api.motan.transport.netty.NettyResponseFuture.timeoutSoCancel(NettyResponseFuture.java:234) at com.weibo.api.motan.transport.netty.NettyResponseFuture.getValue(NettyResponseFuture.java:137) at com.weibo.api.motan.proxy.RefererInvocationHandler.invoke(RefererInvocationHandler.java:109) at com.sun.proxy.$Proxy44.getDetail(Unknown Source) at com.csf.business.fund.FundBaseControl.listKeys(FundBaseControl.java:29) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) at org.jboss.resteasy.plugins.server.netty.RequestDispatcher.service(RequestDispatcher.java:83) at org.jboss.resteasy.plugins.server.netty.RequestHandler.messageReceived(RequestHandler.java:52) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:783) at org.jboss.netty.handler.execution.ChannelEventRunnable.run(ChannelEventRunnable.java:69) at org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExecutor.java:316) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.