JMS Error Codes

This section describes error codes that can be returned by activities in the JMS palette.

BW-JMS-100000:  Invalid configuration data: JMS connection reference is not specified.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  JMS connection reference is not specified in configuration data.

  • Resolution:  Specify a valid JMS connection reference in activity configuration.

BW-JMS-100002:  Invalid configuration data: specfied connection reference not found in repository.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100003:  Invalid configuration data: JNDI context URL is not specified.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100004:  Invalid configuration data: JNDI initial context factory is not specified.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100005:  Could not create connection with JMS server.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100006:  Could not create a session to receive messages.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100007:  Could not create a reply session/producer.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error when attempting to create a reply producer [%1-configuration data].

  • Resolution:  Look at the exception for more information.

BW-JMS-100008:  JNDI lookup of queue name [%1] failed.

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100009:  Cannot retrieve queue with name [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Cannot retrieve queue with name [%1].

  • Resolution:  Make sure that the queue has been setup in your JMS provider.

BW-JMS-100010:  Error creating JNDI initial context [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Cannot create JNDI initial context [%1 - connection key data].

  • Resolution:  Look at the exception for more information.

BW-JMS-100011:  JNDI lookup of topic name [%1] failed.

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100012:  Cannot retrieve topic with name [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Cannot retrieve topic with name [%1].

  • Resolution:  Make sure that the topic has been setup in your JMS provider.

BW-JMS-100013:  Error creating dynamic queue with name [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Error creating dynamic queue with name [%1].

  • Resolution:  Look at the exception for more information. Also refer to your JMS provider documentation.

BW-JMS-100014:  Error creating dynamic topic with name [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Error creating dynamic topic with name [%1].

  • Resolution:  Look at the exception for more information. Also refer to your JMS provider documentation.

BW-JMS-100015:  Could not create queue message receiver.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error when attempting to create a queue receiver [%1-configuration data].

  • Resolution:  Look at the exception for more information.

BW-JMS-100016:  Could not create queue message receiver.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error when attempting to create a queue receiver [%1-Destination].

  • Resolution:  Look at the exception for more information.

BW-JMS-100017:  Could not create durable topic message subsriber.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100018:  Could not create topic message subsriber.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error when attempting to create a topic message subsriber.[%1-configuration data].

  • Resolution:  Look at the exception for more information.

BW-JMS-100019:  Could not create topic message subsriber.[%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error when attempting to create a topic message subsriber.[%1-Destination].

  • Resolution:  Look at the exception for more information.

BW-JMS-100020:  There was an error when attempting to receive a message.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error when attempting to receive a message.

  • Resolution:  Look at the exception for more information.

BW-JMS-100021:  There was an error in onMessage callback for a received message of type [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error in onMessage callback for a received message of type [%1].

  • Resolution:  Look at the exception for more information.

BW-JMS-100022:  Received a message of type [%1] but configured to receive messages of type [%2].

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100023:  There was an error while parsing the reply message.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error while parsing the reply message.

  • Resolution:  Look at the exception for more information.

BW-JMS-100024:  There was an error when attempting to confirm a message.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error when attempting to confirm a message.

  • Resolution:  Look at the exception for more information.

BW-JMS-100026:  JMS message type [%1] is not valid.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  JMS message type [%1] is not valid.

  • Resolution:  Internal error.

BW-JMS-100027:  Error creating temporary queue for reply.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Error creating temporary queue topic for reply.

  • Resolution:  Look at the exception for more information.

BW-JMS-100028:  Error creating temporary topic for reply.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Error creating temporary topic for reply.

  • Resolution:  Look at the exception for more information.

BW-JMS-100029:  Could not create a reply receiver.[Destination=%1]

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error when attempting to create a reply receiver.[Destination=%1].

  • Resolution:  Look at the exception for more information.

BW-JMS-100030:  There was an error when attempting to send a request message.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error when attempting to send a request message.

  • Resolution:  Look at the exception for more information.

BW-JMS-100031:  There was an unexpected error.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an unexpected error.

  • Resolution:  Look at the exception for more information.

BW-JMS-100032:  There was an unexpected error.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an unexpected error.

  • Resolution:  Look at the exception for more information.

BW-JMS-100033:  Unkown state in request/reply processing [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an unexpected error [%1-closure].

  • Resolution:  Look at the exception for more information.

BW-JMS-100034:  There was an error while cancelling.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error while cancelling.

  • Resolution:  Look at the exception for more information.

BW-JMS-100035:  Received a null reply message.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Received a null reply message.

  • Resolution:  Look at the exception for more information.

BW-JMS-100036:  Could not create a session to send request messages.[ConnectionKey=%1, Transacted=%2, AckMode=%3]

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100037:  Could not create a session to receive reply messages.[ConnectionKey=%1, Transacted=%2, AckMode=%3]

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100038:  Could not create a session to send messages.[ConnectionKey=%1, Transacted=%2, AckMode=%3]

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100039:  There was an unexpected error while sending a message.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an unexpected error while sending a message.

  • Resolution:  Look at the exception for more information.

BW-JMS-100040:  There was an unexpected error while sending a reply.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an unexpected error while sending a reply.

  • Resolution:  Look at the exception for more information.

BW-JMS-100041:  There was an internal error when attempting setReady.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an internal error when attempting setReady.

  • Resolution:  Look at the exception for more information.

BW-JMS-100042:  There was an error while sending a message.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error while sending a message.

  • Resolution:  Look at the exception for more information.

BW-JMS-100043:  There was an error while parsing a message.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error while parsing a message.

  • Resolution:  Look at the exception for more information.

BW-JMS-100044:  There was an error while parsing the JMS schema.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error while parsing the JMS schema.

  • Resolution:  This is an internal error.

BW-JMS-100045:  There was an error while parsing the JMS schema.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error while parsing the JMS schema.

  • Resolution:  This is an internal error.

BW-JMS-100046:  There was an error while parsing the JMS schema.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error while parsing the JMS schema.

  • Resolution:  This is an internal error.

BW-JMS-100047:  There was an error while parsing data to build a message: attributes are not allowed.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error while parsing data to build a messag: attributes are not allowed.

  • Resolution:  This is an internal error.

BW-JMS-100048:  There was an error while parsing data to build a message: mixed text not allowed.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  There was an error while parsing data to build a messag: mixed text not allowed.

  • Resolution:  This is an internal error.

BW-JMS-100049:  JMS message priority [%1] in input bind is not valid.

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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).

BW-JMS-100050:  Invalid JMS Application Properties [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100051:  Invalid message body schema specified [%1] [%2].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  The schema [%1] to define message body is not valid. See [%2-exception] for more details.

  • Resolution:  Check the message body schema specified.

BW-JMS-100052:  Invalid JMS message type specified [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  The JMS message type [%1] is not valid.

  • Resolution:  Pick a valid JMS message type.

BW-JMS-100053:  An internal error occured while processing configuration data [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  An internal error occured while processing configuration data. See [%1-exception] for more details.

  • Resolution:  Check the exception for more details.

BW-JMS-100054:  Invalid input data.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Input data is invalid. See the exception for more details.

  • Resolution:  Check activity input data.

BW-JMS-100055:  Error creating JMS message.

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100056:  Invalid configuration data: message body schema is not specified.

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100057:  Invalid configuration data: destination %1 name is not specified.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Invalid configuration data: destination name is not specified.

  • Resolution:  Specify name of the topic or queue destination in Configuration tab.

BW-JMS-100058:  Invalid configuration data: reply to is not specified.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Invalid configuration data: reply to is not specified.

  • Resolution:  Pick the reply target in Configuration tab.

BW-JMS-100059:  Cannot create connection factory in a provider-specific way.

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100060:  Invalid configuration data: message body schema is not specified in 'Input Editor' tab.

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100061:  Invalid configuration data: message body schema is not specified in 'Output Editor' tab.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Invalid configuration data: no schema specified for the reply message body in the Output Editor tab.

  • Resolution:  Specify a schema to represent the reply message body in the Output Editor tab.

BW-JMS-100062:  Invalid message body schema specified in 'Input Editor' tab [%1] [%2].

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100063:  Invalid message body schema specified in 'Output Editor' tab [%1] [%2].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  The schema [%1] to define the reply message body in the Output Editor tab is not valid. See [%2-exception] for more details.

  • Resolution:  Check the reply message body schema specified in the Output Editor tab.

BW-JMS-100064:  Could not decrypt password.[%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • 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.

BW-JMS-100065:  Can't create XAResource.Check if the ConnectionFactory [%1] is XA enabled.

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  Can't create XAResource.Check if the ConnectionFactory [%1] is XA enabled.

  • Resolution:  Check if the ConnectionFactory [%1] is XA enabled.

BW-JMS-100066:  JNDI lookup failed for queue with name [%1].

  • Role:  errorRole

  • Category:  BW-Plugin

  • Description:  JNDI lookup failed for queue with name [%1].

  • Resolution:  Look at the exception for more information. Also refer to your JMS provider documentation.