Description: JMS connection reference is not specified in configuration data.
Resolution: Specify a valid JMS connection reference in activity configuration.
Description: The specified JMS connection reference is not found in repository. [%1-connection reference].
Resolution: Make sure that the connection reference specified in activity configuration refers to a valid shared JMS connection.
Description: JNDI context URL is not specified in the shared JMS connection. [%1-shared connection data].
Resolution: Specify a valid JNDI context URL in the specified shared JMS connection.
Description: JNDI initial context factory is not specified in the shared JMS connection. [%1-shared connection data].
Resolution: Specify a valid JNDI initial context factory in the specified shared JMS connection.
Description: There was an error when attempting to create a connection with JMS server[%1-connection key data].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a session to receive messages [%1-configuration data].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a reply producer [%1-configuration data].
Resolution: Look at the exception for more information.
Description: JNDI lookup of queue name [%1] failed.
Resolution: Look at the exception for more information. Make sure that the queue has been setup in your JMS provider
Description: Cannot retrieve queue with name [%1].
Resolution: Make sure that the queue has been setup in your JMS provider.
Description: Cannot create JNDI initial context [%1 - connection key data].
Resolution: Look at the exception for more information.
Description: JNDI lookup of topic name [%1] failed.
Resolution: Look at the exception for more information. Make sure that the topic has been setup in your JMS provider
Description: Cannot retrieve topic with name [%1].
Resolution: Make sure that the topic has been setup in your JMS provider.
Description: Error creating dynamic queue with name [%1].
Resolution: Look at the exception for more information. Also refer to your JMS provider documentation.
Description: Error creating dynamic topic with name [%1].
Resolution: Look at the exception for more information. Also refer to your JMS provider documentation.
Description: There was an error when attempting to create a queue receiver [%1-configuration data].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a queue receiver [%1-Destination].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a durable topic message subsriber.[%1-configuration data].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a topic message subsriber.[%1-configuration data].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a topic message subsriber.[%1-Destination].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to receive a message.
Resolution: Look at the exception for more information.
Description: There was an error in onMessage callback for a received message of type [%1].
Resolution: Look at the exception for more information.
Description: The message type of received message does not match the configured message type.
Resolution: Make sure that the JMS message type is configured correctly in the activity configuration.
Description: There was an error while parsing the reply message.
Resolution: Look at the exception for more information.
Description: There was an error when attempting to confirm a message.
Resolution: Look at the exception for more information.
Description: JMS message type [%1] is not valid.
Resolution: Internal error.
Description: Error creating temporary queue topic for reply.
Resolution: Look at the exception for more information.
Description: Error creating temporary topic for reply.
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a reply receiver.[Destination=%1].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to send a request message.
Resolution: Look at the exception for more information.
Description: There was an unexpected error.
Resolution: Look at the exception for more information.
Description: There was an unexpected error.
Resolution: Look at the exception for more information.
Description: There was an unexpected error [%1-closure].
Resolution: Look at the exception for more information.
Description: There was an error while cancelling.
Resolution: Look at the exception for more information.
Description: Received a null reply message.
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a session to send request messages [ConnectionKey=%1, Transacted=%2, AckMode=%3].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a session to send reply messages [ConnectionKey=%1, Transacted=%2, AckMode=%3].
Resolution: Look at the exception for more information.
Description: There was an error when attempting to create a session to send messages [ConnectionKey=%1, Transacted=%2, AckMode=%3].
Resolution: Look at the exception for more information.
Description: There was an unexpected error while sending a message.
Resolution: Look at the exception for more information.
Description: There was an unexpected error while sending a reply.
Resolution: Look at the exception for more information.
Description: There was an internal error when attempting setReady.
Resolution: Look at the exception for more information.
Description: There was an error while sending a message.
Resolution: Look at the exception for more information.
Description: There was an error while parsing a message.
Resolution: Look at the exception for more information.
Description: There was an error while parsing the JMS schema.
Resolution: This is an internal error.
Description: There was an error while parsing the JMS schema.
Resolution: This is an internal error.
Description: There was an error while parsing the JMS schema.
Resolution: This is an internal error.
Description: There was an error while parsing data to build a messag: attributes are not allowed.
Resolution: This is an internal error.
Description: There was an error while parsing data to build a messag: mixed text not allowed.
Resolution: This is an internal error.
Description: JMS message priority [%1] in input bind is not valid.
Resolution: A valid JMS message priority must be a number between 0 and 9 (inclusive).
Description: JMS application properties are not valid. See [%1-exception] for more details.
Resolution: Verify that JMS application properties are correct. This can be done by using 'validate for deployment' feature of the Designer.
Description: The schema [%1] to define message body is not valid. See [%2-exception] for more details.
Resolution: Check the message body schema specified.
Description: The JMS message type [%1] is not valid.
Resolution: Pick a valid JMS message type.
Description: An internal error occured while processing configuration data. See [%1-exception] for more details.
Resolution: Check the exception for more details.
Description: Input data is invalid. See the exception for more details.
Resolution: Check activity input data.
Description: There was an error while creating a JMS message. See the exception for more details.
Resolution: Check activity input data. See the exception for more details.
Description: Invalid configuration data: no schema specified for message body.
Resolution: Specify a schema to represent the message body in the 'Input Editor' or 'Output Editor' tab.
Description: Invalid configuration data: destination name is not specified.
Resolution: Specify name of the topic/queue destination in 'Configuration' tab.
Description: Invalid configuration data: reply to is not specified.
Resolution: Pick the reply target in 'Configuration' tab.
Description: Cannot create connection factory in a provider-specific way. Use JNDI lookup instead.
Resolution: Please use TIBCO Enterprise for JMS. Otherwise use JNDI to lookup connection factory.
Description: Invalid configuration data: no schema specified for the request message body in 'Input Editor' tab.
Resolution: Specify a schema to represent the request message body in the 'Input Editor' tab.
Description: Invalid configuration data: no schema specified for the reply message body in 'Output Editor' tab.
Resolution: Specify a schema to represent the reply message body in the 'Output Editor' tab.
Description: The schema [%1] to define the request message body in 'Input Editor' tab is not valid. See [%2-exception] for more details.
Resolution: Check the request message body schema specified in 'Input Editor' tab.
Description: The schema [%1] to define the reply message body in 'Output Editor' tab is not valid. See [%2-exception] for more details.
Resolution: Check the reply message body schema specified in 'Output Editor' tab.
Description: There was an error while decrypting a password. See [%1-exception] for more details.
Resolution: Make sure that the password stored in the repository is not in clear text.
Description: Can't create XAResource.Check if the ConnectionFactory [%1] is XA enabled.
Resolution: Check if the ConnectionFactory [%1] is XA enabled.
Description: JNDI lookup failed for queue with name [%1].
Resolution: Look at the exception for more information. Also refer to your JMS provider documentation.
