Heartbeat mechanism with Smallrye AMQP connector about quarkus

[quarkus-bot]

/cc @Ladicek (smallrye), @jmartisk (smallrye), @phillip-kruger (smallrye), @radcortez (smallrye)

[mnguetsa]

@geoand @cescoffier Any idea how I could do this? 😬

[geoand]

cc @ozangunalp

[cescoffier]

No, except modifying the AMQP client options, I do not see another approach.

I would disable the health check and implement a custom one instead.

[mnguetsa]

No, except modifying the AMQP client options, I do not see another approach.

I would disable the health check and implement a custom one instead.

Hi @cescoffier
I tried modifying the clients options too. But I realized setTcpKeepAlive(true) had no effect on keeping the connection. Or is there another option I missed in the AMQP client options? So far this is what I did with the AMQP client Options:

@ApplicationScoped
public class AmqpConfigurationProvider {
  @ConfigProperty(name = "amqp-port")
  int port;

  @ConfigProperty(name = "amqp-use-ssl")
  boolean useSsl;

  @Produces
  @Identifier("custom-amqp-client-options")
  public AmqpClientOptions getNamedOptions() {
    return new AmqpClientOptions().setTcpKeepAlive(true).setPort(port).setSsl(useSsl);
  }
}

I would use the health check deactivation as last solution. If you know another AMQP option I can try please let me know.
Thanks a lot

[cescoffier]

Which broker are you using? Do they use an idle timeout? Could you potentially send fake frames regularly to keep it open?

[ozangunalp]

I think AMQP 1.0 broker in Azure (I don't remember the product name) had a similar behaviour.

[ozangunalp]

Probably, you are sending the TCP keep-alive but the server doesn't respect it and closes the connection anyway.

[cescoffier]

Cloud-based broker tends to cut connections quickly if there are no L7 frames.