-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
很不错 #7
Comments
谢谢~
guangquan123 <[email protected]> 于2020年4月25日周六 下午9:18写道:
… 很期待这个项目,用心了
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#7>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGWLXTHIETAIOUPUKX5FOULROLPL7ANCNFSM4MQX3HBQ>
.
|
org.apache.dubbo.rpc.RpcException: Failed to invoke the method login in the service com.seckill.dis.common.api.user.UserServiceApi. Tried 3 times of the providers [192.168.0.4:12345] (1/2) from the registry 127.0.0.1:2181 on the consumer 192.168.0.4 using the dubbo version 2.7.1. Last error is: Invoke remote method timeout. method: login, provider: dubbo://192.168.0.4:12345/com.seckill.dis.common.api.user.UserServiceApi?anyhost=true&application=dis-seckill-gateway&bean.name=providers:dubbo:com.seckill.dis.common.api.user.UserServiceApi&check=false&default.deprecated=false&default.dynamic=false&default.lazy=false&default.register=true&default.sticky=false&default.timeout=3000&deprecated=false&dubbo=2.0.2&dynamic=false&generic=false&interface=com.seckill.dis.common.api.user.UserServiceApi&lazy=false&methods=updateUserInfo,checkUsername,getUserByPhone,getUserInfo,login,register&pid=39192&qos.enable=false®ister=true®ister.ip=192.168.0.4&release=2.7.1&remote.application=dis-seckill-user&remote.timestamp=1598544370962&revision=1.0.0&side=consumer&sticky=false×tamp=1598544927882, cause: Waiting server-side response timeout. start time: 2020-08-28 00:19:17.998, end time: 2020-08-28 00:19:20.999, client elapsed: 0 ms, server elapsed: 3001 ms, timeout: 3000 ms, request: Request [id=22, version=2.0.2, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=login, parameterTypes=[class com.seckill.dis.common.api.user.vo.LoginVo], arguments=[LoginVo{mobile='18342390420', password='00c8373145ce7d7a04b4f73155198178'}], attachments={path=com.seckill.dis.common.api.user.UserServiceApi, interface=com.seckill.dis.common.api.user.UserServiceApi, version=0.0.0, timeout=3000}]], channel: /192.168.0.4:64682 -> /192.168.0.4:12345 为啥我这里报错啊,怎么都过不去,菜鸟很受伤 |
把服务都启动起来噻 看我readme-------- 原始邮件 --------发件人: wangsaisai1990 <[email protected]>日期: 2020年8月27日周四 23:25收件人: Grootzz/dis-seckill <[email protected]>抄送: Anxu Chen <[email protected]>, Comment <[email protected]>主 题: Re: [Grootzz/dis-seckill] 很不错 (#7)
org.apache.dubbo.rpc.RpcException: Failed to invoke the method login in the service com.seckill.dis.common.api.user.UserServiceApi. Tried 3 times of the providers [192.168.0.4:12345] (1/2) from the registry 127.0.0.1:2181 on the consumer 192.168.0.4 using the dubbo version 2.7.1. Last error is: Invoke remote method timeout. method: login, provider: dubbo://192.168.0.4:12345/com.seckill.dis.common.api.user.UserServiceApi?anyhost=true&application=dis-seckill-gateway&bean.name=providers:dubbo:com.seckill.dis.common.api.user.UserServiceApi&check=false&default.deprecated=false&default.dynamic=false&default.lazy=false&default.register=true&default.sticky=false&default.timeout=3000&deprecated=false&dubbo=2.0.2&dynamic=false&generic=false&interface=com.seckill.dis.common.api.user.UserServiceApi&lazy=false&methods=updateUserInfo,checkUsername,getUserByPhone,getUserInfo,login,register&pid=39192&qos.enable=false®ister=true®ister.ip=192.168.0.4&release=2.7.1&remote.application=dis-seckill-user&remote.timestamp=1598544370962&revision=1.0.0&side=consumer&sticky=false×tamp=1598544927882, cause: Waiting server-side response timeout. start time: 2020-08-28 00:19:17.998, end time: 2020-08-28 00:19:20.999, client elapsed: 0 ms, server elapsed: 3001 ms, timeout: 3000 ms, request: Request [id=22, version=2.0.2, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=login, parameterTypes=[class com.seckill.dis.common.api.user.vo.LoginVo], arguments=[LoginVo{mobile='18342390420', password='00c8373145ce7d7a04b4f73155198178'}], attachments={path=com.seckill.dis.common.api.user.UserServiceApi, interface=com.seckill.dis.common.api.user.UserServiceApi, version=0.0.0, timeout=3000}]], channel: /192.168.0.4:64682 -> /192.168.0.4:12345
为啥我这里报错啊,怎么都过不去,初学者很受伤
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.
|
看完了,服务依次启动的,然后zookeeper和dubbo的ip不一致
Anxu Chen <[email protected]>于2020年8月28日 周五22:35写道:
…
把服务都启动起来噻 看我readme-------- 原始邮件 --------发件人: wangsaisai1990 <
***@***.***>日期: 2020年8月27日周四 23:25收件人: Grootzz/dis-seckill <
***@***.***>抄送: Anxu Chen ***@***.***>,
Comment ***@***.***>主 题: Re: [Grootzz/dis-seckill] 很不错
(#7)
org.apache.dubbo.rpc.RpcException: Failed to invoke the method login in
the service com.seckill.dis.common.api.user.UserServiceApi. Tried 3 times
of the providers [192.168.0.4:12345] (1/2) from the registry
127.0.0.1:2181 on the consumer 192.168.0.4 using the dubbo version 2.7.1.
Last error is: Invoke remote method timeout. method: login, provider:
dubbo://
192.168.0.4:12345/com.seckill.dis.common.api.user.UserServiceApi?anyhost=true&application=dis-seckill-gateway&bean.name=providers:dubbo:com.seckill.dis.common.api.user.UserServiceApi&check=false&default.deprecated=false&default.dynamic=false&default.lazy=false&default.register=true&default.sticky=false&default.timeout=3000&deprecated=false&dubbo=2.0.2&dynamic=false&generic=false&interface=com.seckill.dis.common.api.user.UserServiceApi&lazy=false&methods=updateUserInfo,checkUsername,getUserByPhone,getUserInfo,login,register&pid=39192&qos.enable=false®ister=true®ister.ip=192.168.0.4&release=2.7.1&remote.application=dis-seckill-user&remote.timestamp=1598544370962&revision=1.0.0&side=consumer&sticky=false×tamp=1598544927882,
cause: Waiting server-side response timeout. start time: 2020-08-28
00:19:17.998, end time: 2020-08-28 00:19:20.999, client elapsed: 0 ms,
server elapsed: 3001 ms, timeout: 3000 ms, request: Request [id=22,
version=2.0.2, twoway=true, event=false, broken=false, data=RpcInvocation
[methodName=login, parameterTypes=[class
com.seckill.dis.common.api.user.vo.LoginVo],
arguments=[LoginVo{mobile='18342390420',
password='00c8373145ce7d7a04b4f73155198178'}],
attachments={path=com.seckill.dis.common.api.user.UserServiceApi,
interface=com.seckill.dis.common.api.user.UserServiceApi, version=0.0.0,
timeout=3000}]], channel: /192.168.0.4:64682 -> /192.168.0.4:12345
为啥我这里报错啊,怎么都过不去,初学者很受伤
—You are receiving this because you commented.Reply to this email
directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADKX24DFMBXAQJZ2EPSGLW3SC6XATANCNFSM4MQX3HBQ>
.
|
dubbo服务启动的时候指定一下ip |
很期待这个项目,用心了
The text was updated successfully, but these errors were encountered: