Hi, Matej,
Thank you for your efforts. You have it _almost_ exactly right. The key piece missing is that the app must be deployed with a *different* name.
For example, with my proposed changes, this works:
{code:java}
testapp..20160120.war
{code}
and
{code:java}
testapp..20160125.war
{code}
As I stated before, the reason for this is that when using centralized management on Payara (and I believe it works exactly the same way on JBoss/WildFly) you cannot deploy two applications with the same name at the same time to the same management domain.
On GlassFish, I get this error, for obvious reasons:
{code}
$ gfadmin list-applications
my-website <ejb, web services, web>
$ gfadmin deploy --name my-website my-website.war
remote failure: Error occurred during deployment: Application my-website is already deployed on other targets. Please use create-application-ref command to create application reference on target server. Please see server.log for more details.
Command deploy failed.
{code} \
So, in order for managed rolling application upgrades to work, there needs to be ability to deploy the application with *different* names and have them use the same session.
This is what this patch is all about.
|
