Skip to Content
Last modified by Pascal Robert on 2023/08/10 22:21
From version 68.1
edited by Pascal Robert
on 2009/08/09 08:24
Change comment: There is no comment for this version
To version 76.1
edited by Pascal Robert
on 2009/08/08 20:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -63,11 +63,11 @@
63 63  
64 64  To get details about the //AjaxExample// application :
65 65  
66 -http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample
66 +http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=app&name=AjaxExample2
67 67  
68 68  And for a specific instance :
69 69  
70 -http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample-1
70 +http:~/~/hostname:56789/cgi-bin/WebObjects/JavaMonitor.woa/admin/info?type=ins&name=AjaxExample2-1
71 71  
72 72  The response for the direct actions will either send a JSON array or YES/NO. For example, the query //info// for all instances will return :
73 73  
... ... @@ -97,17 +97,3 @@
97 97  ///forceQuit// : force quit an application, might be useful to call it from a monitoring system.
98 98  ///stop// : stop an application/instance the normal way.
99 99  ///start// : start an application/instance the normal way.
100 -
101 -=== Automatic archive of SiteConfig.xml ===
102 -
103 -On every change you do to the configuration, a backup of SiteConfig.xml will be done in, by default, /Library/WebObjects/Configuration.
104 -
105 -=== Bounce feature ===
106 -
107 -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 :
108 -
109 -* Find the inactive (eg : not started) instance and start it
110 -* Find the active instances (minus the one started the step below) and enable "Refuse New Session"
111 -* Bounce the active instances when the minimum session count is reached
112 -
113 -This feature, from my understanding, allow you to upload new versions of your app, start up the new version and refuse sessions for the instances running on the older version. I don't know how this will work if your new version use migrations to change your schema (eg : old instances might raise exceptions because of database schema changes), so try it out on a test server before and put your results here.