Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The definition for the specified WebSphere MQ Server bus member names a transport chain that does not exist. Unless corrected, it is not possible for this bus to establish client mode connections to the WebSphere MQ server. |
User response | Modify the WebSphere MQ Server definition to use another transport chain name, or consult the product documentation to determine how to create a new transport chain. |
Problem | The specified WebSphere MQ Server bus member is incorrectly configured to use an inbound transport chain. Unless corrected, it is not possible for this bus to establish client mode connections to the WebSphere MQ Server. |
User response | Modify the WebSphere MQ Server definition to use an outbound transport chain name. |
Problem | The specified WebSphere MQ Server bus member is incorrectly configured to use a transport chain that is not suitable for establishing a client mode connection to WebSphere MQ. Unless corrected, it is not possible for this bus to establish client mode connections to the WebSphere MQ Server. |
User response | Consult the product documentation to determine what chain types are suitable. Modify the WebSphere MQ Server definition to use a suitable transport chain definition. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | Only certain versions of the WebSphere MQ product are supported on certain platforms. For destinations assigned to a WebSphere MQ Server bus member to be accessible, the WebSphere MQ Queue Manager it refers to must be running on a supported version of WebSphere MQ. Consult the product documentation to determine the versions of WebSphere MQ that are supported. |
User response | Modify the WebSphere MQ server bus member definition to always reference a WebSphere MQ queue manager running on a supported version of WebSphere MQ. Alternatively, upgrade the version of WebSphere MQ to a supported version. |
Problem | The connection to a WebSphere MQ queue manager, as defined by the named server definition, is prevented from taking place. The connection is not over a secure medium and the application server is configured for secure connections only. |
User response | Either disable security for the application server, or specify settings that permit a secure connection to WebSphere MQ. |
Problem | Only certain versions of the WebSphere MQ product are supported. For destinations assigned to a WebSphere MQ Server bus member to be fully accessible, the WebSphere MQ queue manager it refers to must be running on a supported version of WebSphere MQ. Consult the product documentation to determine the versions of WebSphere MQ that are supported. |
User response | Modify the WebSphere MQ Server bus member definition to always reference a WebSphere MQ queue manager running on a supported version of WebSphere MQ. Alternatively, upgrade the version of WebSphere MQ to a supported version. |
Problem | An exception occurred when using a Websphere MQ queue. |
User response | Identify the MQ error and take corrective action. |
Problem | An exception occurred when using a Websphere MQ queue manager. |
User response | Identify the MQ error and take corrective action. |
Problem | The connection to the named WebSphere MQ server (queue manager or queue sharing group) failed. The WebSphere MQ reason for the failure is provided. |
User response | Examine the WebSphere MQ reason code to determine the reason for the failure. If possible, resolve the issue and retry. Otherwise, contact your local systems administrator. |
Problem | An attempt to create an agent for sending Programmable Command Form messages to WebSphere MQ failed. It is possible that the Command Server on WebSphere MQ has not been started. The WebSphere MQ reason for the failure is provided. |
User response | Examine the WebSphere MQ reason code to determine the reason for the failure. If possible, resolve the issue and retry. Otherwise, contact your local systems administrator. |
Problem | An attempt to disconnect the agent for sending Programmable Command Form messages to WebSphere MQ has failed. The WebSphere MQ reason for the failure is provided. |
User response | Examine the WebSphere MQ reason code to determine the reason for the failure. If possible, resolve the issue and retry. Otherwise, contact your local systems administrator. |
Problem | An attempt was made to access resources on a WebSphere MQ server, but the WebSphere MQ server is at an unsupported command level. The supported command level is greater than or equal to 600. |
User response | Run against an MQ server that is at a supported command level. |
Problem | An attempt was made to access resources on a WebSphere MQ server, but the WebSphere MQ server is running on an unsupported platform. Currently, only the z/OS platform is supported. |
User response | Run against an MQ server that is running on a supported platform. |
Problem | An attempt to issue the specified command as a programmable command form message to the specified WebSphere MQ server failed. The WebSphere MQ reason for the failure is provided. |
User response | Examine the WebSphere MQ reason code to determine the reason for the failure. If possible, resolve the issue and retry. Otherwise, contact your local systems administrator. |
Problem | An attempt to issue the specified command as a programmable command form message to the specified WebSphere MQ server failed. An IO exception occurred. |
User response | Contact your local systems administrator. |
Problem | An attempt to discover WebSphere MQ resources failed because the allowDiscovery attribute of the WebSphere MQ server object that is currently in use, is set to disallow discovery. |
User response | Modify the current MQ server object to allow resource discovery, or use an alternate MQ server object that is already configured to allow queue discovery. Otherwise, contact your local systems administrator. |
Problem | The specified command was issued to the specified WebSphere MQ server, but the server failed to process it. The WebSphere MQ reason code is provided. |
User response | Examine the WebSphere MQ reason code to determine the reason for failure. If possible, resolve the issue and retry. Otherwise, contact your local systems administrator. |
Problem | The type attribute is set to Queue Sharing Group, but the target WebSphere MQ server is not a z/OS server. Queue Sharing Groups are supported on z/OS servers only. |
User response | Either change the value of the type attribute to Queue Manager, or run against a WebSphere MQ z/OS queue manager that is configured to be a member of a queue sharing group. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | Use of the specified transport chain is not permitted by the security settings of the specified bus. As a result, bus resources assigned to the specified WebSphere MQ Server will not be available. |
User response | Either modify the security settings for the bus to permit use of the specified transport chain, or modify the WebSphere MQ Server definition to use another transport chain. |
Problem | An agent is used to send command messages to a WebSphere MQ Server but this is currently null. It is possible that the agent creation has failed. |
User response | Collect diagnostic trace data and contact your local systems administrator. |
Problem | If the message does not give sufficient information, check previous messages for further help. |
User response | If you are not able to resolve the problem ask your system administrator to help resolve the problem. |