ilaotan commented on issue #10018:
URL: https://github.com/apache/dubbo/issues/10018#issuecomment-1120814259
Use Dubbo's starter to open the service, only set
Dubbo.protocol.name = Tri, see the configuration information from nacos
`
dubbo.metadata-service.url-pars = {"connections": "1", "version": "1.0.0",
"dubbo": "2.0.2", "release": "3.0.7", " SIDE ":" Provider "," Port ":" 20880
"," Protocol ":" Dubbo "}
dubbo.endpoints = [{"port": 20880, "Protocol": "dubbo"}, {"port": 50051,
"protocol": "tri"}]`
MetAdata-Service has registered as a Dubbo agreement by default.
From the DefaultExecutorRepository classes, 20880 can be tracked to the
thread pool according to the port pool, and the 50051 Tri protocol will be
obtained.
You can try to add attributes and find that you can run the thread pool.
`dubbo.application.metadata-service-protocol=tri`
But there is NPE abnormal
If MetAdata-Service takes the Dubbo protocol, is it necessary to ensure that
the TRI protocol can get a thread pool from the DefaultExecutorRepository?
Or is it common to the thread pool with different protocols?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
