Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | An internal error has occurred. The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | An internal error has occurred. The JmsFactoryFactory.getInstance() method did not receive a correct JMSRAFactoryFactory type as expected. |
Action | 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/. |
Explanation | The prefix for temporary destination names may not be longer than twelve characters. |
Action | Specify a prefix that is twelve characters or less. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | The prefix for temporary destination names may not be longer than twelve characters. |
Action | Specify a prefix that is twelve characters or less. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | An error has been caught whilst obtaining a connection. The system will purge the connection and attempt to obtain another one. |
Action | 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/. |
Explanation | The set of sessions in the connection has more than one session when there should only be one. |
Action | 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/. |
Explanation | An object was found in the set of sessions which was not of the type required. |
Action | 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/. |
Explanation | An object was found in the set of sessions which was not of the type required. |
Action | 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/. |
Explanation | The method cannot be called after the connection is closed. |
Action | 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/. |
Explanation | The method cannot be called after the connection is closed. |
Action | 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/. |
Explanation | The request information is not of the correct type. |
Action | 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/. |
Explanation | The call to the lazyEnlist method on the connection manager failed. |
Action | 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/. |
Explanation | The supplied credentials resulted in an authentication failure. |
Action | 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/. |
Explanation | An object of the wrong type was received. |
Action | 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/. |
Explanation | It is not possible to start a local transaction if one already exists. |
Action | 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/. |
Explanation | A SICoreConnection object is required but cannot be found. |
Action | 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/. |
Explanation | A SICoreConnection object is required but cannot be found. |
Action | 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/. |
Explanation | Outside of a WebSphere application server a messaging engine name must be explicitly stated during connection factory configuration in order to support transactional usage. |
Action | Change the connection factory configuration to specify a remoteTargetType of "ME" and a remoteTargetGroup containing the name of the messaging engine to connect to. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | The included exception information can be used for diagnosis. |
Action | 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/. |
Explanation | The supplied credentials resulted in an authentication failure. |
Action | 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/. |
Explanation | An unexpected exception was thrown when the session tried to re-associate itself with a connection manager. |
Action | 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/. |
Explanation | The connection manager is not lazy enlistable. |
Action | 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/. |
Explanation | The method cannot be called after the session is closed. |
Action | 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/. |
Explanation | The method call is not allowed after the session is invalidated. |
Action | 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/. |
Explanation | The method call is not allowed if there is no local transaction. |
Action | 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/. |
Explanation | The call is not allowed in a nonmanaged environment. |
Action | 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/. |
Explanation | The method cannot be called after the session is closed. |
Action | 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/. |
Explanation | The method cannot be called after the session is closed. |
Action | 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/. |
Explanation | The method cannot be called after the session is closed. |
Action | 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/. |
Explanation | The method cannot be called after the session is closed. |
Action | 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/. |
Explanation | The method call is not allowed after the session is invalidated. |
Action | 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/. |
Explanation | The method call is not allowed after the session is invalidated. |
Action | 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/. |
Explanation | The method call is not allowed after the session is invalidated. |
Action | 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/. |
Explanation | The method call is not allowed after the session is invalidated. |
Action | 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/. |
Explanation | The method call is not allowed if there is a global transaction active. |
Action | 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/. |
Explanation | The method call is not allowed if there is no local transaction. |
Action | 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/. |
Explanation | The method call is not allowed if there is a global transaction active. |
Action | 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/. |
Explanation | The method call is not allowed if there is no local transaction. |
Action | 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/. |
Explanation | The method call is not allowed if there is no local transaction. |
Action | 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/. |
Explanation | The JmsJcaReferenceUtils class failed to initialize. |
Action | 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/. |
Explanation | During validation of the properties configured on a JMS activation specification the target significance was deemed to be invalid |
Action | The target significance field had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the target type was deemed to be invalid |
Action | The target type field had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the given reasons were given as to why the validation failed. |
Action | One or more invalid properties where found, correct the values of the properties on the JMS activation specification and restart the server. |
Explanation | During endpoint activation the JMS resource adapter was attempting to obtain a utility class and an unexpected exception was received. |
Action | 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/. |
Explanation | During validation of the properties configured on a JMS activation specification the client ID was deemed to be invalid |
Action | The client ID had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During the validation of a JMS activation specification an unexpected exception was received. |
Action | 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/. |
Explanation | During the registration of the WLM classifier for the JMS resource adapter with the handler registry an unexpected exception was received. |
Action | 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/. |
Explanation | During validation of the properties configured on a JMS activation specification the bus name was deemed to be invalid |
Action | The bus name had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the destination was deemed to be invalid |
Action | The destination had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the destination type was deemed to be invalid |
Action | The destination type had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the acknowledge mode was deemed to be invalid |
Action | The acknowledge mode had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the read ahead was deemed to be invalid |
Action | The read ahead had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the destination was deemed to be invalid |
Action | The destination had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the destination was deemed to be invalid |
Action | The destination had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the subscription durability was deemed to be invalid |
Action | The subscription durability had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the durable subscription home was deemed to be invalid |
Action | The durable subscription home had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the subscription name was deemed to be invalid |
Action | The subscription name had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the share durable subscription was deemed to be invalid |
Action | The share durable subscription field had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the maximum batch size was deemed to be invalid |
Action | The maximum batch size had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | During validation of the properties configured on a JMS activation specification the share data source with CMP was deemed to be invalid |
Action | The share data source with CMP had an invalid value, correct the value of the property on the activation specification and restart the server. |
Explanation | A problem occurred while creating the JmsJcaFactory object. Previous messages contain information about the problem. |
Action | 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/. |
Explanation | The WebSphere Platform Messaging JMS resource adapter was attempting to create an SIUncoordinatedTransaction to register in a transaction as a Synchronization when an exception occurred. |
Action | 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/. |
Explanation | The connection the WebSphere Platform Messaging JMS resource adapter has obtained does not support the container-managed persistence optimization because it is to a remote messaging engine. |
Action | Ensure that there is a local messaging engine available for the resource adapter to connect to or disable the sharing optimization on the connection factory definition via WebSphere administration. |
Explanation | A call to getSynchronization has occurred when the managed connection is already registered as a synchronization in a transaction. |
Action | 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/. |
Explanation | During endpoint activation the JMS resource adapter was attempting to obtain a utility class and an unexpected exception was received. |
Action | 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/. |
Explanation | The message endpoint factory has returned a message endpoint that does not implement the MessageListener interface as expected. |
Action | 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/. |
Explanation | An exception was thrown during the attempt to obtain an instance of the onMessage method. |
Action | 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/. |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | See previous messages for further information. |