Changes for page Wonder JavaMonitor and wotaskd
Last modified by Pascal Robert on 2023/08/10 22:21
From version 162.1
edited by simon
on 2010/12/01 07:44
on 2010/12/01 07:44
Change comment:
There is no comment for this version
To version 168.1
edited by Pascal Robert
on 2012/02/11 08:42
on 2012/02/11 08:42
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. simon1 +XWiki.probert - Content
-
... ... @@ -12,12 +12,12 @@ 12 12 13 13 === Where To Get Them === 14 14 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.15 +You can either download them pre-built from [[Wonder's Jenkins build server>>http://jenkins.wocommunity.org/job/Wonder/lastSuccessfulBuild/]] or build them from the source code. 16 16 17 -To build them from the [[Wonder source code>>WONDER: DownloadWonder 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 -ant frameworks deployment.tools -D wonder.patch=54 -Ddeployment.standalone=true20 +ant frameworks deployment.tools -Ddeployment.standalone=true 21 21 {{/code}} 22 22 23 23 {{info title="What this command does:"}} ... ... @@ -25,7 +25,6 @@ 25 25 * *ant*: calls Apache Ant. It is assumed that you have this already installed. 26 26 * *frameworks*: tells Ant to build the "frameworks" target. This may not be needed if you already have Wonder built and installed in a location Ant can find automatically. 27 27 * *deployment.tools*: tells Ant to build the "deployment.tools" target. This is the target that builds both wotaskd.woa and JavaMonitor.woa. You absolutely need this one. 28 -* *\-Dwonder.patch=54*: tells Wonder to build for WebObjects version 5.4. You need this if you are building against Wonder Trunk. Some branches don't need it, but it doesn't hurt either. 29 29 * *\-Ddeployment.standalone=true*: argument will embed the required Wonder and WebObjects frameworks in built applications. You need this to ensure that the required frameworks are embedded in the built applications. 30 30 31 31 {{/info}} ... ... @@ -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 : 47 +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 it49 +* 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 51 +* Stop the active instances that are refusing new sessions when the minimum session count is reached 52 +* 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. 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. 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 ... ... @@ -220,14 +220,20 @@ 220 220 221 221 {{/code}} 222 222 223 -{{code title="Delete an Instance :"}}223 +{{code title="Delete an Instance"}} 224 224 225 225 curl -X GET http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mApplications/AjaxExample/deleteInstance?id=1 226 226 227 227 {{/code}} 228 228 229 -{{code title=" Addinga NewInstance"}}229 +{{code title="Configuring the Site"}} 230 230 231 231 curl -X PUT -d "{woAdaptor:'www.mydomain.com'}" http://monitorhost:port/cgi-bin/WebObjects/JavaMonitor.woa/ra/mSiteConfig.json 232 232 233 233 {{/code}} 234 + 235 +Note that before configuring the site you must first add a host. If you attempt to configure the site prior to adding a host you will get an InvalidStateException. 236 + 237 +=== Troubleshooting === 238 + 239 +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.