Delay export service should print stack trace if there are exception o… #8125
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
Optimize delay export service logic.
Pre condition:
If module A and B dependency the same dubbo-config core, and it define netty server port is 20880, config delay export service time is 1000 and protocol is dubbo.
Usage scenarios:
When I run module B after successfully started module A at the same compute, module B can successfully started, but module B not export any service, because module A occupied 21880 port.
Conclusion:
So, I think delay export service should print stack trace if there are exception occur so that programmer can see errors in console.
Brief changelog
Verifying this change
Checklist