I have an application that uses Camel Netty4 component as a consumer
endpoint which is configured as a TCP client (clientMode set to true) with
the reconnect option enabled. The reconnect feature works well, the TCP
connection automatically reconnects to the remote server after a network
outage. Unfortunately it seems that this reconnect behavior runs
indefinitely until the connection is established. Is there some way to set
a limit to this reconnect feature, i.e. put a limit on how many reconnect
attempts can be made before throwing a connection error?

Another question but this one is for the Netty4 component implemented as a
producer that sends a payload to a remote server. Is there a way to
configure the endpoint to enable the reconnect feature which would allow
the TCP client to try establish a connection for a number of attempts
before throwing a connection error?

Thanks in advance!

Reply via email to