Message Reference > J Message Codes > JMS Messages
  

JMS Messages

JMS_1001 Failed to connect to a JNDI provider: <error message>.

Explanation:
The Integration Service could not connect to a JNDI provider.
User Response:
Check the additional error message for more information.

JMS_1002 The object <object name> looked up from JNDI is not a Destination object.

Explanation:
The value for JMS Destination in the JMS application connection is not valid.
User Response:
Enter a valid value for JMS Destination. Use a value that exists in the JNDI configuration.

JMS_1003 Failed to set JMS exception listener: <error message>.

Explanation:
The Integration Service cannot set a listener for JMS exceptions.
User Response:
Check the additional error message for more information.

JMS_1004 The object <object name> is not a QueueConnectionFactory object in JNDI.

Explanation:
The value for JMS Connection Factory Name in the JMS application connection is not valid. The name of the connection factory is not a queue connection factory name in the JNDI configuration.
User Response:
Enter a valid queue connection factory name for the JMS Connection Factory Name attribute in the application connection.

JMS_1005 The object <object name> is not a TopicConnectionFactory object in JNDI.

Explanation:
The value for JMS Connection Factory Name in the JMS application connection is not valid. The name of the connection factory is not a topic connection factory name in the JNDI configuration.
User Response:
Enter a valid topic connection factory name for the JMS Connection Factory Name attribute in the application connection.

JMS_1006 The destination object is not a Queue object.

Explanation:
The value for the JMS Destination attribute in the JMS application connection is not a valid queue name. However, the value for JMS Destination Type in the application connection is QUEUE.
User Response:
Provide a valid queue name for the JMS Destination attribute. Make sure the queue name exists in the JNDI configuration.
Change the Destination Type to TOPIC if the value for the JMS Destination attribute is a topic.

JMS_1007 The destination object is not a Topic object.

Explanation:
The value for the JMS Destination attribute in the JMS application connection is not a valid topic. However, the value for JMS Destination Type in the application connection is TOPIC.
User Response:
Provide a valid topic for the JMS Destination attribute. Make sure the topic exists in the JNDI configuration.
Change the JMS Destination Type to QUEUE if the value for the JMS Destination attribute is a queue.

JMS_1008 Failed to create JMS connection: <error message>.

Explanation:
The Integration Service cannot connect to JMS.
User Response:
Check the additional error message for more information.

JMS_1009 Failed to create JMS session: <error message>.

Explanation:
The Integration Service cannot start a JMS session.
User Response:
Check the additional error message for more information.

JMS_1010 Failed to create JMS connection consumer: <error message>.

Explanation:
The Integration Service cannot create a JMS connection consumer.
User Response:
Check the additional error message for more information.

JMS_1011 Failed to start JMS connection: <error message>.

Explanation:
The Integration Service could not initialize a JMS connection.
User Response:
Check the additional error message for more information.

JMS_1012 Failed to stop JMS connection: <error message>.

Explanation:
The Integration Service could not stop the JMS connection.
User Response:
Check the additional error message for more information.

JMS_1013 Failed to close JMS connection: <error message>.

Explanation:
The Integration Service could not close the JMS connection.
User Response:
Check the additional error message for more information.

JMS_1014 Failed to close JNDI connection: <error message>.

Explanation:
The Integration Service could not close the JNDI connection.
User Response:
Check the additional error message for more information.

JMS_1015 Failed to look up object <object name> from JNDI.

Explanation:
The specified value in the JMS application connection is not valid.
User Response:
Make sure the attribute value in the JMS application is valid. Make sure the value exists in the JNDI configuration.
Explanation:
The JNDI server may not be running.
User Response:
Verify that the JNDI server is running. If necessary, start the server.

JMS_1018 Cannot find message type from metadata extension.

Explanation:
JMS cannot find the message type represented in the source or target definition. The repository may contain inconsistencies.
User Response:
Contact Informatica Global Customer Support.

JMS_1019 Cannot find JMS connection.

Explanation:
There may be no application connection specified for the Source Qualifier or target in the session properties.
User Response:
Specify a value for the application connection in the session properties.
Explanation:
The repository may contain inconsistencies.
User Response:
Contact Informatica Global Customer Support.

JMS_1020 Failed to create the message consumer: <error message>.

Explanation:
JMS could not create the message consumer.
User Response:
Check the additional error message for more information.

JMS_1021 Failed to create the message consumer because of conflicting JMS session and JMS connection objects.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

JMS_1022 Failed to get the JMS destination <destination>. Reason: <error message>.

Explanation:
The specified value for the JMS Destination attribute in the JMS application connection does not exist in the JNDI configuration.
User Response:
Configure JNDI to include the value. Or, use a value that exists in the JNDI configuration.

JMS_1023 Failed to get the Queue Connection Factory <queue connection factory>. Reason: <error message>.

Explanation:
The Integration Service cannot retrieve the queue connection factory from JNDI to connect to JMS. The value for the JMS Connection Factory Name attribute may not be valid.
User Response:
Make sure the value for the JMS Connection Factory Name attribute is valid. Also, make sure the value exists in the JNDI configuration.
Explanation:
The JNDI server may not be running.
User Response:
Verify that the JNDI server is running. If necessary, start the JNDI server.

JMS_1024 Failed to get the Topic Connection Factory <topic connection factory>. Reason: <error message>.

Explanation:
The Integration Service cannot retrieve the topic connection factory from JNDI to connect to JMS. The value for the JMS Connection Factory Name attribute may not be valid.
User Response:
Make sure the value for the JMS Connection Factory Name attribute is valid. Also, make sure the value exists in the JNDI configuration.
Explanation:
The JNDI server may not be running.
User Response:
Verify that the JNDI server is running. If necessary, start the JNDI server.

JMS_1026 The file jndi.properties is not found. No additional SSL related properties are used at runtime.

Explanation:
The Integration Service could not run the session with SSL, because it could not find the JNDI.properties file.
User Response:
To run the session with SSL, add the JNDI.properties file with the necessary SSL configuration to the <INFA_HOME>/server/infa_shared/SrcFiles directory.

JMS_2002 Error in getting the session extension information for Source Qualifier <Source Qualifier name>.

Explanation:
The Integration Service cannot read the session properties. The repository may contain inconsistencies.
User Response:
Contact Informatica Global Customer Support.

JMS_2025 An error occurred while processing the message received by Source Qualifier <Source Qualifier name>. Reason: <error message>.

Explanation:
The Integration Service could not process a message.
User Response:
Check the additional error message for more information.

JMS_2026 JMS error occurred while processing the message received by Source Qualifier <Source Qualifier name>. Reason: <error message>.

Explanation:
The Integration Service encountered a JMS error while processing a message.
User Response:
Check the additional error message for more information.

JMS_2027 The data received is too large for processing the field <field name> by Source Qualifier <Source Qualifier name>. Reason: <error message>.

Explanation:
The Integration Service cannot process data for the specified field. The data is too large.
User Response:
Check the additional error message for more information.

JMS_2028 The message received by Source Qualifier <Source Qualifier name> does not match the body definition.

Explanation:
The Integration Service received a message whose body fields do not match the source definition. The Integration Service rejected the message.
User Response:
Make sure the body fields of the messages the Integration Service reads from the source match the format of the source definition. Otherwise, the Integration Service rejects the messages.

JMS_2029 The Source Qualifier <Source Qualifier name> encountered an error in closing the consumer. Reason: <error message>.

Explanation:
The Integration Service could not close the JMS consumer.
User Response:
Check the additional error message for more information.

JMS_2032 Unknown error occurred while writing the data to the DTM buffer by Source Qualifier <Source Qualifier name>. Reason: <error message>.

Explanation:
The Integration Service encountered an unknown error.
User Response:
Check the additional error message for more information.

JMS_2035 The partition #<number> of Source Qualifier <Source Qualifier name> failed to get cache coordinator for recovery.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

JMS_2036 File cache folder is not provided. Please enter a file cache folder.

Explanation:
You enabled message recovery for the session, but did not specify a file cache folder.
User Response:
In the session properties, enter a file cache folder.

JMS_2037 Failed to create storage information object for Guaranteed Message Delivery. Reason: <error message>.

Explanation:
You ran a session with message recovery enabled for the session. The session failed when the Integration Service tried to write data to the recovery cache.
User Response:
Check the additional error message for more information.

JMS_2038 Failed to register recovery cache. Reason: <error message>.

Explanation:
The Integration Service could not register the session for message recovery.
User Response:
Check the additional error message for more information.

JMS_2041 Failed to recover data from recovery cache. Reason: <error message>.

Explanation:
During a recovery session, the Integration Service could not read messages from the recovery cache.
User Response:
Check the additional error message for more information.

JMS_2042 Unknown error encountered while recovering data from recovery cache.

Explanation:
During a recovery session, the Integration Service encountered an unknown error. The cache might be corrupt.
User Response:
Remove the cache file. Run the session again.

JMS_2043 Failed to write data to recovery cache. Reason: <error message>.

Explanation:
The Integration Service could not write data to the recovery cache.
User Response:
Check the additional error message for more information.

JMS_2044 Source Qualifier <Source Qualifier name> encountered an error while acknowledging the message. Reason: <error message>.

Explanation:
The Integration Service encountered an error acknowledging a source message.
User Response:
Check the additional error message for more information.

JMS_2046 A data conversion error happened while processing the message for field <field name> in the Source Qualifier <Source Qualifier name>.

Explanation:
The Integration Service could not process the specified field because of a data conversion error. The datatype for the field is not compatible with the datatype for the corresponding field in the source definition.
User Response:
Make sure that the datatype for the field in the JMS source messages is compatible with the datatype in the source definition.

JMS_2047 Message listener cannot be set: <error message>.

Explanation:
The Integration Service cannot set the JMS message listener.
User Response:
Verify that the JMS settings are correct. Check the additional error message for more information.

JMS_2048 Error closing JMS session: <error message>.

Explanation:
The JMS session cannot close.
User Response:
Check the additional error message for more information.

JMS_2050 Source Qualifier <Source Qualifier name> encountered error while receiving the JMS message. Reason: <error message>.

Explanation:
The Integration Service encountered a JMS error.
User Response:
Check the additional error message for more information.

JMS_2051 The requested datatypes do not match the data written to the recovery cache. The cache may be corrupt.

Explanation:
The message recovery cache file may contain inconsistencies.
User Response:
Manually delete the corrupted cache file.

JMS_2052 The jms.jar library could not be loaded.

Explanation:
The Integration Service could not start the session because it could not load the jms.jar file.
User Response:
Verify that the jms.jar file is in the Integration Service /bin/javlib directory.

JMS_2063 The Integration Service fails a JMS real-time session that is enabled for recovery and contains multiple partitions.

Explanation:
A JMS real-time session that contains multiple partitions cannot be enabled for recovery.
User Response:
Delete the partitions or do not enable the session for recovery.

JMS_2064 Source Qualifier <Source Qualifier name> received <number of recovery messages received> out of <number of possible recovery messages> possible recovery messages. The Integration Service processed the messages in the previous session and will delete them through partition <partition ID>.

User Response:
Restart the session. If the problem persists, contact Informatica Global Customer Support.

JMS_2065 Source Qualifier <Source Qualifier name> received <number of recovery messages received> out of <number of possible recovery messages> possible recovery messages. The Integration Service did not process the messages in the previous session and will write the messages through partition <partition ID>.

User Response:
Restart the session. If the problem persists, contact Informatica Global Customer Support.

JMS_3003 Cannot create writer connection: <error message>.

Explanation:
The Integration Service cannot connect to JMS to write target messages.
User Response:
Check the additional error message for more information.

JMS_3004 Cannot close connection: <error message>.

Explanation:
The Integration Service cannot close the JMS connection.
User Response:
Check the additional error message for more information.

JMS_3005 Cannot close JMS session: <error message>.

Explanation:
The JMS session cannot close.
User Response:
Check the additional error message for more information.

JMS_3006 Cannot commit JMS session: <error message>.

Explanation:
The Integration Service cannot commit messages to the JMS target.
User Response:
Check the additional error message for more information.

JMS_3007 Cannot roll back JMS session: <error message>.

Explanation:
The Integration Service could not roll back messages from the target.
User Response:
Check the additional error message for more information.

JMS_3008 Cannot create JMS message object: <error message>.

Explanation:
Internal error.
Out of memory error.
User Response:
Check the additional error message for more information.
Contact Informatica Global Customer Support.

JMS_3009 Cannot create message writer: <error message>.

Explanation:
Internal error.
Out of memory error.
User Response:
Check the additional error message for more information.
Contact Informatica Global Customer Support.

JMS_3013 Cannot create a message object because an invalid message type is given.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

JMS_3014 The field <field name> is not a valid JMS target field.

Explanation:
The repository may contain inconsistencies.
User Response:
Contact Informatica Global Customer Support.

JMS_3015 An invalid row type was encountered. JMS writer will publish a message if the row type is INSERT, UPDATE, and DELETE.

Explanation:
The row type for the source rows is Data Driven, but must be Insert, Update, or Delete.
User Response:
From the Properties tab in the session properties, set the value for the Treat Source Rows As property to Insert, Update, or Delete.

JMS_3016 JMS writer encountered an unknown row type error.

Explanation:
The repository may contain inconsistencies.
User Response:
Contact Informatica Global Customer Support.

JMS_3017 The value provided for <property name> in the JMS connection <connection name> is invalid. Reason: <error message>.

Explanation:
The value for the specified property is not valid.
User Response:
Provide a valid value for the property in the session properties.

JMS_3018 JMS writer encountered a JMS exception while field <field name> was being processed: <error message>.

Explanation:
The Integration Service encountered a JMS exception while processing the specified field. The Integration Service increased the error threshold as a result of the error.
User Response:
Check the additional error message for more information.

JMS_3020 JMS writer encountered a data conversion error while field <field name> was being processed.

Explanation:
The Integration Service could not convert the data for the specified field when writing messages to the JMS target. The field contains incompatible datatypes. The Integration Service rejected the field.
User Response:
Make sure the datatypes in the target definition are compatible with JMS datatypes.

JMS_3021 JMS writer encountered a general exception: <error message>.

Explanation:
The JMS writer encountered an error.
User Response:
Check the additional error message for more information.

JMS_3022 JMS writer encountered a general error: <error message>.

Explanation:
The JMS writer encountered an error.
User Response:
Check the additional error message for more information.

JMS_3023 JMS exception happened in JMS provider: <error message>.

Explanation:
The target JMS provider encountered an error.
User Response:
Check the additional error message for more information.

JMS_3024 Invalid datatype ID: <error message>.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

JMS_3025 JMS writer received NULL for the field <field name>, which is set to Not Null. The message will be rejected.

Explanation:
The specified field is set to Not Null in the target definition for the mapping.
User Response:
Edit the target definition in the Designer, and clear the Not Null option for the field to prevent messages with a NULL value from being rejected.

JMS_3026 JMS writer encounters a JMS exception: <error message>.

Explanation:
The Integration Service encountered a JMS error when writing messages to the target.
User Response:
Check the additional error message for more information. If the additional error message is an MQSeries JMS message regarding an invalid value for the JMSTimeToLive field in the target, it prints the value for field multiplied by 1,000. For example, if the JMSTimeToLive value in the target is -1, the MQSeries JMS message prints -1,000.

JMS_3027 JMS writer encountered an out of memory error.

Explanation:
JVM is out of memory. As a result, the PowerCenter session failed.
User Response:
Increase the memory for JVM. Then restart the session.

JMS_3028 JMS writer encountered an error in getting the default JMSReplyTo object <object name> from JNDI. Reason: <error message>.

Explanation:
The Integration Service could not obtain a value for JMSReplyTo from JNDI.
User Response:
Check the additional error message for more information.

JMS_3029 JMS writer encountered an error in processing the data for the field <field name> in the target <target name>. Reason: <error message>.

Explanation:
The Integration Service could not process data for the specified field in the target.
User Response:
Check the additional error message for more information.

JMS_3030 The jms.jar library could not be loaded.

Explanation:
The file jms.jar is not available in the <PowerCenter Installation Directory>/server/bin/javalib directory.
User Response:
Copy jms.jar to the <PowerCenter Installation Directory>/server/bin/javalib directory.

JMS_3031 The Integration Service cannot guarantee that it will process messages only once. Some messages may be lost or duplicated.

Explanation:
Integration Service did not register the JMS writer with the cache coordinator.
User Response:
For relational targets, verify that the recovery table exists and the table creation privilege to the database user name is configured in the target database connection. For queue targets, verify that the recovery queue exists.

JMS_3033 The Integration Service failed to write the recovery state to the recovery <recovery destination type>, recovery destination <recovery destination name>, connection factory <connection factory name>. Reason: <reason for error>.

User Response:
Review the reason for error and make any appropriate changes.

JMS_3034 Field <field name> for target <target name> can be projected if IsDestinationNameDynamic is set to true in session properties.

Explanation:
The JMS target is configured to have a static destination name. When the destination name is static, the Integration Service uses the destination name from the application connection. You cannot project the destination name in the JMS target.
User Response:
Enable IsDestinationNameDynamic in session properties, or remove the link to the destination in the JMS target.