| Explanation | An unexpected notification was received. |
| Action | Report program defect to IBM. |
| Explanation | An unexpected exception occured. |
| Action | Report program defect to IBM. |
| Explanation | An application event was received for a non-existent application. |
| Action | Report program defect to IBM. |
| Explanation | A web module is deployed into a virtual host which was not found. |
| Action | Report program defect to IBM. |
| Explanation | An application server''s web container did not have an associated thread pool. |
| Action | Report program defect to IBM. |
| Explanation | The Proxy is waiting to receive current routing information. The wait will be a timeout in the specified number of seconds. |
| Action | None |
| Explanation | The Proxy has received current routing information. |
| Action | None |
| Explanation | The Proxy Server has received partial routing information, some information may be missing. |
| Action | If repeated partial information is received, try increasing the timeout value by setting "routing.info.timeout". |
| Explanation | A server has been marked started or stopped in the local ODC tree |
| Action | None |
| Explanation | The deployments directory of an application could not be located. |
| Action | Verify that the application is deployed correctly. |
| Explanation | An updated ODC generated plugin-cfg.xml file was written due to events that changed its contents. |
| Action | None |
| Explanation | This should not happen. It can be caused by a problem with the configuration or a conflicting other process(es). This process will be unable to communicate in certain important ways unless and until the problem is corrected and this process is restarted. |
| Action | Consider the details in the exception. Correct any configuration problem, eliminate conflicting use of the configured port(s), or report to IBM. |
| Explanation | The peer communication layer for On Demand Configuration is setting up. |
| Action | Information only; no action required. |
| Explanation | The peer communication layer for On Demand Configuration could not find the host name of the Deployment Manager for this cell; this process will operate as a standalone process. |
| Action | Ensure that this node is federated into a cell, unless you intend it to operate in standalone mode. |
| Explanation | The peer communication layer for On Demand Configuration encountered a configuration error. |
| Action | Report error condition to IBM. |
| Explanation | This is a setting used to test failure handling, not to be used in normal operations. |
| Action | If this testing is not desired, remove the cell custom property named son.connectFailProbability. |
| Explanation | This is a setting used to test flow control, not to be used in normal operations. |
| Action | If this testing is not desired, remove the cell custom property named son.writeDelay. |
| Explanation | This is a setting used to expose problems that are exacerbated by bug 15832, not to be used in normal operations. |
| Action | If this testing is not desired, remove the cell custom property named son.keepBug15832. |
| Explanation | The peer communication layer for On Demand Configuration is starting. |
| Action | Information only; no action required. |
| Explanation | The peer communication layer for On Demand Configuration has started. |
| Action | Information only; no action required. |
| Explanation | An informational message that indicates that this server has detected the start of the indicated process. |
| Action | None. |
| Explanation | An informational message that indicates that this server has detected the stop of the indicated process. |
| Action | None. |
| Explanation | An internal error occurred. |
| Action | Report to IBM. |
| Explanation | A suspicious internal condition arose. |
| Action | Report to IBM if bad symptoms result. |
| Explanation | The specified UDP Channel has been opened and is now listening. |
| Action | Information only; no action required. |
| Explanation | The peer infrastructure is setting up. |
| Action | Information only; no action required. |
| Explanation | The unstructured overlay has completed its initialization, and is not using SSL. |
| Action | Information only; no action required. |
| Explanation | The unstructured overlay has completed its initialization, and is using SSL. |
| Action | Information only; no action required. |
| Explanation | This is one step in shutting down the host process. |
| Action | Information only; no action required. |
| Explanation | This is one step in shutting down the host process. |
| Action | Information only; no action required. |
| Explanation | The specified UDP Channel has been closed and and is no longer listening. |
| Action | Information only; no action required. |
| Explanation | This is a periodic printout of network statistics for the overlay. |
| Action | Information only; no action required. |
| Explanation | A new edge was added in the overlay. |
| Action | Information only; no action required. |
| Explanation | A new edge was added in the overlay. |
| Action | Information only; no action required. |
| Explanation | An edge was removed from the overlay. |
| Action | Information only; no action required. |
| Explanation | An edge was removed from the overlay. |
| Action | Information only; no action required. |
| Explanation | This is a periodic printout of operational statistics for the overlay. |
| Action | Information only; no action required. |
| Explanation | This is a periodic printout of operational statistics for the overlay. |
| Action | Information only; no action required. |
| Explanation | This should not happen, and indicates a temporary or continuing problem with connectivity or load. |
| Action | Report to IBM if bad symptoms are associated. |
| Explanation | This is a status message; large numbers of active connections or buffers indicate there may be something going wrong. |
| Action | Report to IBM if this is associated with bad symptoms. |
| Explanation | An internal error occurred. |
| Action | Report to IBM. |
| Explanation | A suspicious internal condition arose. |
| Action | Report to IBM if bad symptoms result. |
| Explanation | An attempt has been made to perform an operation which is not supported by this server. |
| Action | Report to IBM any unsupported operations. |