Explanation | An informational message that indicates that this Deployment Manager process is in standby mode. |
Action | None. |
Explanation | An informational message that indicates that this Deployment Manager process is in active mode. |
Action | None. |
Explanation | An informational message that indicates the availability of the JMX SOAP proxy. |
Action | None. |
Explanation | The server cannot start the JMX SOAP proxy because of the stated exception. |
Action | Examine the exception in this message for problem determination. |
Explanation | The JMX SOAP proxy is unable to find a Deployment Manager process running in active mode. |
Action | Verify that a Deployment Manager process is running and in active mode. |
Explanation | This Deployment Manager process is in active mode but does not hold the lock on the file {0}. The active Deployment Manager process must hold a lock on this file, and if it does not, then it must be stopped. |
Action | Verify that the connection between all Deployment Manager processes and the shared device is stable, and then restart this deployment manager. |
Explanation | There was problems during reloading of tasks from harddisk. |
Action | None. |
Explanation | An informational message that indicates that Deployment Manager node {0} has been set to active mode. |
Action | None |
Explanation | An informational message that indicates that Deployment Manager node {0} has been removed from active mode. The Deployment Manager process is being stopped. |
Action | None |