CWWKV

CWWKV0000I: The DynamicRouting MBean is available.
CWWKV0001I: The DynamicRouting MBean has been deactivated.
CWWKV0002W: Error adding connector information to collective repository for server {0}. Generated plugin configuration files will not include this connector.
CWWKV0003W: Error removing connector information from collective repository for server {0}. Generated plugin configuration files will include this connector, although it will not route.
CWWKV0004W: Error reading REST endpoint connector information for server {0}. Generated plugin configuration files will not include this connector.
CWWKV0005W: Error writing REST endpoint connector information to collective repository for server {0}. Generated plugin configuration files will not include this connector.
CWWKV0006W: Error reading REST endpoint connector information for server {0}. This server will not be included in the generated plugin configuration files.
CWWKV0007I: The WebSphere plug-in configuration files have been successfully generated.
CWWKV0008W: Dynamic Routing service sent 307 response to the client {0} because {1}.
CWWKV0009E: Exception occurred while handling POST request from the client {0} : {1}
CWWKV0010I: A routing information change event of type {0} was received for routing artifact of type {0}.
CWWKV0011W: The non-default plugin trace specification {0} does not specify a condition. The trace specification will match all requests.
CWWKV0012I: dumpPOSTResponse finished with output : {0}
CWWKV0013E: Error occurred while dumping POST response : {0}
CWWKV0014W: Dumping POST response to server log because the DynamicRouting MBean could not dump to {0} due to {1}.
CWWKV0015E: The number of destination end point parameters specified for the routing rule end point {0} is not correct. The parameters for permit type {1} must be "collective,cluster". This end point will be discarded.
CWWKV0016E: The number of destination end point parameters specified for the routing rule end point {0} is not correct. The parameters for permit type {1} must be "collective,host,server directory,server name". This end point will be discarded.
CWWKV0017E: The number of destination end point parameters specified for the routing rule end point {0} is not correct. The parameters for permit type {1} must be "collective,application name,module name". This end point will be discarded.
CWWKV0018E: Permit routing rule destination end point {0} contains an invalid end point type {1}. Only {2} are valid destination end point types. This end point will be discarded.
CWWKV0019E: Permit routing rule destination end point {0} is not formatted correctly. The format for a routing rule destination end point is "type=parm1,parm2,...". No end point type was be determined so the end point will be discarded and not considered for this routing rule.
CWWKV0020E: Authentication to the Dynamic Routing REST service uses the admin role.
CWWKV0021E: The match expression {1} for the {0} web server did not validate correctly and will be ignored.
CWWKV0022E: For Dynamic Routing routing rule associated with web server {0}, with matchExpression {1}, the rule Order attribute value {2} has been used previously. The rule is skipped.
CWWKV0023E: A Dynamic Routing PERMIT routing rule does not contain any specified endpoint sets. The rule associated with web server {0}, with matchExpression {1} and rule Order attribute value {2} will be skipped.
CWWKV0024E: A Dynamic Routing PERMIT routing rule contains an endpoint set without an endpoint. The rule associated with web server {0}, with matchExpression {1} and rule Order attribute value {2} will be skipped.
CWWKV0025E: A Dynamic Routing routing rule does not contain a valid rule action. The rule associated with web server {0}, with matchExpression {1} and rule Order attribute value {2} will be skipped.
CWWKV0026E: The web server with name {0} was specified previously with attribute value for overrideAffinty = {1}. Another specification for the same web server uses value {2}. All rules for web server {0} are skipped.
CWWKV0027W: The overrideAffinity attribute value for the {0} web server differs from the value for the shared web server routing rules. For the {0} web server, overrideAffinity will use the value {1}.
CWWKV0028E: The match expression validation failed syntax checking with the following tokens remaining: {0}. Check the syntax for improperly formatted match expressions.
CWWKV0100I: The ScalingController feature is activated.
CWWKV0101I: The ScalingController feature is deactivated.
CWWKV0102I: This server is elected to be the primary scaling controller.
CWWKV0103I: This server no longer is the primary scaling controller.
CWWKV0104E: An internal error has occurred. The "<{0}>" element is not present in the configuration: {1}. The missing "<{0}>" element will be ignored.
CWWKV0105E: The configuration of the default scaling policy is in error. The setting of min={1} and max={2} in the "<{0}>" element is not correct. The "<{0}>" element will be ignored.
CWWKV0106E: The configuration of scaling policy {0} is in error. The setting of min={2} and max={3} in the "<{1}>" element is not correct. The "<{1}>" element will be ignored.
CWWKV0107E: The scaling controller encountered an exception while processing collective data. The exception stack trace follows: {0}
CWWKV0108E: The scaling controller cannot start server {0}. The server command MBean is not available.
CWWKV0109E: The scaling controller cannot stop server {0}. The server command MBean is not available.
CWWKV0110I: The scaling controller is stopping server {0} in user directory {1} on host {2} to meet the maximum instances for cluster {3}.
CWWKV0111I: The scaling controller is starting server {0} in user directory {1} on host {2} to meet the minimum instances for cluster {3}.
CWWKV0112I: The scaling controller has successfully started server {0} on host {1}.
CWWKV0113I: The scaling controller is starting server {0} in user directory {1} on host {2} to increase capacity in cluster {3}. The average {4} utilization in the cluster is {5} percent.
CWWKV0114I: The scaling controller has successfully stopped server {0} on host {1}.
CWWKV0115I: The scaling controller is stopping server {0} in user directory {1} on host {2} to reduce capacity in cluster {3}.
CWWKV0116W: Multiple scaling policies {0} are bound to the cluster pattern {1}. The scaling controller is using the scaling policy named {2}.
CWWKV0117E: The scaling controller was unsuccessful in an attempt to start server {0} on host {1}. Return code: {2} Standard output: {3} Standard error: {4}
CWWKV0118E: The scaling controller was unsuccessful in an attempt to start server {0} on host {1}. The exception is "{2}".
CWWKV0119E: The scaling controller was unsuccessful in an attempt to stop server {0} on host {1}. Return code: {2} Standard output: {3} Standard error: {4}
CWWKV0120E: The scaling controller was unsuccessful in an attempt to stop server {0} on host {1}. The exception is "{2}".
CWWKV0121I: The server {0} in user directory {1} on host {2} has been defined as a scaling member in cluster {3}.
CWWKV0122I: The server {0} in user directory {1} on host {2} has been removed as a scaling member in cluster {3}.
CWWKV0123E: Duplicate host singleton leaders have been detected on host {0}. This condition may degrade scaling controller decisions. The leader identity of server {1} is {2}. The leader identity of server {3} is {4}.
CWWKV0124I: The shared configuration file {0} for cluster {1} has been deleted. This action was taken because cluster {1} is no longer being managed by this scaling controller.
CWWKV0125I: The scaling controller did not start server {0} on host {1} because the server is already running.
CWWKV0126W: The configuration of scaling policy {0} does not contain a min or max metric threshold.
CWWKV0127W: The configuration of scaling policy {0} does not contain a max metric threshold.
CWWKV0128W: The configuration of scaling policy {0} does not contain a min metric threshold.
CWWKV0129I: The scaling controller is starting server {0} in user directory {1} on host {2} as a replacement for server {3} on host {4}.
CWWKV0130I: The scaling controller did not stop server {0} on host {1} because the server is already stopped.
CWWKV0131I: The scaling listener SPI plugin selected its own candidates for the pending {0} action.
CWWKV0131W: ScalingStackProvisioner failed to provision a host for stack group {0} because a bad stack parameter was specified.
CWWKV0132W: ScalingStackProvisioner failed to provision a host for stack group {0} because the controller was unable to open the zip file for the stack group.
CWWKV0133E: ScalingStackProvisioner failed to provision a host for stack group {0} because of a file transfer error.
CWWKV0133I: The scaling listener SPI plugin agreed with the {0} action suggested by the scaling controller.
CWWKV0134E: ScalingStackProvisioner failed to provision a host for stack group {0} because of an unexpected exception.
CWWKV0134I: The scaling listener SPI plugin elected to handle the pending {0} action. No further action will be taken by the scaling controller.
CWWKV0134W: The following targets provided by the scaling listener SPI plugin cannot be found and thus will not be considered for the {0} action: {1}.
CWWKV0135I: The scaling listener SPI plugin has been activated on the scaling controller.
CWWKV0136I: The scaling listener SPI plugin has been deactivated on the scaling controller.
CWWKV0137W: The scaling listener SPI plugin refined the candidates list for the pending action {0}, but selected candidates are not valid.
CWWKV0138W: The scaling listener SPI plugin returned an invalid return type of 'null'.
CWWKV0139W: The scaling listener SPI plugin specified an invalid scaling decision duration of {0}. A duration of 0 will be used instead.
CWWKV0140W: The scaling listener SPI plugin request timed out. The time limit of {0} seconds elapsed with no response from the scaling listener SPI plugin. The scaling controller will take a default action.
CWWKV0141E: An exception was caught during a call to the scaling listener SPI plugin: {0}.
CWWKV0200I: The ScalingMember feature is activated.
CWWKV0201I: The ScalingMember feature is deactivated.
CWWKV0202E: The collective singleton service, {0}, is not behaving as expected.
CWWKV0203I: Server {0} is elected as the host leader.
CWWKV0204I: Server {0} is no longer the host leader.
CWWKV0205I: The host leader for this server is {0}.
CWWKV0206E: An error occurred while trying to identify the scaling controller leader. Exception information: {0}
CWWKV0207I: Unable to find the identity of the scaling controller leader.
CWWKV0208W: The shared configuration service is not available on the collective controller. The metadata file {0} will not be published.
CWWKV0300I: The StackManager service started.
CWWKV0301I: The StackManager service stopped.
CWWKV0302I: The existing stacks are {0}
CWWKV0303I: Stack group {0} changed.
CWWKV0304W: Stack group {0} does not exist.
CWWKV0305I: Value {0} was assigned for deploy variable {1} during the stack deployment.
CWWKV0306E: The deploy stack cannot update the deploy variables for stack {0} into the collective repository. Cause: {1}.
CWWKV0307W: Stack {0} does not exist.
CWWKV0308W: Installable {0} does not exist.
CWWKV0309I: New stack {0} was added.
CWWKV0310I: Stack {0} was removed.
CWWKV0311I: Stack {0} changed.
CWWKV0312W: Cannot update the cluster name for the {0} stack. Deployed cluster members already exist.
CWWKV0401I: Intelligent management has successfully provisioned and started a new server instance ({0}) on host {1} in response to a scale out command.
CWWKV0402E: Intelligent management has encountered an error ({0}) while trying to provision and start a new server on host in response to a scale out command.
CWWKV0403I: The scaling controller cannot meet the minimum instances for cluster {0} because it cannot find a host with the capacity to add a server.
CWWKV0404I: The scaling controller cannot increase the number of servers in cluster {0} because it cannot find a host with the capacity to add a server.
CWWKV0405I: The scaling controller cannot meet the minimum instances for cluster {0} because too few scaling members are defined.
CWWKV0406I: The scaling controller cannot perform the request at this time.
CWWKV0407I: The scaling controller cannot increase the number of servers in cluster {0} because too few scaling members are defined.
CWWKV0408E: The {0} metric for the {1} scope is not supported on this operating system.
CWWKV0600I: The HealthManager feature is activated.
CWWKV0601I: The health condition {0} provided in {1} is registered.
CWWKV0602I: The health condition plugin {0} is activated.
CWWKV0603I: The health condition {0} is being monitored on target {1}.
CWWKV0604I: The health condition {0} is no longer being monitored on target {1}.
CWWKV0605I: The health condition {0} on target {1} now has a status of {2}.
CWWKV0607I: The health policy {0} is activated for {1}.
CWWKV0608I: The health actions for policy {0} are invoked for {1}.
CWWKV0609I: The health policy {0} is added.
CWWKV0610I: The health policy {0} is removed.
CWWKV0611I: The health policy {0} is deactivated for {1}.
CWWKV0612I: The Health Analyzer is activated in {0}.
CWWKV0613I: The {0} health policy has an invalid target.
CWWKV0614I: The {0} condition specified in the {1} health policy is invalid or not ready yet.
CWWKV0615I: The {0} action specified in the {1} health policy is invalid or not ready yet.
CWWKV0616E: The {0} health policy has an invalid target of type {1}. The target is missing a value for attribute {2}.
CWWKV0700I: The health action {0} provided in {1} is registered.
CWWKV0701I: Server {0} cannot be restarted, because the restart process is prohibited at this time.
CWWKV0702I: Server {0} cannot be restarted when the node is in maintenance mode.
CWWKV0703I: Server {0} was restarted successfully.
CWWKV0704E: Server {0} failed to restart with the following exception {1}.
CWWKV0705I: Java heap dump for Server {0} was successfully generated.
CWWKV0706E: The heap dump failed for server {0} with the following exception {1}.
CWWKV0707I: Java thread dump for Server {0} was successfully generated.
CWWKV0708E: The thread dump operation failed for server {0} with the following exception {1}.
CWWKV0709I: The health action plugin, {0}, has been activated.
CWWKV0710E: Server {0} failed to set to maintenance mode.
CWWKV0710I: Server {0} was successfully set to maintenance mode.
CWWKV0711E: Server {0} failed to unset maintenance mode.
CWWKV0711I: Server {0} successfully unset maintenance mode.
CWWKV0712E: The health action {0} provided in {1} has failed to execute.
CWWKV0712I: The {0} health action in {1} finished running.
CWWKV0713E: The status of health action with id {0} was not found by the Health Action Manager.
CWWKV0714E: The health action with id {0} was not found by the Health Action Manager and could not be cancelled.
CWWKV0715E: Check the messages for action results; the health action failed with return code {0}.
CWWKV0750I: The HealthAnalyzer feature has been activated.
CWWKV0751I: The health analyzer server {0} has been elected as the leader.
CWWKV0752I: The Memory Usage health condition analyzer has been activated.
CWWKV0753I: The Memory Leak health condition analyzer has been activated.