[GitHub] [apisix] neverlaughtingboy opened a new issue #6631: help request: how can I build a http request to forward to mydubbo service

Wed, 16 Mar 2022 05:29:47 -0700 


neverlaughtingboy opened a new issue #6631:
URL: https://github.com/apache/apisix/issues/6631


   ### Description
   
   My service only supports dubbo protocol，and it use nacos  as a registry 
center，my nacos client version is 2.0.4。
   
   I have tried  config my upstream like this：
   
![image](https://user-images.githubusercontent.com/19867847/158586370-e09c102c-9729-4699-a461-5cd63b6e7fc7.png)
   upstream config
   
![image](https://user-images.githubusercontent.com/19867847/158586684-4bfa3aab-e6b8-4848-bd06-67f0838e42bd.png)
   route config
   
![image](https://user-images.githubusercontent.com/19867847/158586880-5e52f996-72a5-4b2d-84de-95f68dac0811.png)
   result：
   
![image](https://user-images.githubusercontent.com/19867847/158587175-3b44ae6a-3b90-4742-84aa-ed408ff33ee7.png)
   
   and how to config my upstream use  discovery type，I tired like this：
   
![image](https://user-images.githubusercontent.com/19867847/158588168-6c73073f-173c-446d-af3a-bcda8499c59b.png)
   
   it prompt error message：http_access_phase(): failed to set upstream: 
discovery nacos is uninitialized,
   
   ### Environment
   
   - APISIX version (run `apisix version`):2.12.1
   - Operating system (run `uname -a`):Linux  4.19.91-24.1.al7.x86_64
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):1.19.9.1
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):3.4.16-debian-10-r14
   - APISIX Dashboard version, if relevant:2.10.1-alpine
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):3.8.0
   


-- 
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]

Reply via email to