Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SOL-80176] SCSt Binder - Don't prevent app start-up if Broker unavailable #223

Open
Mrc0113 opened this issue May 9, 2023 · 0 comments
Labels
enhancement New feature or request tracked Internally tracked by Solace's internal issue tracking system

Comments

@Mrc0113
Copy link
Contributor

Mrc0113 commented May 9, 2023

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.

@Nephery Nephery added the enhancement New feature or request label May 10, 2023
@Nephery Nephery added the tracked Internally tracked by Solace's internal issue tracking system label Jun 15, 2023
@Nephery Nephery changed the title SCSt Binder - Don't prevent app start-up if Broker unavailable [SOL-80176] SCSt Binder - Don't prevent app start-up if Broker unavailable Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tracked Internally tracked by Solace's internal issue tracking system
Projects
None yet
Development

No branches or pull requests

2 participants