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 | 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 given value is not allowed for the property specified. |
Action | Change the value to a value that is supported for the property. |
Explanation | The user name and password supplied are not correct. |
Action | See the linked exception for the user name and check that the user name and password are correct and have been defined to the system. |
Explanation | An attempt to create a JMS connection failed due to an exception from the JCA runtime. |
Action | See the linked exception for more information. |
Explanation | The user name is not authorized to access the resource. |
Action | See the linked exception for the user name and ensure that it is correctly authorized to the required resource on the system. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
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 application called a method that must not be used after the connection is closed. |
Action | Ensure that the connection is not closed before calling the method. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
Explanation | An application has tried to set the client ID after it has previously been set or administratively configured. |
Action | Ensure that the client ID is not set after it has been previously set or configured. |
Explanation | A call into the JCA runtime to create a session generated an exception. |
Action | Examine the linked exception for further information. |
Explanation | A method was called that is not permitted in the current container. |
Action | Remove the call to the method. |
Explanation | The application has attempted to use a feature or capability that is not supported by the current release of the software. |
Action | Remove the code that attempts to use this capability or update to a later release of the software if available. |
Explanation | The connection was closed during the execution of this method. |
Action | Repeat the call using a new connection. |
Explanation | The application called a method that must not be called on a nontransacted session. |
Action | Change the application program to remove this behavior. |
Explanation | It was not possible to unsubscribe from the durable subscription. This may happen if there is an active subscriber attached to the subscription, or the subscription holds messages that are under transaction. |
Action | Ensure that there is no active subscriber and retry the unsubscribe method. |
Explanation | The current user does not have authorisation to unsubscribe the durable subscription. |
Action | Check the userID has the required access to the resources needed. See the linked exception for more details. |
Explanation | The application called a method that is optional in the JMS specification, and which is not supported by this implementation. |
Action | Remove calls to the named methods from the application. |
Explanation | The user application passed in an implementation class from an unsupported JMS provider. |
Action | Replace the unsupported object with one that is supported. |
Explanation | A queue name was supplied to a createTopic call or vice versa. |
Action | Alter the name so that it correctly describes the object type. |
Explanation | The given value is not allowed for the property specified. |
Action | Change the value to a value that is supported for the property. |
Explanation | An application called a method that must not be used after the session is closed. |
Action | Ensure that the session in not closed before calling the method. |
Explanation | The application called a method that must not be called on a transacted session. |
Action | Change the application program to remove this behavior. |
Explanation | The application call a method on a session object for which the associated Connection has been closed. |
Action | Ensure that the connection is not closed before calling the method. |
Explanation | The application tried to connect to a destination that is not defined. |
Action | Correctly define the required destination and repeat the operation. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
Explanation | The application tried to unsubscribe a durable subscription which does not exist. |
Action | No action is required unless the application expected the subscription to exist, in which case it should previously have created it. |
Explanation | A method was called that is not permitted in the current container. |
Action | Remove the call to the method. |
Explanation | It is mandatory to set the durableSubscriptionHome property before creating a connection that will use durable subscribers |
Action | Set the ConnectionFactory durableSubscriptionHome property to the name of the messaging engine on which the subscription should be localized. |
Explanation | The user name is not authorized to access the resource. |
Action | See the linked exception for more detail. Check that the user name is correctly authorized to the required resource on the system. |
Explanation | The temporary topic could not be deleted. It may have active subscribers. |
Action | Close any subscribers to the topic and retry the call. |
Explanation | An application called a method that must not be used after the message producer is closed. |
Action | Ensure that the message producer is not closed before calling the method. |
Explanation | A problem was encountered whilst creating a MessageProducer. |
Action | See the linked exception for more information. |
Explanation | A problem was encountered whilst sending a messsage. |
Action | See the linked exception for more information. |
Explanation | The producer was created with a null destination and a destination was not supplied on the send method. |
Action | Change the application so that a send method that specifies a destination is used, or specify a destination when creating the producer. |
Explanation | The producer was created with a specified destination; it is not valid to specify a destination again when sending a message. |
Action | Change the application so that a send method that does not specify a destination is used, or specify a null destination when creating the producer. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
Explanation | The given value is not allowed for the property specified. |
Action | Change the value to a value that is supported for the property. |
Explanation | The linked exception contains details of the authority that is required to carry out this operation. |
Action | The administrator must grant the required authority to the relevant user. |
Explanation | An application called a method that must not be used after the message consumer is closed. |
Action | Ensure that the message consumer is not closed before calling the method. |
Explanation | The JMS specification does not permit the use of a session for synchronous methods when asynchronous message delivery is running. |
Action | Create a separate session if you wish to use both synchronous methods and asynchronous delivery simultaneously. |
Explanation | A message selector was supplied that was incorrect. |
Action | See the linked exception for more information. |
Explanation | A method was called that is not permitted in the current container. |
Action | Remove the call to the method. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
Explanation | A problem was encountered whilst creating a MessageConsumer. |
Action | See the linked exception for more information. |
Explanation | A stopped connection will not deliver messages to message consumers. An attempt to consume messages from a stopped connection may indicate an error in the application logic. |
Action | Check to see if consuming from a stopped connection is an expected behaviour of the application. Correct the application design if it is not. |
Explanation | A MessageConsumer with a registered MessageListener received an exception from the onMessage method. |
Action | The onMessage method should be changed to avoid throwing exceptions. |
Explanation | The linked exception contains details of the authority that is required to carry out this operation. |
Action | The administrator must grant the required authority to the relevant user. |
Explanation | An application tried to set an object property using an object type that is not permitted by the JMS specification. |
Action | Use a permitted object type, which are the primitive wrapper classes or String objects. |
Explanation | While receiving a message an exception was thrown that caused the operation to fail. |
Action | Examine the specified exception, and linked exception object for more information. |
Explanation | Conversion between the two specified data types is not permitted by the JMS specification. |
Action | Retrieve the named item using one of the permitted conversions. |
Explanation | An application attempted to retrieve the value of a field that has not been set. |
Action | Set the value of the field before retrieving it. |
Explanation | A user application has attempted to set a field using a name that is not valid, for example, null or empty String. |
Action | Use a valid field name. |
Explanation | A user application has attempted to set a read-only message body. |
Action | Change the application program to remove this behavior, or call the clearBody method first. |
Explanation | A user application has attempted to set a read-only message property. |
Action | Change the application program to remove this behavior, or call the clearProperties method first. |
Explanation | A user application has attempted to read a write-only message body. |
Action | Change the application program to remove this behavior, or call the reset method first. |
Explanation | The message has either been constructed by the application, or has been obtained using a queue browser, and so does not support the stated operation. |
Action | Ensure that applications only invoke this operation on messages obtained via a receive call, or on messages presented to a MessageListener. |
Explanation | It was not possible to create the message due to an error. |
Action | Examine the linked exception for details of the error. |
Explanation | The supplied property name does not conform to the allowed format described in the JMS specification. |
Action | Check the characters used in the property name and modify as necessary. |
Explanation | The supplied property name begins with the JMS prefix, but is not one of the supported, settable properties. |
Action | Check the property name and correct errors. |
Explanation | JMS_IBM properties may only be set using a specific variable type. |
Action | Correct application code to use the required variable type when setting this JMS_IBM property. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
Explanation | The given value is not allowed for the property specified. |
Action | Change the value to a value that is supported for the property. |
Explanation | It was not possible to serialize the object because of the exception. |
Action | Examine the linked exception for details of the error. |
Explanation | It was not possible to deserialize the message because of the exception shown. |
Action | Examine the linked exception for details of the error. |
Explanation | A user application requested a message from a queue browser when none was available. |
Action | Ensure the application either does not call this method when there are no messages available, or handles this exception. |
Explanation | An application called a method that must not be used after the queue browser is closed. |
Action | Ensure that the queue browser is not closed before calling the method. |
Explanation | The createBrowserSession call returned null instead of a valid BrowserSession object. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
Explanation | A problem was encountered whilst browsing the destination. |
Action | See the linked exception for more information. |
Explanation | A message selector was supplied that was incorrect. |
Action | See the linked exception for more information. |
Explanation | While receiving a message an exception was thrown that caused the operation to fail. |
Action | Examine the specified exception, and linked exception object for more information. |
Explanation | The linked exception contains details of the authority that is required to carry out this operation. |
Action | The administrator must grant the required authority to the relevant user. |
Explanation | A null reference was passed to the StreamMessage.readBytes method, so no data could be returned. |
Action | Pass a suitably sized buffer into the readBytes method. |
Explanation | The end of the message content has been reached. This is normal if the reading application does not know how much data to expect. |
Action | No action required. |
Explanation | An attempt has been made to read the next field from the stream whilst a byte array is partly read. |
Action | Ensure that the user code completes the read of any byte array before attempting to read the next field. |
Explanation | An attempt was made to read a StreamMessage field containing null using the readChar method. |
Action | Avoid reading nulls using the readChar method. |
Explanation | The supplied value does not have a known encoding. |
Action | Ensure that the application supplies a value from the defined list of encodings. |
Explanation | A problem has occurred with data streams used for format conversion of float and double values. |
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 attempt was made to read beyond the end of the message. This may be a normal condition if an application has been coded to read variable length data using the JMS 1.0.2 specification. |
Action | If necessary, recode the application to use the new getBodyLength method. |
Explanation | There was a problem during either reading or writing of a UTF-8 string. The most common problem is attempting to write a string longer than 65535 characters. |
Action | See the linked exception for further information. |
Explanation | An object was provided to the writeObject method that was not a Java primitive wrapper type. |
Action | Correct the application to ensure that only objects of the permitted types are passed as parameters to the writeObject method. |
Explanation | An error was encountered whilst trying to write an item to the message. |
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 provided to the writeObject method that was not a Java primitive wrapper type. |
Action | Correct the application to ensure that only objects of the permitted types are passed as parameters to the writeObject method. |
Explanation | An object was provided to the writeObject method that was not a Java primitive wrapper type. |
Action | Correct the application to ensure that only objects of the permitted types are passed as parameters to the writeObject method. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
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 | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
Explanation | The connection was closed during the execution of this method. |
Action | Repeat the call using a new connection. |
Explanation | The durable subscription is not accepting consumers. It may already have an active subsriber, or it may have been administratively disabled. See the linked exception for further detail. |
Action | Check the application(s) to see if there may be multiple attempts to access a single durable subscription. The JMS specification prohibits this, but if absolutely required see the shareDurableSubscriptions option on the connection factory. |
Explanation | The current user does not have authorisation to access the durable subscription. |
Action | Check the userID has the required access to the resources needed. See the linked exception for more details. |
Explanation | A problem was encountered interpreting the provided selector string. |
Action | Check the selector string and correct any errors. |
Explanation | It was not possible to create a durable subscriber because of a problem with the topic space. |
Action | See the linked exception for details. If the topic space did not exist, either create it or use one that does exist. If the topic was a temporary one, either use a non-durable subscriber or change to a permanent topic. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
Explanation | The given value is not allowed for the property specified. |
Action | Change the value to a value that is supported for the property. |
Explanation | The given value is not allowed for the property specified. |
Action | Change the value to a value that is supported for the property. |
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 | It is likely that the destination object does not have sufficient information to be used for production and/or consumption of messages. |
Action | Refer to your IBM representative for information on the cause of the given reason code. |
Explanation | The publish/subscribe broker profile topic mapping used to transfer the original publication from MQ does not contain a broker input queue so it is not possible to route the reply message. |
Action | Add the correct broker input queue name to the appropriate broker profile topic mapping. |
Explanation | The given value is not allowed for the property specified. |
Action | Change the value to a value that is supported for the property. |
Explanation | The given value is not allowed for the property specified. |
Action | Change the value to a value that is supported for the property. |
Explanation | An exception originated outside of user code whilst asynchronous delivery was running |
Action | See the linked exception for more information |
Explanation | The messaging engine to which the application is attached has been shut down. |
Action | The application should use this as a signal to disconnect from the messaging engine. |
Explanation | A communications failure has resulted in the loss of the connection to the messaging engine. |
Action | Examine the linked exception for more information. |
Explanation | The messaging engine has been shutdown leaving the connection unusable. |
Action | Restart the messaging engine and reconnect. |
Explanation | The specified character set is a required for operation of this functionality, but could not found. |
Action | Make the specified character set available for use by this JVM. |
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 | 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 identified character is not allowed in a name-value pair element of a URI string unless escaped by a backslash. |
Action | Escape the identified character by preceding it with a backslash. |
Explanation | The name-value pair element identified is malformed, possibly not containing both a name and a value. |
Action | Examine the identified name-value pair element to ensure that is it correctly formed. |
Explanation | The identified destination prefix is reserved. |
Action | Consider using the prefix 'queue://' for a queue destination or 'topic://' for a topic destination. |
Explanation | The name property of the URI element indentified could not be decoded into a valid Destination property. |
Action | Ensure that the name property identified is a valid property for Destination objects. |
Explanation | The use of queue managers as specified in the destination URI is not supported. |
Action | Specify a valid URI which does not include the use of a queue manager. |
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 | 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 illegal escape sequence was found whilst processing the URI string for a Destination |
Action | If the destination or replyTo strings have been manipulated by user code then check that all & characters are correctly escaped (for use in xml). If not, consider contacting IBM service. |
Explanation | Whilst attempting to prepare a message for transmission to MQ, an character was encountered in the Destination or ReplyTo fields that did not conform to the UTF-16 surrogate rules. |
Action | Ensure that no illegal surrogate characters are used for Destination or ReplyTo names that may be sent to MQ. |
Explanation | The application called a method that is not supported by the JMS specification. |
Action | Change the application program to remove this behavior. |
Explanation | The application has attempted to use a feature or capability that is not supported by the current release of the software. |
Action | Remove the code that attempts to use this capability or update to a later release of the software if available. |
Explanation | The application called a method that is not supported by the JMS specification. |
Action | Change the application program to remove this behavior. |
Explanation | The application has attempted to use a feature or capability that is not supported by the current release of the software. |
Action | Remove the code that attempts to use this capability or update to a later release of the software if available. |
Explanation | During execution of the specified method an exception was thrown by another component. |
Action | See the linked exception for more information. |
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 | If the message does not give sufficient information, check any previous messages for further information. |
Action | If you are not able to resolve the problem ask your system administrator to help resolve the problem. |