We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
try{ ReferenceConfigCache cache = ReferenceConfigCache.getCache(); Object proxy = cache.get(new ReferenceConfig()); }catch (Throwable e){ e.printStackTrace(); }
Pls. provide [GitHub address] to reproduce this issue.
We are able to get proxy after start up the provider. Object proxyNew = cache.get(config);
What actually happens? cache always return null even provider started.
I think, we have to return null once consumer startup failed.
public <T> T get(ReferenceConfig<T> referenceConfig) { String key = generator.generateKey(referenceConfig); ReferenceConfig<?> config = cache.get(key); if (config != null) { return (T) config.get(); } T t = referenceConfig.get(); if (null == t){ return null; }else{ cache.putIfAbsent(key, referenceConfig); return t; } }
Otherwise, the consumer cannot recover, as it have been initialized. The solution of #2233 is not able to resolve the issue.
private void init() { if (initialized) { return; } initialized = true; }
The text was updated successfully, but these errors were encountered:
My mistake, the solution of #2233 is able to solve the issue.
Sorry, something went wrong.
haiyang1985
No branches or pull requests
Environment
Steps to reproduce this issue
Object proxyNew = cache.get(config);
Pls. provide [GitHub address] to reproduce this issue.
Expected Result
We are able to get proxy after start up the provider.
Object proxyNew = cache.get(config);
Actual Result
What actually happens?
cache always return null even provider started.
I think, we have to return null once consumer startup failed.
Otherwise, the consumer cannot recover, as it have been initialized. The solution of #2233 is not able to resolve the issue.
The text was updated successfully, but these errors were encountered: