apache / apache/servicecomb-java-chassis

INFO Required: Edge gateway service routing to mesher Side car proxy

Open
#3,473 1 comment 0 reactions 0 assignees View on GitHub
edge
Dominant language
Java
Stars
1.9k
Forks
814
Avg merge
8d 23h
Merged PRs (30d)
1

Description

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?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.