Summary: Restarting, shutting down and refreshing containers; viewing a runtime configuration report.
 |
Note: The Start, Stop, Restart/Refresh, Shutdown API operations considered as deprecated since 6.x and will be removed in future releases. These operations are relevant only for a single space which is not running within a ServiceGrid Container. An attempt to shutdown a space which runs within a GSC will cause a new re deployment of another space instance. |
Container Operations There are two ways to perform maintenance operations on a container:
- Selecting a container node (
) in the Grid Tree, then clicking the relevant button on the top toolbar.
- Right-clicking a container node (
) in the Grid Tree, then selecting the relevant operation from the context menu.
Operation |
Description |
Toolbar Button |
Context Menu Command |
Restart Container |
Stops and restarts the container and all the spaces in it. |
 |
Restart |
Shutdown Container |
Stops the container and all the spaces in it and un-registers all the associated proxies from the lookup servers. |
 |
Shutdown |
Refresh Container |
Looks for all registered proxies and re-displays them. |
 |
Refresh |
Runtime Configuration Report It is often useful to know the current configuration of a running container. To view a runtime configuration report for a container:
- In the GigaSpaces Browser, right-click the container node (
). The container context menu is displayed:
- From the menu, select Runtime Configuration Report.
The report is displayed in a new window:
 |
You can also view the GigaSpaces runtime configuration settings by setting the system property -Dcom.gs.env.report=true in the Java command line. Refer to the GigaSpaces Properties List for more details. |
The information displayed includes:
- Space configuration
- Container configuration
- Cluster configuration
- System properties
- System environment and variables
- Java properties
- Network interfaces
- GigaSpaces build or version etc.
|