Configuring Apicurio Registry event sourcing with HTTP Error

Description

Trying to use APICURIO reg mem event sourcing with HTTP, followed all the steps mentioned in - https://www.apicur.io/registry/docs/apicurio-registry/2.3.x/getting-started/assembly-configuring-the-registry.html#registry-cloud-events_registry

custom API is up and running properly and accessible as well

in logs can see appropriate event Type : io.apicurio.registry.artifact-created as well but while firing event seems port taken default and not considering mentioned in configuration

suspected code : https://github.com/Apicurio/apicurio-registry/blob/c6afc84d269e93bf81756ddefbf9c9dd3c436aa7/app/src/main/java/io/apicurio/registry/events/http/HttpEventSink.java#L85

error msg is also confusing to identify whether its going in if (line 88) or else (line 91) block

Environment

localhost docker

Steps to Reproduce

1. Start Apicurio mem registry
2. Have ready to use API with endpoint /events and provide configurations as mentioned : https://www.apicur.io/registry/docs/apicurio-registry/2.3.x/getting-started/assembly-configuring-the-registry.html#registry-cloud-events_registry
3. perform CRUD on apicurio registry mem NOTE: All was done localhost docker custom API is accessible from docker –>

Expected vs Actual Behaviour

event sourcing should happen and get all information

Logs

INFO <> [io.apicurio.registry.events.http.HttpEventSink] (vert.x-eventloop-thread-0) Firing event io.apicurio.registry.artifact-created
spingboot-test-apicurio-1 | 2022-10-20 07:13:52 ERROR <> [io.apicurio.registry.events.http.HttpEventSink] (vert.x-eventloop-thread-0) Error sending event to http://myspringapp:9999/events: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:80
spingboot-test-apicurio-1 | Caused by: java.net.ConnectException: Connection refused
spingboot-test-apicurio-1 | at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
spingboot-test-apicurio-1 | at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777)
spingboot-test-apicurio-1 | at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330)
spingboot-test-apicurio-1 | at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
spingboot-test-apicurio-1 | at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:710)
spingboot-test-apicurio-1 | at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:658)
spingboot-test-apicurio-1 | at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:584)
spingboot-test-apicurio-1 | at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496)
spingboot-test-apicurio-1 | at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
spingboot-test-apicurio-1 | at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
spingboot-test-apicurio-1 | at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
spingboot-test-apicurio-1 | at java.base/java.lang.Thread.run(Thread.java:829)

[carlesarnal]

Hi @1indiangirl,

We need a bit more context here, like the Registry version you’re using, how you’re configuring the sink and, if possible, a reproducer of the issue. From the error, it seems to me that Registry cannot access your Spring application, but it’s a bit hard to say without more information.

[cs0978]

We can reproduce this behavior with OpenShift 4.9 and 4.10. The error still exist after upgrading to version 2.3.1 of the Apicurio Registry.