Apicurio Registry Http Event Sink issue #2704
Unanswered
marcin-brzozowski
asked this question in
Q&A
Replies: 1 comment
-
Two things, the first one is that in the version you're using we're using the netty version with the fix. The second thing is that depending on your machine and your environment, in this particular case I would avoid using the service name as the hostname and use either docker internal or your external IP address to solve this problem. Thanks |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm trying to configure the ApicurioRegistry so that it sends CloudEvents to the configured HttpEventSink.
Apicurio Registry Version:
apicurio-registry-storage-sql:2.2.5.Final
My docker-compose looks more or less like this:
However, registry for some reason keeps trying to hit the
localhost/127.0.0.1:80
server:There is one issue that I've managed to find, that looks like might be related: reactor/reactor-netty#1405
I also tried logging inside the apicurio-registry container and manually sending a POST request to the
http://cloudevents-subscriber:5000/api/events/receive
endpoint using CURL and it worked perfectly fine. Is there something I mussed up with the configuration? Maybe setting the sink viaJAVA_TOOL_OPTIONS
somehow messed up the configuration? My knowledge of Java world is pretty limited. I would be grateful for any guidance. Thank you!Beta Was this translation helpful? Give feedback.
All reactions