I would suggest focusing on Docker networking rather than Tomcat. My
guess is that how that works will inform your Tomcat configuration. You
might also try first getting it to work with two Docker instances on a
single machine.
-Terence Bandoian
On 3/1/2024 11:59 AM, Manak Bisht wrote:
I am
I am fairly certain now that the docker container is the problem. I am
unable to replicate the issue without it. Using the hostname/IP address of
the host (tomcat/ip) for the receiver always causes the following problem,
01-Mar-2024 22:30:32.315 INFO [main]
Manak,
On 2/12/24 10:33, Manak Bisht wrote:
Chris,
On Mon, 12 Feb 2024, 20:52 Christopher Schultz, <
ch...@christopherschultz.net> wrote:
I wouldn't refuse to configure, since anyone using
0.0.0.0 with /separate/ hosts wouldn't experience this problem.
I am using separate hosts (two
Chris,
On Mon, 12 Feb 2024, 20:52 Christopher Schultz, <
ch...@christopherschultz.net> wrote:
> I wouldn't refuse to configure, since anyone using
> 0.0.0.0 with /separate/ hosts wouldn't experience this problem.
I am using separate hosts (two docker containers on two different machines)
in my
Mark,
On 2/9/24 06:14, Mark Thomas wrote:
With the Receiver using address="0.0.0.0" I see the same issues you do.
I'm not yet convinced that is a bug.
If this is known to essentially always not-work... should we log
something at startup? I wouldn't refuse to configure, since anyone using
