Re: HotDeploy
Re: HotDeploy
- Subject: Re: HotDeploy
- From: Stefan Klein <email@hidden>
- Date: Wed, 04 May 2011 22:54:51 +0200
Am 04.05.11 22:36, schrieb Pascal Robert:
Le 2011-05-04 à 16:31, Stefan Klein a écrit :
There is one pitfall: If you changed the database shema, EOModel and use ERXMigration (what have I done without?)
Yes, that can be a problem. Not bad if you are only adding columns, but if removed columns or adding constraints, when people in the "old" instances save data, it might blow at the database level.
Adding colums might be also a problem if you add default values via
awakeFromInsertion().
Stefan
Am 04.05.11 22:25, schrieb Pascal Robert:
Le 2011-05-04 à 16:17, Jesse Tayler a écrit :
oh!
is that what bounce does?
well then!
so,
1 press bounce
2 deploy new files
2 is press bounce, 1 is deploy new files
3 wait for new instances to come up
The bounce action will start any inactive instances. So you have one running instance and one idle, and when you "bounce" the already running instance go under "refuse new sessions" mode (so current users can finish their work) and the idle instance kicks off with the new code.
so, new instances have the new files and existing instance sessions reliably run on old files?
Yes, the new instances have to start from another bundle. So say "old" instances runs on /opt/MyApp.woa.20110101 and the "new" instances runs on /opt/MyApp.woa.20110504
On May 4, 2011, at 4:08 PM, Pascal Robert wrote:
Le 2011-05-04 à 16:00, Daniel Mejia a écrit :
Hi,
I have a question regarding the deploy. Is it possible to redeploy an application when the application is running, or I need to shutdown every instance, deploy the application and restart every instance?
You will have classpath issues when doing that. It's better to use the "Bounce" feature of Monitor, which put the "old" app in "refuse new sessions" mode and start new instances with the new code. _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden