[SOL-80176] SCSt Binder - Don't prevent app start-up if Broker unavailable #223
Labels
enhancement
New feature or request
tracked
Internally tracked by Solace's internal issue tracking system
It seems that if a Solace binder can not connect to a broker when starting up that it prevents the entire Spring Boot app from starting. In most cases this probably isn't an issue, but in some cases your application will have more than just messaging interfaces and you want your app to start and have it continue to try to connect to the Event Broker afterwards. Note that per a discussion with the Spring team at VMWare this is how Spring AMQP and Kafka work as well.
This task is in relation to this community post: https://solace.community/discussion/1758/spring-cloud-stream-solace-binder-prevents-application-from-running-when-solace-is-down. I think the user found the root of the issue in the message on May 8th in that the connectivity happens in the
@PostConstruct
method of the binder and when that fails the bean is not created.The text was updated successfully, but these errors were encountered: