Explanation | WebSphere Application Server has started the core group bridge service. |
Action | No user action required. |
Explanation | WebSphere Application Server has started the subscription router for the core group bridge service. |
Action | No user action required. |
Explanation | WebSphere Application Server has stopped the core group bridge service. |
Action | No user action required. |
Explanation | WebSphere Application Server has stopped the subscription router for the core group bridge service. |
Action | No user action required. |
Explanation | The core group bridge service is configured for communication between the connected core groups. The availability status of all of the servers defined in each core group is now shared among all of the connected core groups. |
Action | No user action required. |
Explanation | The core group bridge service is using the specified port (DCS endpoint) to listen for Distribution and Consistency Services (DCS) mesages. |
Action | No user action required. |
Explanation | Lists the available bridges that a core group bridge service can use to establish communication between connected core groups. |
Action | No user action required. |
Explanation | A core group bridge server in an access point group has started or stopped and state information is in the process of being redistributed. |
Action | No user action required. |
Explanation | Core group bridges from the peer access point's cell are not allowed to post information to this cell. These bridges are allowed to read from this cell. |
Action | No user action required. |
Explanation | The connecting server specified the correct access point group, which enabled it to connect. |
Action | No user action required. |
Explanation | The inbound chain used to handle HTTP and HTTPS core group bridge messages is available. |
Action | No user action required. |
Explanation | Message indicates when a custom property is set. |
Action | No user action required. |
Explanation | A core group bridge server is in the process of rebuilding the state information from foreign core groups. |
Action | No user action required. |
Explanation | The core group bridge server has received all of the necessary state information from list foreign core groups. |
Action | No user action required. |
Explanation | The core group bridge server did not receive all of the necessary state information in the allocated time. The core groups the bridge received state from are listed. |
Action | No user action required. |
Explanation | Lists of servers the core group bridge did not receive synchronization information from in the allocated time. |
Action | No user action required. |
Explanation | Displays total amount of data from foreign core groups that is posted to the local core group. |
Action | No user action required. |
Explanation | The configuration information for the core group bridge service is invalid. See the error log for more information. |
Action | Use either the administrative console application or the command line scripting tool to correct the invalid core group bridge service configuration. |
Explanation | A required service for the core group bridge service service is not accessible. See the error log for more information. |
Action | Ensure that the required service is configured correctly. |
Explanation | Core group bridge services must be enabled within the core group before the core group bridge services can send messages to other core groups. |
Action | Enable at least one core group bridge service for communication with other core groups. |
Explanation | The core group bridge service can only execute on a node managed by a deployment manager. |
Action | Add this node to a deployment manager's list of managed nodes if you want the core group bridge service to execute on this node. |
Explanation | This core group bridge service was contacted by a core group bridge service that is not configured as part of this core group bridge service's access point group. |
Action | To establish communication with the invalid core group bridge, add the host name and DCS port of the invalid core group bridge, as a peer access point, to the configuration settings for the core group bridge service. |
Explanation | A server can only be a bridge for a core group that it is located in. |
Action | Review the core group bridge settings for core groups {0} and {1} and make sure the correct servers are selected as bridge interfaces. |
Explanation | A connecting tunnel bridge must connect to each available member of the core group access point in a remote cell. |
Action | Update the PeerCoreGroup of the remote cell to include the unkown server. |
Explanation | This server used an incorrect tunnel access point group to communicate with the targeted tunnel bridge server. |
Action | Configure the member communication key of this server's tunnel access point group to match the member communication key of the targeted bridge's tunnel access point group. The member communication key is the name of the tunnel access point group by defaut. |
Explanation | The inbound chain used to handle HTTP core group bridge messages is not available. |
Action | Make sure the DCS port for this server is available. |
Explanation | Only have one tunnel peer access point can be configured for a cell. |
Action | Delete one of the tunnel peer access points for the specified cell |
Explanation | Core group bridge services must be enabled within the core group before messages can be sent to other core groups. |
Action | Enable at least one core group bridge service for communication with other core groups. |
Explanation | This system does not have enough CPU cycles available to process the core group bridge post messages. This problem might occur if too many servers are being stopped or started. |
Action | If, after all of the servers are started, the system resources are still insufficient to process the core group bridge post messages, then move the core group bridge service to a server that is located on a system that has more available system resources. |
Explanation | This system does not have enough CPU cycles available to process the core group bridge subscription messages. This problem might occur if too many servers are being stopped or started. |
Action | If, after all of the servers are started, the system resources are still insufficient to process the core group bridge subscription messages, then move the core group bridge service to a server that is located on a system that has more available system resources. |
Explanation | This bridge was contacted by a server that it is not configured to communicate with. |
Action | Ensure the undefined server is not an improperly configured Peer Access Point. |
Explanation | An incorrect tunnel access point group to communicate with the targeted tunnel bridge server. |
Action | Configure the member communication key of the connecting server's tunnel access point group to match the member communication key of this bridge's tunnel access point group. The member communication key is the name of the tunnel access point group by defaut. |