Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 160.1
edited by simon
on 2010/12/01 07:53
Change comment: There is no comment for this version
To version 166.1
edited by John Huss
on 2011/06/28 20:24
Change comment: clarified bounce behavior

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.simon
1 +XWiki.johnthuss
Content
... ... @@ -14,7 +14,7 @@
14 14  
15 15  You can either download them pre-built from [[Wonder's Hudson build server>>http://webobjects.mdimension.com/hudson/job/Wonder54/lastSuccessfulBuild/artifact/dist/]] or build them from the source code.
16 16  
17 -To build them from the [[Wonder source code>>WONDER:Download Wonder Source, Build, Install and Upgrade]], simply run the following command from the Wonder directory at the root of the Wonder source.
17 +To build them from the [[Wonder source code>>WONDER:Getting the Wonder Source Code]], simply run the following command from the Wonder directory at the root of the Wonder source.
18 18  
19 19  {{code}}
20 20  ant frameworks deployment.tools -Dwonder.patch=54 -Ddeployment.standalone=true
... ... @@ -45,13 +45,14 @@
45 45  
46 46  ==== Simplified/Automated Bouncing ====
47 47  
48 -In the "list instances" page, you get a "Bounce" action link. This action only work if you have at least one active instance and one inactive. What it does is :
48 +In the "list instances" page, you get a "Bounce" action link. This action only work if you have at least one active instance and one inactive instance (only one inactive instance takes part in the bounce). What it does is :
49 49  
50 -* Find the inactive (i.e., not started) instance and start it
50 +* Find one inactive (i.e., not started) instance and start it
51 51  * Find the active instances (minus the one started in the previous step) and enable "Refuse New Session"
52 -* Bounce the active instances when the minimum session count is reached
52 +* Stop the active instances that are refusing new sessions when the minimum session count is reached
53 +* Restart all but one of the instances that were just stopped and turn on "Auto-Recover"
53 53  
54 -This feature, from Pascal's understanding, allows you to upload new versions of your application, start up the new version and refuse sessions for the instances running on the older version.
55 +This feature, from Pascal's understanding, allows you to upload new versions of your application, start up the new version and refuse sessions for the instances running on the older version.  This is designed to work so that you always have just **one** inactive instance that is only used while the bounce is performed.  While waiting for the existing sessions to end you will have only one instance of your app accepting new sessions; you need to determine if this is acceptable for your app or not.
55 55  
56 56  {{warning title="Database Changes"}}
57 57  
... ... @@ -236,4 +236,4 @@
236 236  
237 237  === Troubleshooting ===
238 238  
239 -If JavaMonitor did not start on your fresh install of WebObjects, check out the WOTaskd Didn't Start question in the troubleshooting section.
240 +If JavaMonitor won't start up check the [[troubleshooting deployment>>WO:Troubleshooting Deployment]] section. In particular pay attention to the [[WOTaskd Didn't Start>>WO:Troubleshooting Deployment]] Q&A.