Tim Marcus Moore

It looks like what's happening here is that the services are trying to contact the service registry, and that it being routed through the proxy. Is 127.0.0.1 also in your...

In that case, I'm kind of stumped @erip. You're probably in the best position to debug this. Does setting `lagomServiceLocatorAddress in ThisBuild := "0.0.0.0"` (without `0.0.0.0` added to no proxy)...

@gabox01 this sounds like a different issue than what @erip originally reported, which is new in 1.5.0-M2. I think it would be better to keep this issue focused on that...

@ignasi35 why do you say that adding to the reference guide would not be great? I would think that all of the functionality in the framework would ideally be in...

@edmondo1984 I agree that a filter would be better for that use case. See docs on [`EssentialFilter`](https://www.playframework.com/documentation/2.6.x/JavaHttpFilters#More-powerful-filters). @ignasi35 #409 describes tracing from the client-side.

Is this the same as #1091?

For reference, here's the original discussion of this: https://discuss.lightbend.com/t/cassandra-read-side-and-a-jdbc-readside-event-processor-possible-in-lagom-1-4/881?u=tmoore

I'm going to reword the title of this issue, so that it reflects the problem to be solved from a Lagom user's perspective, rather than the specific implementation of the...

Relates to #1353, but that issue is about having multiple instances of one read-side type (e.g., multiple RDBMS) while this is about mixing different types (Cassandra and RDBMS).

Also, I think this will probably be 1.5.0+ only and not backported, because it will introduce new APIs.