Make it possible to don't startup service bindings automatically
Issue
it is not possible to startup the application in 'passive mode'. This is a showstopper for us as there is currently no way for us to restart our servers without closing down our entire system.
We plan to handle our software updates as rolling upgrades, where we let the LBs direct all incoming requests to one of the servers in the cluster while we upgrade the other one. This way we can isolate the server being upgraded from part of the incoming events, but not from all of them. We are also receiving JMS events as well as events from our schedulers. Our A-MQ servers are running as network brokers, distributing incoming events to consumers on both servers.
We have to be able to isolate one server at a time from all new events and let it complete any ongoing requests before updating it. We can stop the critical bindings using JMX, but the problem is that they will become active again when the new software is deployed. It can lead to serious problems if we receive new events before all services are started.
We found this fix, which seems to be a limited change.
https://issues.jboss.org/browse/SWITCHYARD-2580
Would it be possible to get a patch with this fix? We would at least need the possibility to control 'activeness' on global level at startup with for example a system property. We would really need it asap so we can complete our deployment procedures. If this is not possible, we will need an alternative workaround.
Environment
Red Hat JBoss Fuse Service Works 6.0.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
