Thanks for the info. I'll check it out.
Mike
--
View this message in context:
http://karaf.922171.n3.nabble.com/Is-there-an-upgrade-process-for-Karaf-4-1-0-to-4-1-1-tp4050010p4050053.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Many people use the karaf-maven-plugin to create a custom distro that can
define the boot features (karaf ones as well as your own) as well as
changes to configs.
If you do this in your build or deployment pipeline then upgrading to a new
karaf version is mainly changing the karaf version to the
I have a test bed with a master / slave cluster setup for Artemis each node
is on different Karaf instance and using a replicated persistence model. I
guess I can give it a try under load to see if this will function as an
upgrade model.
I'm not using the Karaf cluster options only the Artemis
I guess you don't have several servers with load balancing. So, would it be
possible to start a temporary server which will replace the main one, then
upgrade the main one and replace back the temporary one?
JP
-Message d'origine-
De : mtod09 [mailto:m...@thetods.net]
Envoyé :
That does not sound like a good approach for a production system. If I have
to rebuild for every new version of Karaf it would cause a big disruption in
production. I would have to stop all inbound messaging then drain all the
persisted messages before I could cut over to a new system. Not to
You can try to copy over the etc dir but you will have to reinstall you
feature repos and features unless you set them as boot features.
Christian
On 04.04.2017 15:02, mtod09 wrote:
Anyone have a process I would like to upgrade without having reinstall
everything?
--
View this message in
Anyone have a process I would like to upgrade without having reinstall
everything?
--
View this message in context:
http://karaf.922171.n3.nabble.com/Is-there-an-upgrade-process-for-Karaf-4-1-0-to-4-1-1-tp4050010p4050025.html
Sent from the Karaf - User mailing list archive at Nabble.com.
