Skip to content
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

@Reference annotation issue #2164

Closed
2 tasks done
YoungHu opened this issue Aug 2, 2018 · 2 comments
Closed
2 tasks done

@Reference annotation issue #2164

YoungHu opened this issue Aug 2, 2018 · 2 comments
Labels
type/bug Bugs to being fixed

Comments

@YoungHu
Copy link
Contributor

YoungHu commented Aug 2, 2018

  • I have searched the issues of this repository and believe that this is not a duplicate.
  • I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

  • Dubbo version: 2.6.2
  • Operating System version: mac os 10.13/win10
  • Java version: JDK6/7/8

Step to reproduce this issue

  1. provider side shutdown
  2. start consumer side use @reference annotation(check=true)
  3. invoke provider get NPE

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

like consumer with xml config <dubbo:refrence>, if not provider application startup failed.

Actual Result

application startup successful, and when invoke provider get NPE, then we startup the provider side still get NPE

If there is an exception, please attach the exception trace:

Just put your stack trace here!

case reason:
when use @Refence annotation(be know that check default value is true) , if no provider actually ReferenceConfig class throw exception, but this exception was ignored.

@zonghaishang zonghaishang added type/bug Bugs to being fixed priority/normal labels Aug 2, 2018
@rocky-peng
Copy link

this issue had been resolved in the newest master . test date: 2018-08-4

@YoungHu
Copy link
Contributor Author

YoungHu commented Aug 30, 2018

same issue with #1999 ,so close this one

@YoungHu YoungHu closed this as completed Aug 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Bugs to being fixed
Projects
None yet
Development

No branches or pull requests

3 participants