Thanks Alexis, yes rolling upgrade can achieve application upgrade
without loss of service. We actually also have rolling upgrade feature
in the prior releases (e.g. v2.1), but the new application versioning
feature which was added in 3.1 has simplified the rolling upgrade steps.
- Hong
On 5/24/2011 3:45 PM, Alexis Moussine-Pouchkine wrote:
> Salut,
>
> I'll let the deployment experts chime in but pre-GlassFish 3.1, redeployment of applications usually involves having the application to be unavailable for a (rather short) period of time which users possible experiencing 404's or 503's (IIRC).
>
> Now, starting with GlassFish 3.1 we have a new feature called "Application versioning" which enables you to deploy a new version in disabled mode and switch to that new version by simply enabling it, thus cutting down on the upload and deployment time. Check out this documentation section for more details - http://download.oracle.com/docs/cd/E18930_01/html/821-2426/abdik.html
>
> -Alexis
>
>
> On 23 mai 2011, at 09:24, Yannick Eyebe wrote:
>
>
>> Hi,
>> I have some questions about hot redeployment in glassfish.
>> while hot redeploying an application in glassfish server(without stop and restart glassfish server)
>>
>> 1-Does the application is still available for current users?
>> 2-what going to happen when a user logs on , while making a hot redeployment of the application?Is the user request blocked before momentarily to be written after the new version of the application ? what happens really? can I have a document that explains it clearly with a diagram and explaination of this diagram?
>>
>>
>>
>
>