> is that what bounce does?
No.
What bounce does is look at the # of instances, start a number of instances on
each server, then set all other minus the number of instances started to refuse
and schedule, so that they shutdown after a while and restart. The net effect
is that you have the sam
The general (there are variations) approach used by people for small
deployments (a few manageable instances) are:
1) Deploy new embedded Application and embedded WebServer Resources bundles
with unique versioned bundle names (IIRC you can set this in build.app.name in
project properties in Ecl
Thank you very much,
I'm going to try this solution tonight.
regards,
Daniel.
On 04/05/2011, at 15:25, Pascal Robert wrote:
>
> 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 file
So, add the same default to the column as in awakeFromInsertion.
It can always be removed again after all rollout of new version is done (aka
all old instances are dead)
On May 4, 2011, at 4:54 PM, Stefan Klein wrote:
> Am 04.05.11 22:36, schrieb Pascal Robert:
>> Le 2011-05-04 à 16:31, Stefan
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
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 t
There is one pitfall: If you changed the database shema, EOModel and use
ERXMigration (what have I done without?)
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
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 ha
One simple thing that works for the most part is to install the app into a
new "versioned" directory and use a sym-link to point to the production
version. Then you can just change the sym-link and restart the instances
one by one. This results in many fewer problems than overwriting the files
us
oh!
is that what bounce does?
well then!
so,
1 press bounce
2 deploy new files
3 wait for new instances to come up
so, new instances have the new files and existing instance sessions reliably
run on old files?
On May 4, 2011, at 4:08 PM, Pascal Robert wrote:
>
> Le 2011-05-04 à 16:00,
you mean deploy like write over the files while the app is running?
the best thing is to have two sets of apps so you can wind down instances on
one, update the files, restart and the other etc.
but of course, there's all kinds of complications.
that all said, in less than critical situations,
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 issue
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?
Regards,
Daniel.
___
Do not post admin
13 matches
Mail list logo
