Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | The value provided is not allowed for the property specified. |
Action | Enter a value that is supported for the property. |
Explanation | Authentication failed using the supplied details because the user name or the password is incorrect. |
Action | See the linked error message for more information.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 because of an exception from the JCA runtime environment. |
Action | See the linked exception for more information. |
Explanation | The user name is not authorized to access the resource. |
Action | See the linked error message for the user name. Ensure that it is correctly authorized for the required resource on the system. |
Explanation | Another component detected an error during the execution of the specified method. |
Action | See the linked error message for more information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | Authentication failed using the supplied details because the user name or the password is incorrect. |
Action | See the linked error message for more information.Check that the user name and password are correct, and have been defined to the system. |
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 | Another component detected an error during the execution of the specified method. |
Action | See the linked error message for more information. |
Explanation | An application has tried to set the client ID, which has already 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 to the JCA runtime environment to create a session generated an error. |
Action | See the linked error message for more 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 | Having a large number of sessions open on a connection can have a negative impact on performance. |
Action | Ensure that the application closes sessions that are no longer required. |
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 non-transacted session. |
Action | Change the application program to remove this behavior. |
Explanation | You cannot unsubscribe from a durable subscription that has an active consumer or holds messages that are locked under an active transaction. |
Action | Ensure that there is no active consumer, then retry the unsubscribe method. |
Explanation | The current user is not authorized to unsubscribe the durable subscription. |
Action | Check that the userID has the required access to the resources needed. See the linked error message for more information. |
Explanation | The application called a method that is optional in the JMS specification, and that 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 a topic name was supplied to a createQueue call. |
Action | Change the name to the correct object type. |
Explanation | The value provided is not allowed for the property specified. |
Action | Enter 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 called 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 | Define the required destination and repeat the operation. |
Explanation | Another component detected an error during the execution of the specified method. |
Action | See the linked error message 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 | Having a large number of producers open can have a negative impact or performance. |
Action | Ensure that the application closes producers that are no longer required. |
Explanation | The durableSubscriptionHome property must be set before a connection is created that will use durable subscriptions. |
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 error message for the user name and ensure that it 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 | Having a large number of consumers open on a session can have a negative impact on performance. |
Action | Ensure that the application closes consumers that are no longer necessary. |
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 while creating a MessageProducer. |
Action | See the linked error message for more information. |
Explanation | A problem was encountered whilst sending a message. |
Action | See the linked error message 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 | Another component detected an error during the execution of the specified method. |
Action | See the linked error message for more information. |
Explanation | The value provided is not allowed for the property specified. |
Action | Enter a value that is supported for the property. |
Explanation | The linked error message contains details of the authority 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 | If you want to use both synchronous methods and asynchronous delivery simultaneously, create a separate session. |
Explanation | An incorrect message selector was supplied. |
Action | See the linked error message for more information. |
Explanation | A method was called that is not permitted in the current container. |
Action | Remove the call to the method. |
Explanation | Another component detected an error during the execution of the specified method. |
Action | See the linked error message for more information. |
Explanation | A problem was encountered whilst creating a MessageConsumer. |
Action | See the linked error message for more information. |
Explanation | A stopped connection will not deliver messages to message consumers. An attempt to consume messages from a stopped connection might indicate an error in the application logic. |
Action | Check whether consuming from a stopped connection is an expected behavior of the application. If it is not, correct the application design. |
Explanation | A MessageConsumer with a registered MessageListener received an error message from the onMessage method. |
Action | Change the onMessage method to avoid throwing exceptions. |
Explanation | The linked error message describes the authority 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 is one of the primitive wrapper classes or String objects. |
Explanation | While receiving a message an error occurred that caused the operation to fail. |
Action | See the linked error message for more information. |
Explanation | The JMS specification does not permit conversion between the two specified data types. |
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 change the body of a message which is currently read-only. |
Action | Change the application program to remove this behavior, or set the message body to be writable by first calling the clearBody method. |
Explanation | A user application has attempted to change the property of a message which is currently read-only. |
Action | Change the application program to remove this behavior, or set the message property to be writable by first calling the clearProperties method. |
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 using a receive call, or on messages presented to a MessageListener. |
Explanation | It was not possible to instatiate a message in JMS because an error occurred in another part of the system. |
Action | See the linked error message for more information. |
Explanation | The supplied property name does not conform to the format described in the JMS specification. |
Action | Modify the property name. |
Explanation | The supplied property name begins with the JMS prefix, but is not one of the supported, settable properties. |
Action | Modify the property name. |
Explanation | JMS_IBM properties must be set using specific variable types. |
Action | Correct the application code to use the required variable type to set this JMS_IBM property. |
Explanation | Another component detected an error during the execution of the specified method. |
Action | See the linked error message for more information. |
Explanation | The value provided is not allowed for the property specified. |
Action | Enter a value that is supported for the property. |
Explanation | The object could not be serialized because of an error. |
Action | See the linked error message for more information. |
Explanation | The message could not be deserialized because of the exception shown. |
Action | See the linked error message for more imformation. |
Explanation | The application requested a message from a queue browser when none was available. |
Action | Modify the application to handle this error or use the hasMoreElements method to check whether further messages are available. |
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 | Another component detected an error during the execution of the specified method. |
Action | See the linked error message for more information. |
Explanation | A problem was encountered whilst browsing the destination. |
Action | See the linked error message for more information. |
Explanation | An incorrect message selector was supplied. |
Action | See the linked error message for more information. |
Explanation | While receiving a message an error occurred that caused the operation to fail. |
Action | See the linked error message for more information. |
Explanation | The linked error message contains details of the authority 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 StreamMessage before the current byte array field has been read completely. |
Action | Ensure that the user code fully reads 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | An attempt was made to read beyond the end of the message. This might 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 getBodyLength method. |
Explanation | A problem occurred during the 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 error message for further information. |
Explanation | The writeObject method was provided with an object parameter that was not a 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 occured while trying to write an item to the message. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | The writeObject method was provided with an object parameter that was not a 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 | The writeObject method was provided with an object parameter that was not a 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 | Another component detected an error during the execution of the specified method. |
Action | See the linked error message for more information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | Another component detected an error during the execution of the specified method. |
Action | See the linked error message 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 subscriber, or it may have been administratively disabled. See the linked error message for more information. |
Action | Check the application(s) for 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 authorization to access the durable subscription. |
Action | Check the userID has the required access to the resources needed. See the linked error message for more information. |
Explanation | A problem was encountered interpreting the provided selector string. |
Action | Check the selector string and correct any errors. |
Explanation | A durable subscriber cannot be created because of a problem with the topic space. |
Action | See the linked error message for details. If the topic space did not exist, create it or use one that does exist. If the topic was a temporary one, use a non-durable subscriber or change to a permanent topic. |
Explanation | Another component detected an error during the execution of the specified method. |
Action | See the linked error message 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 | The destination object does not have sufficient information for the production and consumption of messages. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | The publish/subscribe broker profile topic mapping used to transfer the original publication from MQ does not contain a broker input queue. |
Action | Add the broker input queue name to the appropriate broker profile topic mapping. |
Explanation | The value provided is not allowed for the property specified. |
Action | Enter a value that is supported for the property. |
Explanation | The value provided is not allowed for the property specified. |
Action | Enter a value that is supported for the property. |
Explanation | An exception originated outside of user code while asynchronous delivery was running. |
Action | See the linked error message for more information. |
Explanation | The messaging engine to which the application is attached has been shut down. |
Action | This is a signal to the application to disconnect from the messaging engine. |
Explanation | A communications failure has resulted in the loss of the connection to the messaging engine. |
Action | See the linked error message 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 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | A JMS message has been received from a later release of the Application Server and has been given to an application. The application has then attempted to retrieve either the JMSDestination or the JMSReplyTo message header from the message. The message header field cannot be retrieved because one of its properties is not supported on this release. |
Action | Remove the unsupported property from the JMSDestination or JMSReplyTo used by the sending application. The unsupported property may have been specified directly by the sending application or may have been specified on the configuration of the JMS Queue. |
Explanation | The name-value pair element identified is malformed, possibly because it does not contain both a name and a value. |
Action | Check that the name-value pair element is 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 identified 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 URI that does not use a queue manager. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
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 | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | See any linked error message for more information. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/BdfL85. |
Explanation | The message producer has promised not to modify message payloads after setting them. Calls to certain methods on message objects are considered to break this promise. |
Action | Either modify the application code to remove the offending call, or change the administration option that indicates that the promise is in place. Note that disabling the administration option may result in reduced performance. |
Explanation | The message producer has promised not to modify message payloads after setting them. Only one call to BytesMessage.writeBytes(byte[] value) is allowed in this situation. |
Action | There are three actions available to remedy the problem: 1) modify the application code to remove the offending call, 2) call BytesMessage.clearBody() after the first call, or 3) change the administration option that indicates that the promise is in place. Note that disabling the administration option may result in reduced performance. |
Explanation | This method is not allowed to be called as per the JMS specification. For more details about the list of methods that are not permitted, refer to the JMS specification documentation. |
Action | Remove the call to the method. |