You can use the administrative console to control the maximum
amount of heap memory that is available for the underlying core group
transport to allocate.
About this task
New feature: This topic
references one or more of the application server log files. Beginning
in WebSphere Application Server Version 8.0 you can configure the
server to use the High Performance Extensible Logging (HPEL) log and
trace infrastructure instead of using
SystemOut.log ,
SystemErr.log,
trace.log,
and
activity.log files or native z/OS logging
facilities. If you are using HPEL, you can access all of your log
and trace information using the LogViewer command-line tool from your
server profile bin directory. See the information about using HPEL
to troubleshoot applications for more information on using HPEL.
newfeat
The high availability manager consumes its allocated heap memory
when it sends interprocess messages on behalf of other services that
use the high availability manager functionality. For example, the
heap memory might be consumed while sending memory-to-memory replication
data, or highly available routing data from one core group member
to another core group member.
The value that you specify for
the Transport memory size property acts as a flow control mechanism
that might affect the speed at which data is replicated or the speed
at which routing data is made available to other core group members.
Therefore, you might want to perform this task if you are seeing
large numbers of any of the following Distribution and Consistency
Services (DCS) congestion messages in your
SystemOut.log file:
DCSV1051W, a high severity congestion event for outgoing messages
DCSV1052W, a medium severity congestion event for outgoing messages
DCSV1054W, a medium severity congestion event for incoming messages
Under extreme workloads, these messages might still occur
on a properly tuned system.
Mixed-version environment: If you are running in a mixed cell environment, you must continue
to use the following two memory configuration attributes to configuring
core group memory utilization for the Version 6.x cells:
- The Transport buffer size property, which is set for each individual
core group member. To specify a value for this property, in the administrative
console, navigate one of the following paths:
- If the core group member is an application server, click server_name .
- If the core group member is a node agent, click node_agent_name .
- If the core group member is a deployment manager, click .
- The IBM_CS_DATASTACK_MEG custom property. To specify a value for
this custom property, in the administrative console, click core_group_name .
mixv
To change the amount of memory that is available for
in-flight messages and network communication buffers, complete the
following steps: