Clustered / Versioned applications cannot be enabled on individual cluster instances

[lprimak]

Regression from GlassFish 3.1.2.2
This is an upstream bug: https://java.net/jira/browse/GLASSFISH-21198

[smillidge]

I am seeing subtly different behaviour.

If I have a cluster test-cluster with two instances test1c test2c

If I have two versions of an application deployed.
app:1.0
app:2.0

deployed initially using

asadmin deploy --target test-cluster  -name app:1.0 app.war
asadmin deploy --target test-cluster --enabled false -name app:2.0 app.war

The version 1.0 application is available from both nodes.

If I then do

asadmin enable --target test1c app:2.0

The application is accessible on test1c but a 404 is given for test2c

If i then do

asadmin enable --target test2c app:2.0

The application is again available on both nodes.

[smillidge]

My understanding is that when the 2.0 version is enabled on test1c the 1.0 version should remain available on test2c.

[lprimak]

Sorry, I misread your comments above. The above is the exact behavior I am seeing as well,
which is the issue at hand. It doesn't matter what the version string looks like.
Right now, it's impossible to do rolling upgrades on GF 4.1

Thank you for looking at this issue.

[ratcashdev]

#270 is pretty much a duplicate as far as clusters as concerned, although it would not be bad if rolling updates would work on a standalone instance as well.

[lprimak]

Rolling upgrades work on GF 4.1 right now with standalone instances, just not with clusters. I don't see a reason why it wouldn't work the same with Payara.

On Sep 9, 2015, at 9:33 AM, ratcash notifications@github.com wrote:

#270 is pretty much a duplicate as far as clusters as concerned, although it would not be bad if rolling updates would work on a standalone instance as well.

—
Reply to this email directly or view it on GitHub.

[ratcashdev]

If that's true (somehow I could not achieve it, but will try again following the process outlined by @smillidge without the 'target' option) then #270 could be simply closed. Will post back with my results.

[smillidge]

Standalone instances and versioned apps should work fine on Payara. In fact configuring standalone instances with Hazelcast web session clustering across the instances, by specifying the same Hazelcast configuration will also give HA web sessions similar to a "cluster". So full HA rolling updates are possible with standalone instances.

Problem is only cluster related as the version is disabled across all cluster instances rather than just the target cluster instance.

[ratcashdev]

Checked in 4.1.153. I can confirm, rolling updates in standalone instance works. #270 can be closed.