Use Java™ virtual
machine (JVM) properties to configure how your container server reconnects
to the data grid if the container server becomes disconnected.
JVM system properties
If a container server becomes disconnected from the data
grid,
WebSphere® eXtreme Scale attempts
to reconnect those container servers. By setting system properties,
you can control how the container reconnect functionality performs.
You can set these properties when you start a container server. Some
of the properties are applicable to
WebSphere eXtreme Scale in a stand-alone environment,
while others are only applicable when starting a container server
for
WebSphere eXtreme Scale for
WebSphere Application Server. For example, when starting
a container server for
WebSphere eXtreme Scale in
a stand-alone environment, you can set these properties as an option
from the command line:
startOgServer.sh server01 -objectgridFile
objectgrid.xml -deploymentPolicyFile deployment.xml -Dcom.ibm.websphere.objectgrid.container.reconnect.restart=false
startXsServer.sh server01 -objectgridFile
objectgrid.xml -deploymentPolicyFile deployment.xml -Dcom.ibm.websphere.objectgrid.container.reconnect.restart=false
For
more information, see Starting and stopping stand-alone servers. If
you want to set the appropriate property for WebSphere eXtreme Scale for WebSphere Application Server, you can use the WebSphere Integrated Solutions
Console tool. This tool is a graphical user interface that resides
on the WebSphere Application Server environment,
and is installed as an extension to the WebSphere ISC.
- com.ibm.websphere.objectgrid.container.reconnect.block.reconnect.time
- Defines the amount of time (in milliseconds) to block another
container reconnect call. Only valid when a container server is started
for the product offering:WebSphere eXtreme Scale for WebSphere Application Server.
Default: 30000
milliseconds
- com.ibm.websphere.objectgrid.container.reconnect.min.successful.heartbeats
- Defines the minimum number of successful heartbeats before a container
can be stopped. Only valid when a container server is started for
the product offering: WebSphere eXtreme Scale for WebSphere Application Server.
Default: 10
- com.ibm.websphere.objectgrid.container.reconnect.restart
- Defines whether container reconnect can restart the JVM. Only
valid when a container server is started for WebSphere eXtreme Scale in a stand-alone environment.
Default: true
- com.ibm.websphere.objectgrid.container.reconnect.restart.delay
- Defines the time (in milliseconds) to delay after parent death
before proceeding with startup on the newly created child container
when restarting the JVM. Only valid when a container server is started
for the product offering: WebSphere eXtreme Scale in
a stand-alone environment.
Default: 2000 milliseconds
- com.ibm.websphere.objectgrid.container.reconnect.restart.parent.timeout
- Defines the time (in milliseconds) for the newly created child
container to wait for parent death before timing out when restarting
the JVM. Only valid when a container server is started for the product
offering: WebSphere eXtreme Scale in a
stand-alone environment.
Default: 180000 milliseconds
- com.ibm.websphere.objectgrid.container.reconnect.retry.forever
- Defines whether the container retries container reconnect forever.
Only valid when a container server is started for the product offering:WebSphere eXtreme Scale for WebSphere Application Server.
Default: false