Explanation | Part of the migration process is to create a service integration bus. This was unsuccessful. |
Action | Report this problem to your system administrator. |
Explanation | Part of the migration process is to add the named server to the service integration bus. This was unsuccessful. |
Action | Report this problem to your system administrator. |
Explanation | Part of the migration process is to create a WebSphere MQ client link. This was unsuccessful. |
Action | Report this problem to your system administrator. |
Explanation | One of the queues found in the configuration data being migrated could not be created in the new configuration. |
Action | Report this problem to your system administrator. |
Explanation | The command did not return a result. |
Action | Report this problem to your system administrator. |
Explanation | The result returned by the command indicates that it failed. |
Action | Report this problem to your system administrator. |
Explanation | When a server is a member of a bus, it should have one messaging engine defined for that bus. In this case, no messaging engines have been found. |
Action | Report this problem to your system administrator. |
Explanation | When a server is a member of a bus, it should have one messaging engine defined for that bus. In this case, more than one messaging engine has been found. |
Action | Report this problem to your system administrator. |
Explanation | An exception was thrown. |
Action | See stack trace for details. |
Explanation | The server configuration is invalid. |
Action | Run configuration validation. |
Explanation | An unexpected error has occurred. |
Action | Report this problem to your system administrator. |
Explanation | The supplied JMS server has no "was.shortName" property, or the "was.shortName" property defines a null shortname. |
Action | Report this problem to your system administrator. |