shri-arunraj opened a new issue, #3473:
URL: https://github.com/apache/servicecomb-java-chassis/issues/3473
Below is the system flow i am experimenting with,
====================================
Edge service ( developed with java chassis SDK) <-> Side car Proxy connector
(built with Service-mesh and service ports configured to point to legacy
application) --> Legacy Servlet application
====================================================
I can successfully able to run mesher as side car proxy and get it
registered in the service center. I can also able to hit provider API's
(servlet based application) via mesher side car proxy.
However I can't able to route to the provider application via mesher side
car proxy from the edge gateway.
Below is the routing configuration in edge service.
* I am using `URLMappedEdgeDispatcher`.
* And `legacy` is name of the side car provider mesher microservice with
which it has been registered in the service center.
``` http:
dispatcher:
edge:
url:
enabled: true
mappings:
legacy:
path: "/legacy/.*"
microserviceName: legacy
prefixSegmentCount: 0
versionRule: 0.0.0+ `
```
I am getting this error on runtime
```
**2022-11-10 17:38:46,606 [ERROR] [transport-vert.x-eventloop-thread-3] -
locate path failed, status:Not Found, http method:GET, path:/calculator/bmi/,
microserviceName:calculator (OperationLocator.java:72)**
```
@liubao68 It seems URLMappedEdgeDispatcher is not the right one to use here
as it does schema based routing. Please help point me how we can achieve this?
are there any other dispatchers which would effectively route traffic from edge
service to side car proxy mesher connector?
--
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]
