how to "hot" (re)deploy new WARs ?

[Alessandro de Manzano]

Hello,

I'm not totally sure this is the right place to ask my question, but... how could I update my Java EE app running in my Payara production server without a down ?

It seems to me there is only one solution, using something like JRebel or similar, to hot update class files.

Or am I wrong ? There is a way to deploy a "new" .war/.ear and more or less gracefully "move" app users to it without a real, complete redeploy phase ?

Any hint or suggestion is much welcome !

Many thanks in advance

Ale

[Ondro Mihályi]

Hi,

Solutions like JRebel aren't recommended in production. They aim to help during redeployment to quickly refresh the application after the code changes.

In order to update an application in Payara Server without a downtime, you need to use a cluster of at least 2 instances, session replication turned on and a load balancer in front of Payara Server. A single Payara Server doesn't support running 2 versions of the same application at once so it's not possible to seamlessly update your app with a single server.

What you want to do we call "rolling upgrades" and it's described in detail in this blog: https://blog.payara.fish/payara-server-rolling-upgrades

Note that you only need to be running 2 Payara Servers during an update. Afterwards, you can shut the second server down.

Ondro

--
You received this message because you are subscribed to the Google Groups "Payara Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to payara-forum+unsubscribe@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/payara-forum/ea02d3f7-a864-4164-a238-adeb69850472%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.