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 | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | An application has connected to the messaging engine and requested a destination type which does not match the underlying destination type. |
User response | Correct the connecting application, or alter the destination to the required type using the administrative console. |
Problem | The named destination is unknown on the local messaging engine. |
User response | Check that the destination name is correct. If the destination exists on another messaging engine, ensure that communication with the other messaging engine is working. |
Problem | An attempt was made to use a transaction that has already been completed. |
User response | Make sure that the transaction used is a new transaction. |
Problem | An attempt has been made to send a message to a destination and a check has been made to ensure that this destination is send allowed. This check failed as the destination is send disallowed. |
User response | Update the destination so it is send allowed and resend the message. |
Problem | A user is not authorized to send to the destination. |
User response | If the user should have authority to send messages on the given destination then update the users authorization rights for the destination. |
Problem | A user is not authorized to send to temporary destinations with the named prefix. |
User response | If the user should have authority to send messages on the given temporary destination then update the users authorization rights for the temporary destination. |
Problem | A user is not authorized to send to the destination using the specified topic. |
User response | If the user should have authority to send messages on the given topic then update the users authorization rights for the topic on the given destination. |
Problem | The Producer has been closed and cannot be used on the specified destination. |
User response | Create a new Producer session to the specified destination. |
Problem | The connection has been closed and cannot be used for any operation. |
User response | Create a new connection to the messaging engine. |
Problem | The next destination in the forward routing path could not be found so the message was put to the exception destination but there was an error putting the message to the exception destination. |
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 | An attempt has been made to send a message to a destination and a check has been made to ensure that a queue point is available for this destination. This check failed as the only queue point for this destination is send disallowed. |
User response | Update the queue point for the destination so it is send allowed and retry the send operation. |
Problem | All queues to the named destination have already reached their configured high limit therefore the message cannot be accepted. |
User response | Check that the configured high messages limit for the destination is correct. If the destination exists on another messaging engine, ensure that communication with the other messaging engine is working. |
Problem | An attempt was made to send a message to a destination, but no message points of that destination could be found. |
User response | Create a message point for the destination and retry the command. |
Problem | The destination with the given name is corrupt and cannot be used. |
User response | Reset the destination from the administrative console |
Problem | The target destination in the alias path is unknown on the local messaging engine. |
User response | Define the target destination or correct the incorrect alias in the administrative console. |
Problem | The alias destination is not valid because it targets a service destination. |
User response | Remove the service destination target by changing aliases in the resolution path in the administrative console. |
Problem | The named link is unknown on the local messaging engine, so the attempt to create the named bus failed. |
User response | Check that the link name is correct and defined in the administrative console for the bus. Check that the messaging engine has the latest configuration applied to it. |
Problem | The named destination is already known on the local messaging engine, so an attempt to create one failed. |
User response | Make sure the destination configuration is correct in the administrative console and restart the server. |
Problem | The destination is no longer usable because it has been deleted. |
User response | Specify a valid destination name when creating the producer session. |
Problem | An attempt was made to put a message to a destination, but the message has a higher reliability than the destination can support. |
User response | Update the destination so that it can support messages of a higher reliability or reduce the reliability of the message to be sent. |
Problem | An attempt to use a service destination when the forward routing path is empty has been made. |
User response | A service destination has to have mediated destinations in its forward routing path. Correct the path and retry. |
Problem | This message cannot be delivered because every attempt to commit the transaction that would deliver the message did not succeed. |
User response | Investigate the cause of the transaction rollbacks. |
Problem | The message was administratively removed from the given destination and moved to the exception destination. |
User response | None. |
Problem | A message could not traverse its supplied routing path because the path contained an incorrect destination. |
User response | Check the destinations on the routing path are available. |
Problem | The named foreign bus is unknown on the local messaging engine. |
User response | Check that the foreign bus name is correct. Check that the foreign bus link has been defined and retry the command. |
Problem | The named foreign bus is unknown on the local messaging engine. |
User response | Check that the foreign bus name is correct. Check that the foreign bus link has been defined and retry the command. |
Problem | The named foreign bus link is unknown on the local messaging engine. |
User response | Check that the foreign bus name is correct and has links defined. If no links are defined, define a new foreign bus link between the two buses. |
Problem | An application has attempted to send a message to a destination on a foreign bus but there are no links defined between the local bus and the foreign bus. |
User response | Define a link between the local bus and the foreign bus in the admin console and resend the message. |
Problem | The named MQ link is unknown on the local messaging engine. |
User response | Check the MQ link name is defined and has the correct case sensitive spelling. If the MQ link is undefined, either use a MQ link which does exist or define a new MQ link. |
Problem | A message was redirected along a forward routing path. The number of redirects exceeded the maximum allowed. The message was therefore sent to the exception destination. |
User response | Check the forward routing path for cycles. Alternatively increase the maximum value via the custom property, sib.processor.maxForwardRoutingPath |
Problem | The message was given to the specified mediation; that mediation generated an exception and, as a result, the message has been rerouted to the exception destination. |
User response | If the mediation should not have rerouted the message, investigate the cause of the exception. |
Problem | After being mediated by the specified mediation, the message does not conform to the message format specified. The mediation has either changed the message contents or changed the message format (or both). The original version of the message has been rerouted to the exception destination. |
User response | Investigate how and why the specified mediation has modified the message so that it does not conform to the specified message format. |
Problem | After being mediated by the specified mediation, the message properties contained objects that could not be serialized, or the data graph is not valid. |
User response | Investigate how and why the specified mediation has modified the message so that it is no longer well formed. |
Problem | The message is too big. |
User response | Check the MQ settings. |
Problem | The message cannot be processed because of a format error. |
User response | Check the connection. |
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/. |