Created a non-transactional session for JMS provider <insert_1>.
Severity
0 : Information
BIP12003
Created a transactional session for JMS provider <insert_1>.
Severity
0 : Information
BIP12004
Created an XA session for JMS provider <insert_1>.
Severity
0 : Information
BIP12005
Opened queue <insert_1> for receiving messages.
Severity
0 : Information
Explanation
The message selector <insert_2> is used to filter messages.
BIP12006
Opened queue <insert_1> for browsing messages.
Severity
0 : Information
Explanation
The message selector <insert_2> is used to filter messages.
BIP12007
Opened topic <insert_1> for subscription.
Severity
0 : Information
BIP12008
Received from queue <insert_1>.
Severity
0 : Information
BIP12009
Browsed from queue <insert_1>.
Severity
0 : Information
BIP12010
Received from topic <insert_1>.
Severity
0 : Information
BIP12011
Opened queue <insert_1> for sending messages.
Severity
0 : Information
BIP12012
Opened topic <insert_1> for publishing messages.
Severity
0 : Information
BIP12013
Sent to queue <insert_1>.
Severity
0 : Information
BIP12014
Published to topic <insert_1>.
Severity
0 : Information
BIP12015
Waiting for a message on queue <insert_1>.
Severity
0 : Information
BIP12016
Timed out waiting for message on queue <insert_1>.
Severity
0 : Information
BIP12017
Sent to backout queue <insert_1>.
Severity
20 : Error
Explanation
The node was unable to process a JMS message. The exception text is: <insert_2>.
Response
Investigate the cause of the message failure.
BIP12018
Failed to connect to JMS provider <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
The node tries to reconnect to the JMS provider, unless the message flow is shutting down. Check that the JMS provider is available, and investigate the cause of the failure.
BIP12019
Failed to create a non-transactional session for JMS provider <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Verify that the JMS provider is available, and that sufficient resources have been allocated. Investigate the cause of the failure.
BIP12020
Failed to create a transactional session for JMS provider <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Verify that the JMS provider is available, and that sufficient resources have been allocated. Investigate the cause of the message failure.
BIP12021
Failed to create an XA session for JMS provider <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Verify that the JMS provider is available, and that sufficient resources have been allocated. Investigate the cause of the message failure.
BIP12022
Failed to open queue <insert_1> for receiving messages.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Please check the message selector syntax if you have used selectors for filtering messages. Verify that the source queue exists. Investigate the cause of the JMS Exception. If the problem persists, contact the vendor of the JMS provider.
BIP12023
Failed to open queue <insert_1> for browsing messages.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Please check the message selector syntax if you have used selectors for filtering messages. Verify that the source queue exists. Investigate the cause of the JMS Exception. If the problem persists, contact the vendor of the JMS provider.
BIP12024
Failed to subscribe to topic <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>
Response
Please check the message selector syntax if you have used selectors for filtering messages. Verify that the source queue exists. Investigate the cause of the JMS Exception. If the problem persists, contact the vendor of the JMS provider.
BIP12025
Failed to receieve message from queue <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Verify that the source queue exists and is not get-inhibited.
BIP12026
Failed to browse message from queue <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Verify that the source queue exists and is not get-inhibited.
BIP12027
Failed to receive message from topic <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>
Response
Verify that the topic exists.
BIP12028
Failed to open queue <insert_1> for sending messages.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Please verify that the destination queue exists.
BIP12029
Failed to open topic <insert_1> for publishing messages.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Please verify that the destination topic exists.
BIP12030
Failed to send message to queue <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is: <insert_2>.
Response
Please verify that the destination queue exists and is not put-inhibited.
BIP12031
Failed to publish message on topic <insert_1>.
Severity
20 : Error
Explanation
The JMS Exception text is : <insert_2>.
Response
Please verify that the destination topic exists.
BIP12032
Backout destination is not configured.
Severity
20 : Error
Explanation
The node was unable to process a JMS message because of errors, and cannot send it to a backout destination because none was configured.
Response
Investigate the cause of the message failure. Consider setting Backout Destination and Backout Threshold properties for the node.
BIP12033
Failed to verify XA compliance of the JMS provider <insert_1>.
Severity
20 : Error
Response
Modify the node attribute and redeploy, or enable XA-Compliant transaction coordination by setting the JMSProviders configurable service attribute 'jmsProviderXASupport' to 'true'.
BIP12034
Failed to find JNDI definition for connection factory <insert_1>.
Severity
20 : Error
Explanation
The node cannot obtain a JNDI Administered Object, because some of the values specified are incorrect. The JMS Exception text is: <insert_2>.
Response
Check the JNDI Administered configuration for the JMS provider used by the node.
Either:
Modify the JNDI Administered objects and rebuild the bindings
or
Change the Configurable Service attributes associated with this JMS Provider and restart the integration server.
or
Change the node attributes and redeploy the message flow.
BIP12035
Failed to find JNDI definition for source queue <insert_1>.
Severity
20 : Error
Explanation
The node cannot obtain a JNDI Administered Object, because some of the values specified are incorrect. The JMS Exception text is: <insert_2>.
Response
Check the JNDI Administered configuration for the JMS provider used by the node.
Either:
Modify the JNDI Administered objects and rebuild the bindings
or
Change the Configurable Service attributes associated with this JMS Provider and restart the integration server.
or
Change the node attributes and redeploy the message flow.
BIP12036
Failed to find JNDI definition for destination queue <insert_1>.
Severity
20 : Error
Explanation
The node cannot obtain a JNDI Administered Object, because some of the values specified are incorrect. The JMS Exception text is: <insert_2>.
Response
Check the JNDI Administered configuration for the JMS provider used by the node.
Either:
Modify the JNDI Administered objects and rebuild the bindings
or
Change the Configurable Service attributes associated with this JMS Provider and restart the integration server.
or
Change the node attributes and redeploy the message flow.
BIP12037
Failed to find JNDI definition for reply-to-destination <insert_1>.
Severity
20 : Error
Explanation
The node cannot obtain a JNDI Administered Object, because some of the values specified are incorrect. The JMS Exception text is: <insert_2>.
Response
Check the JNDI Administered configuration for the JMS provider used by the node.
Either:
Modify the JNDI Administered objects and rebuild the bindings
or
Change the Configurable Service attributes associated with this JMS Provider and restart the integration server.
or
Change the node attributes and redeploy the message flow.
BIP12038
Failed to find JNDI definition for backout queue <insert_1>.
Severity
20 : Error
Explanation
The node cannot obtain a JNDI Administered Object, because some of the values specified are incorrect. The JMS Exception text is: <insert_2>.
Response
Check the JNDI Administered configuration for the JMS provider used by the node.
Either:
Modify the JNDI Administered objects and rebuild the bindings
or
Change the Configurable Service attributes associated with this JMS Provider and restart the integration server.
or
Change the node attributes and redeploy the message flow.
BIP12039
Failed to parse message because the message type is not valid for the message domain.
Severity
20 : Error
Explanation
The JMS Message received by the node is not a valid type for the message domain. The message will be delivered to the failure terminal of the node or rolled back if a failure path is not configured. The exception text is <insert_1>.
Response
Either reconfigure the JMSInput node to change the expected message domain, or modify the value of the JMSType header in the JMS Message.
BIP12040
Failed to parse message because the message is badly formed.
Severity
20 : Error
Explanation
The node was unable to parse the received JMS Message because it was corrupted or badly formed. The exception text is <insert_1>.
Response
Investigate the cause of the badly formed JMS Message.
BIP12041
Failed to generate JMS message.
Severity
20 : Error
Explanation
The node was unable to set either header or payload data to the JMS output message because it was either badly formed or in an unexpected type. The exception text is <insert_1>.
Response
If possible, turn on service trace and investigate the cause of the badly formed data.
BIP12042
Failed to acknowledge JMS message.
Severity
20 : Error
Explanation
The node was unable to acknowledge a JMS message on the JMS session. The exception text is <insert_1>.
Response
Investigate the cause of the JMS Exception.
BIP12043
Failed to find configurable service <insert_1>.
Severity
20 : Error
Explanation
The node cannot obtain a configurable service, because it does not exist.
Response
Create the JMS Provider configurable service associated with this node and restart the integration node.
BIP12050
Received the file <insert_1>.
Severity
0 : Information
Explanation
The IBM Sterling Connect:Direct resource manager received the file <insert_1> from the primary Connect:Direct server (PNODE) <insert_2> which was sent to the secondary Connect:Direct server (SNODE) <insert_3>. The correlating Connect:Direct process is <insert_4>, process number <insert_5>. You can use the Connect:Direct statistics to get further information about the process.
BIP12051
Ignored an inbound transfer with the filepath <insert_1>.
Severity
0 : Information
Explanation
The IBM Sterling Connect:Direct resource manager ignored an inbound transfer from the primary Connect:Direct server (PNODE) <insert_2>, which was sent to the secondary Connect:Direct server (SNODE) <insert_3>. This happened, because no CDInput node specified filter properties to match the filepath <insert_1> of the transfer. The correlating Connect:Direct process is <insert_4>, process number <insert_5>. You can use the Connect:Direct statistics to get further information about the process.
Response
If this was unexpected, edit the filter properties of a CDInput node to match the filepath of the transfer, in order to process the file.
BIP12052
Read a record from file <insert_1>.
Severity
0 : Information
Explanation
The CDInput node <insert_2> recognized a record in the file <insert_1> and propagated a separate message from it.
BIP12053
Read the whole file <insert_1>.
Severity
0 : Information
Explanation
The CDInput node <insert_2> treated the whole received file <insert_1> as one record, and propagated a message from it.
BIP12054
Finished reading file <insert_1> and took no further action.
Severity
0 : Information
Explanation
The CDInput node <insert_2> finished reading the file <insert_1> and left it in the input directory.
BIP12055
Finished reading file <insert_1> and deleted the file.
Severity
0 : Information
Explanation
The CDInput <insert_2> node finished reading the file <insert_1> and deleted the file.
BIP12056
Finished reading file <insert_1> and archived the file.
Severity
0 : Information
Explanation
The CDInput node <insert_2> finished reading the file <insert_1> and archived the file by adding a timestamp to the file.
BIP12057
Sent the file <insert_1>.
Severity
0 : Information
Explanation
The CDOutput node <insert_6> has successfully sent a command to the primary IBM Sterling Connect:Direct server (PNODE) <insert_3> to transfer the file <insert_1> to the secondary IBM Sterling Connect:Direct server (SNODE) <insert_2>. The correlating Connect:Direct process is <insert_4>, process number <insert_5>. You can use the Connect:Direct statistics to get further information about the process.
BIP12058
Wrote a message to the file <insert_1>.
Severity
0 : Information
Explanation
The CDOutput <insert_2> node wrote a message to the file <insert_1>.
BIP12059
Failed to connect to server on hostname <insert_1>, attempting to reconnect.
Severity
20 : Error
Explanation
IBM Integration Bus failed to connect and is trying to reconnect to the IBM Sterling Connect:Direct server on hostname <insert_1> using port <insert_2> and username <insert_3>. Reason: <insert_4>. New connection attempts will not be logged again until a successful connection is established.
BIP12060
Connected to server <insert_1>; waiting for transfers.
Severity
0 : Information
Explanation
The IBM Sterling Connect:Direct resource manager is connected to the Connect:Direct server <insert_1> and is waiting for transfers. A poll for new transfers happens every second but this message will not be logged again.
BIP12061
Started processing file <insert_1>.
Severity
0 : Information
Explanation
The CDInput node <insert_2> started processing the file <insert_1>.
BIP12062
Lost connection to <insert_1>.
Severity
20 : Error
Explanation
Lost connection to <insert_1>.
BIP12063
Established connection to <insert_1>.
Severity
0 : Information
Explanation
Established connection to <insert_1>.
BIP12064
Sent data to <insert_1>.
Severity
0 : Information
Explanation
Sent data to <insert_1>.
BIP12065
Received data from <insert_1>.
Severity
0 : Information
Explanation
Received data from <insert_1>.
BIP12066
Waiting for data from <insert_1>.
Severity
0 : Information
Explanation
Waiting for data from <insert_1>.
BIP12067
Failed to connect to <insert_1>.
Severity
20 : Error
Explanation
Failed to connect to <insert_1>.
BIP12068
<insert_1>1
Severity
0 : Information
Explanation
<insert_1>1
BIP12069
<insert_1>1
Severity
10 : Warning
Explanation
<insert_1>1
BIP12070
<insert_1>1
Severity
20 : Error
Explanation
<insert_1>1
BIP12071
Retrying to connect to <insert_1>.
Severity
10 : Warning
Explanation
Retrying to connect to <insert_1>.
BIP12072
Measured rate of <insert_1> has exceeded the notification threshold of <insert_2>.
Severity
0 : Information
Explanation
Measured rate of <insert_1> messages per second has exceeded the notification threshold of <insert_2> messages per second. Another entry will be written out when the rate drops back below the notification threshold.
BIP12073
Measured rate of <insert_1> has dropped below the notification threshold of <insert_2>
Severity
0 : Information
Explanation
Measured rate of <insert_1> messages per second has dropped below the notification threshold of <insert_2> messages per second. Another entry will be written out when the rate exceeds the notification threshold again.
BIP12074
Executing a database statement for <insert_1>.
Severity
0 : Information
Explanation
Executing a database statement against data source <insert_1>.
BIP12075
Executed a database statement for <insert_1>.
Severity
0 : Information
Explanation
Executed a database statement against data source <insert_1>.
BIP12076
Failed to prepare a database statement for <insert_1>.
Severity
10 : Warning
Explanation
Failed to prepare a database statement against data source <insert_1> please refer to the system error log for details.
BIP12077
Failed to execute a database statement for <insert_1>.
Severity
10 : Warning
Explanation
Execution of the database statement against data source <insert_1> failed. Please refer to the system error log for more details.
BIP12078
Connecting to database <insert_1>.
Severity
0 : Information
Explanation
Attempting connection to database <insert_1>.
BIP12079
Connected to database <insert_1>.
Severity
0 : Information
Explanation
A successful connection to database <insert_1> was made.
BIP12080
Preparing a database statement for <insert_1>.
Severity
0 : Information
Explanation
Preparing a database statement against data source <insert_1>.
BIP12081
Prepared a database statement for <insert_1>.
Severity
0 : Information
Explanation
Prepared a database statement against data source <insert_1>.
BIP12082
Delaying by <insert_1> seconds to keep the message rate below the maximum message rate of <insert_2>
Severity
0 : Information
Explanation
Delaying by <insert_1> seconds to keep the message rate below the maximum message rate of <insert_2>
BIP12083
Starting an aggregation named <insert_1>.
Severity
0 : Information
Explanation
Aggregation <insert_1> is commencing.
BIP12084
Sending an aggregation request named <insert_1> for folder <insert_2>.
Severity
0 : Information
Explanation
Aggregation <insert_1> is sending a request for folder name <insert_2>.
BIP12085
Received an aggregation reply named <insert_1> for folder <insert_2>.
Severity
0 : Information
Explanation
Aggregation <insert_1> has received a reply for folder name <insert_2>.
BIP12086
Timed out an aggregation named <insert_1>
Severity
0 : Information
Explanation
The aggregation <insert_1> timed out before all of the reply message requests were received.
BIP12087
Completed a timed out aggregation named <insert_1>.
Severity
0 : Information
Explanation
The aggregation <insert_1> timed out, but all reply message requests were received before the time out completed. The aggregation will be propagated to the Out terminal.
BIP12088
Finished aggregation named <insert_1>.
Severity
0 : Information
Explanation
Aggregation <insert_1> has completed.
BIP12089
Received an aggregation reply that is unknown.
Severity
0 : Information
Explanation
A reply was received that does not belong to any outstanding aggregation.
BIP12090
Processing of a message exceeded the processing timeout of <insert_2> seconds.
Severity
0 : Information
Explanation
The message flow <insert_1> has an instance that exceeded the processingTimeSec of <insert_2> defined for the message flow to process a message. A report will be published to MQ with the exact details.
BIP12091
Processing of a message finished after <insert_3> seconds.
Severity
0 : Information
Explanation
The message flow <insert_1> has an instance that took longer to process a message than the processingTimeSec of <insert_2> defined for the message flow, but finished processing after <insert_3> seconds.
BIP12092
Disconnected successfully from <insert_1>.
Severity
0 : Information
Explanation
Disconnected sucessfully from <insert_1>.
BIP12093
Fan-out completed for aggregation named <insert_1>.
Severity
0 : Information
Explanation
The fan-out for aggregation <insert_1> has completed.
BIP12094
Failed to disconnect from <insert_1>.
Severity
20 : Error
Explanation
Failed to disconnect from <insert_1> because of an exception <insert_2>.
Response
Investigate the exception <insert_2>.
BIP12095
Subscribed to topic <insert_1> with quality of service <insert_2>.
Severity
0 : Information
Explanation
Subscribed to topic <insert_1> with quality of service <insert_2>.
BIP12096
Failed to connect to <insert_1>.
Severity
20 : Error
Explanation
Failed to connect to <insert_1> with exception <insert_2>.
Response
Check that the hostname and port are specified correctly. That the server can be reached and that the client ID <insert_3> is unique across all MQTT publish and subscribe nodes connecting to the MQTT server.
BIP12097
Published to topic <insert_1> with quality of service <insert_2>.
Severity
0 : Information
Explanation
Published to topic <insert_1> with quality of service <insert_2>.
BIP12098
Received message from topic <insert_1> with quality of service <insert_2>.
Severity
0 : Information
Explanation
Received message from topic <insert_1> with quality of service <insert_2>.
BIP12099
Failed to publish to topic <insert_1> with quality of service <insert_2>. Operation timed out.
Severity
20 : Error
Explanation
Failed to publish to topic <insert_1> with quality of service <insert_2>. Operation timed out.