BIP7000-7999: Runtime components - Publish Subscribe
- BIP7001
- ACL already exists for topic <insert_1> and principal <insert_2>.
- Severity
- 20 : Error
- Explanation
- The broker received a request to create an ACL which already exists.
- Response
- You must use change or delete to act on the existing ACL or re-specify the topic or the principal to create a new ACL entry. If you don't expect this ACL to exist, check that the ACL has not already been created by another user, and that you have deployed any changes you wish to make.
- BIP7002
- ACL update error on topic <insert_1> and principal <insert_2>.
- Severity
- 20 : Error
- Explanation
- An internal error caused the update on the ACL for topic <insert_1> and principal <insert_2> to fail.
- Response
- Verify the topic and principal are correct and retry the operation. If the operation continues to fail, contact your IBM support center.
- BIP7005
- ACL not found for topic <insert_1> and principal <insert_2>.
- Severity
- 20 : Error
- Explanation
- The ACL operation failed because there is no ACL for topic <insert_1> and principal <insert_2>.
- Response
- Create the ACL before the operation, or verify the topic and principal are correct and retry the operation. If you expect this ACL to exist, check that the ACL has not been removed by another user, and that you have deployed any changes you wish to make.
- BIP7006
- No such principal <insert_1>.
- Severity
- 20 : Error
- Explanation
- The operation failed because principal <insert_1> does not exist.
- Response
- Verify the principal is correct and retry the operation. If you expect this principal to exist, check that it has not been changed by another user, and that you have deployed any changes you wish to make.
- BIP7008
- Security not enabled.
- Severity
- 30 : Severe error
- Explanation
- The operation failed because security was not enabled.
- Response
- This is an internal error and you should contact your IBM Support center.
- BIP7009
- Security policy violation - <insert_1> <insert_2> <insert_3>.
- Severity
- 20 : Error
- Explanation
- There was a violation of security policy or authorization was denied.
- Response
- Ensure that the user has the required authority to complete the operation and retry.
- BIP7013
- Unknown broker (Queue Manager <insert_1>).
- Severity
- 30 : Severe error
- Explanation
- The operation failed because the broker (Queue Manager <insert_1>) is unknown.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7014
- Unknown connection with id <insert_2> to broker (Queue Manager <insert_1>).
- Severity
- 30 : Severe error
- Explanation
- The operation failed because the connection with id <insert_2> to broker (Queue Manager <insert_1>) is unknown.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7015
- Permission conflict <insert_1>.
- Severity
- 20 : Error
- Explanation
- The operation failed because of an attempt to set incompatible permissions <insert_1>.
- Response
- Ensure that the permissions specified are not mutually exclusive, and retry the operation. Refer to the online help for more information on valid combinations of permissions.
- BIP7016
- Native security system error <insert_1>.
- Severity
- 20 : Error
- Explanation
- A call has been made to the operating system and there has been a error code returned.
- Response
- Look up the error code in your operating system documentation, and correct the problem. If the problem persists, contact your IBM support center.
- BIP7017
- Unknown user <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The user <insert_1> was not found in the security information.
- Response
- This may be an unauthorized user. However, if you expect the user to be able to access the broker, then this is an internal error, and you should contact your IBM support center.
- BIP7018
- Client (id <insert_1>) not registered.
- Severity
- 20 : Error
- Explanation
- An attempt was made to deregister a subscription registered by the client with id <insert_1>, but this subscription was not found, or some other error prevented the subscription being deregistered.
- Response
- Other messages in the log may give more details why the subscription was not deregistered. If the subscribing application involves a temporary dynamic queue, try stopping this application. If publications are no longer being sent to the subscriber queue, this message may be ignored, otherwise this is an internal error and should be reported to your IBM support center.
- BIP7019
- Problem accessing the broker database for publish/subscribe function.
- Severity
- 20 : Error
- Explanation
- A problem was encountered when accessing the broker database while processing a publish/subscribe function. The available information is given above in other messages.
- Response
- Check that the database is started and accessible, by using your database management tools. You may find some useful information in the problem determination section of the product documentation. Investigate any error codes given in the message above in your database documentation.
- BIP7020
- Start up failure <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Initialization of the Publication node failed.
- Response
- Check the system log for possible errors and restart the broker.
- BIP7021
- Internal Error in the PubSub Matching Engine <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error has occurred in the Matching Engine, recoverable work will be rolled back and then processing will continue.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7022
- Problem removing expired subscription.
- Severity
- 30 : Severe error
- Explanation
- An exception has occurred whilst removing an expired subscription. Previous messages will indicate the exact nature of this exception and its severity. The Publish/Subscribe Service has been rolled back.
- Response
- Check the error messages which precede this error to determine why the failure occurred, and take action as described by those messages.
- BIP7023
- Subscription to topic <insert_2> was not found for client <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- During processing of a RegisterSubscriber or a RequestUpdate request the subscription which client <insert_1> had for topic <insert_2> could not be found. The broker will be terminated.
- Response
- This is an internal error. Contact your IBM support center.
- BIP7024
- Cannot create or modify ACLs without access to information on users and groups.
- Severity
- 20 : Error
- Explanation
- The operation failed because the user/group cache for the broker is empty. The broker maintains a persistent cache of user and group information which it initially receives from the User Name Server. The cache will be empty if the broker has never successfully registered with the User Name Server, or if the registration is not complete at the time the ACL creation or modification request is processed.
- Response
- Check that the User Name Server has been started, and that the broker has successfully registered with the User Name Server. If the registration occurs after this failure, then retry the operation. Check preceding system log entries for related errors. Contact your IBM support center if the problem persists.
- BIP7025
- User does not have permission to subscribe to a topic: <insert_1>.
- Severity
- 10 : Warning
- Explanation
- Authorization to subscribe or request an update on a topic has been denied.
- Response
- Ensure that the user has the required authority to complete the operation and retry.
- BIP7026
- User does not have publish permission on a topic: <insert_1>.
- Severity
- 10 : Warning
- Explanation
- Authorization to publish or delete a publication on a topic has been denied.
- Response
- Ensure that the user has the required authority to complete the operation and retry.
- BIP7027
- User cannot receive a message because they do not have subscribe permission on a topic: <insert_1>.
- Severity
- 0 : Information
- Explanation
- Authorization to deliver a publication on a topic to a subscriber has been denied.
- Response
- If you require that the user should receive such publications revise the appropriate group or user ACLs and retry.
- BIP7030
- Publish/Subscribe state recovery failed.
- Severity
- 20 : Error
- Explanation
- A problem was encountered when accessing the broker database while processing transactional recovery for publish/subscribe information following some other error. The available information is given above in other messages. Refer to earlier messages for the original cause of the transaction failure.
- Response
- Check that the database is started and accessible, by using your database management tools. You may find some useful information in the problem determination section of the product documentation. Investigate any error codes given in the message above in your database documentation.
- BIP7031
- Publish/Subscribe state recovery started due to transaction rollback.
- Severity
- 0 : Information
- Explanation
- A transaction which involved an update to the Publish/Subscribe state has been rolled back in the broker. In order to restore the Publish/Subscribe state to its prior value, it will be recovered from the broker's database. The available information is given above in other messages. Refer to earlier messages for the original cause of the transaction failure.
- Response
- This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
- BIP7032
- Publish/Subscribe state recovery started due to incorrect sequence number.
- Severity
- 0 : Information
- Explanation
- An internal Publish/Subscribe message has been received with an incorrect sequence number. This indicates that the broker's Publish/Subscribe state is inconsistent, and will be recovered from the broker's database.
- Response
- This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
- BIP7033
- Publish/Subscribe state recovery completed.
- Severity
- 0 : Information
- Explanation
- Recovery of the Publish/Subscribe state from the broker's database is complete.
- Response
- This message is for information only. No action is required.
- BIP7034
- Publish/Subscribe support has been disabled.
- Severity
- 20 : Error
- Explanation
- A message has been propagated to a Publication node, but the Publish/Subscribe mode is set to DISABLED.
- Response
- You cannot use the Publication node within message flows if you have set the Publish/Subscribe mode to DISABLED.
- BIP7035
- Publish/Subscribe support in the broker has been disabled.
- Severity
- 0 : Information
- Explanation
- The broker's publish/subscribe engine has been disabled. The following message processing nodes, if present in a message flow that is deployed to this broker, cannot accept messages: Publication node, SCADAInput node, SCADAOutput node, Real-timeInput node, and Real-timeOptimized Flow node
- Response
- This message is for information only.
- BIP7036
- An error occurred in Content-Based Filtering subscription-time processing while attempting to validate the filter <insert_1>.
- Severity
- 20 : Error
- Explanation
- The Content-Based Filtering engine was asked to validate the specified ESQL filter, but the operation failed. See the following messages for details of the error.
- Response
- Correct the filter expression.
- BIP7037
- An error occurred in Content-Based Filtering publication-time processing.
- Severity
- 20 : Error
- Explanation
- The Content-Based Filtering engine was asked to evaluate an ESQL filter against a message, but the operation failed.
- Response
- See the following messages for details of the error.
- BIP7038
- The Content-Based Filtering engine has started with <insert_1> validation threads and <insert_2> evaluation threads.
- Severity
- 0 : Information
- Explanation
- The Content-Based Filtering engine has started and is now ready to receive Content-Based Filtering requests from WebSphere MQ.
- Response
- No user action required.
- BIP7040
- Unknown parameter name <insert_1>.
- Severity
- 20 : Error
- Explanation
- The parameter name <insert_1> is not a valid configuration parameter of the node.
- Response
- If this error has occurred as a result of an action from the Message Broker Toolkit, it is an internal error and you should contact your IBM support center. Otherwise, correct the invalid parameter name, then retry the operation.
- BIP7041
- Invalid parameter value <insert_1> <insert_2>.
- Severity
- 20 : Error
- Explanation
- The parameter <insert_1> had a value <insert_2> which is outside its allowed range, contains disallowed characters, is not a member of the permitted set of values, or was invalid for some other reason.
- Response
- If this error has occurred as a result of an action from the Message Broker Toolkit, it is an internal error and you should contact your IBM support center. Otherwise, correct the invalid value, then retry the operation.
- BIP7042
- The Content-Based Filtering engine successfully validated the filter <insert_1>.
- Severity
- 0 : Information
- Explanation
- While processing a subscription, WebSphere MQ queried the Content-Based Filtering engine to validate an ESQL filter; the validation has been successful.
- Response
- No user action required.
- BIP7043
- The Content-Based Filtering engine received a new message from WebSphere MQ.
- Severity
- 0 : Information
- Explanation
- While processing a publication, WebSphere MQ sent a message to the Content-Based Filtering engine. Subsequently, the Content-Based Filtering engine will evaluate filters against this message.
- Response
- No user action required.
- BIP7044
- The Content-Based Filtering engine evaluated the filter <insert_1> against the last received message, and the filter matched.
- Severity
- 0 : Information
- Explanation
- While processing a publication, WebSphere MQ queried the Content-Based Filtering engine to evaluate an ESQL expression against the last received message. The ESQL expression matched the message.
- Response
- No user action required.
- BIP7045
- The Content-Based Filtering engine evaluated the filter <insert_1> against the last received message, and the filter did not match.
- Severity
- 0 : Information
- Explanation
- While processing a publication, WebSphere MQ queried the Content-Based Filtering engine to evaluate an ESQL expression against the last received message. The ESQL expression did not match the message.
- Response
- No user action required.
- BIP7047
- Neighbor (Queue Manager <insert_1>) failed to register the subscription request with reason code <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The Neighbor broker could not process the subscription request successfully. Broker will send the subscription request again.
- Response
- Check the reason code and resolve the issue on Neighbor broker.
- BIP7049
- Unexpected Java exception <insert_1>.
- Severity
- 20 : Error
- Explanation
- An unexpected exception was thrown from Java code. The detail shows the Java stack trace where the exception occurred. The broker may continue to run but may produce unexpected results.
- Response
- Restart the broker. If the problem persists you should contact your IBM support center.
- BIP7050
- Failed to locate Java class <insert_1>.
- Severity
- 20 : Error
- Explanation
- The Java class <insert_1> could not be found.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7051
- Failed to locate Java method <insert_1> in class <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- The Java method <insert_1> in class <insert_2> could not be found.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7052
- Failed to create Java object <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The Java object <insert_1> could not be created.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7053
- Unexpected Java exception <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An unexpected exception was thrown from Java code. The detail shows the Java stack trace where the exception occurred.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7054
- Unexpected null pointer for instance of class <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An unexpected null pointer exception was thrown from Java code on an object of class <insert_1>.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7055
- Invalid attribute value <insert_1> <insert_2>.
- Severity
- 20 : Error
- Explanation
- The attribute <insert_1> had a value <insert_2> which is outside its allowed range, contains disallowed characters, is not a member of the permitted set of values, or was invalid for some other reason.
- Response
- If this error has occurred as a result of an action from the Message Broker Toolkit, it is an internal error and you should contact your IBM support center. Otherwise, correct the invalid value, then retry the operation.
- BIP7056
- Attribute value not found or invalid <insert_1>.
- Severity
- 20 : Error
- Explanation
- The attribute <insert_1> had no value or the value could not be determined.
- Response
- If this error has occurred as a result of an action from the Message Broker Toolkit, it is an internal error and you should contact your IBM support center. Otherwise, check the attribute has a valid value, then retry the operation.
- BIP7057
- Invalid neighbor with queue manager <insert_1>.
- Severity
- 20 : Error
- Explanation
- The queue manager <insert_1> could not be contacted for the purpose of sending publications between brokers. The connection has not been made.
- Response
- Ensure that the appropriate WebSphere MQ configuration is in place to allow the broker to communicate with the given queue manager, and that there is a broker currently installed and configured on that queue manager.
- BIP7058
- Failed to create message element <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- While attempting to build a message a failure occurred on creating element <insert_1>.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7059
- Failed to navigate to message element <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- While attempting to explore the contents of a message an error occurred because the element <insert_1> was missing or unreachable.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7061
- Invalid client identifier <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The client identifier <insert_1> is incomplete or invalid.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7062
- An invalid PCF message has been detected: diagnostic data <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An invalid PCF message has been detected.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7063
- Not an RFH message.
- Severity
- 30 : Severe error
- Explanation
- The message was found not to be an RFH message while performing an operation only supported for RFH format messages.
- Response
- Ensure that the message sent for this operation has an RFH header and retry.
- BIP7064
- Failed to create Java VM <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The broker creates a Java Virtual Machine to support internal operations, but in this case has been unable to do so. There may have been a problem with the way the product was installed, or something has subsequently affected the installation.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7065
- Failed to attach thread to JVM.
- Severity
- 30 : Severe error
- Explanation
- The broker creates a Java Virtual Machine to support internal operations. This error indicates that there has been an internal problem using the JVM.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7066
- Failed to get the Java Native Interface pointer.
- Severity
- 30 : Severe error
- Explanation
- The broker creates a Java Virtual Machine to support internal operations. This error indicates that there has been an internal problem using the JVM.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7067
- Caught exception while deleting message flow <insert_1> <insert_2>.
- Severity
- 20 : Error
- Explanation
- There was a problem while attempting to delete the named message flow.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7069
- Tried to create two instances of <insert_1> where only one is allowed.
- Severity
- 30 : Severe error
- Explanation
- Some publish subscribe resources, such as the internal node which processes control messages, must not be created more than once. This error indicates that an attempt was made to create a second instance of such a resource.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7071
- Message (of type <insert_2>) on incorrect queue <insert_1>.
- Severity
- 20 : Error
- Explanation
- An application put a message of type <insert_2> on queue <insert_1>. This queue is not intended for messages of that type and the message was not processed.
- Response
- Ensure that your applications are putting messages on the correct queue. Publish and Delete Publication messages should only be put on application queues. Control messages should only be put on SYSTEM.BROKER.CONTROL.QUEUE. Correct the application, then retry the operation.
- BIP7072
- Neighbor (queue manager <insert_1>) is already an WebSphere publish/subscribe neighbor.
- Severity
- 20 : Error
- Explanation
- An attempt has been made to join this broker with a WebSphere Message Broker broker on queue manager <insert_1>. This request was unsuccessful because the broker is already joined as an WebSphere publish/subscribe neighbor.
- Response
- If queue manager <insert_1> is a WebSphere Message Broker broker then it can only be joined to this broker when the WebSphere publish/subscribe link has been removed. This can be achieved using the mqsiclearmqpubsub command.
- BIP7073
- Invalid publisher event message received in subordinate process.
- Severity
- 30 : Severe error
- Explanation
- A publisher event message, which is used to synchronize publish/subscribe information between two execution groups, had no message body, so was not correctly processed.
- Response
- If you have several execution groups, they may be out of step. They can be resynchronized by restarting the broker, but this is an internal error and you should contact your IBM support center.
- BIP7074
- Exception <insert_2> condition detected while recovering client <insert_1> from the database.
- Severity
- 20 : Error
- Explanation
- An exception condition was detected in the message broker when trying to recover a client from the database.
- Response
- Ensure that the client id exists and is valid and re-try the operation.
- BIP7075
- Unable to find client id <insert_1> for subscription registered to topic <insert_2>.
- Severity
- 20 : Error
- Explanation
- While trying to recover the subscriptions a matching client id could not be found.
- Response
- Ensure that the client id is valid and re-try the operation.
- BIP7076
- Unable to find client id <insert_1> for publisher registered to topic <insert_2>.
- Severity
- 20 : Error
- Explanation
- While trying to recover the Publisher a matching client id could not be found.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7077
- Unable to start Publish/Subscribe Service.
- Severity
- 30 : Severe error
- Explanation
- The message broker was unable to start the Publish/Subscribe Service. See the following messages for details of the error.
- Response
- If the error persists contact your IBM support center.
- BIP7078
- Failed to detach thread from the JVM.
- Severity
- 30 : Severe error
- Explanation
- The broker creates a Java Virtual Machine to support internal operations. This error indicates that there has been an internal problem using the JVM.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7079
- Node <insert_2>: The Publish/Subscribe service has received a message of type <insert_1>.
- Severity
- 0 : Information
- Explanation
- The Publish/Subscribe service has started processing a control message.
- Response
- No user action required.
- BIP7080
- Node <insert_3>: The Publication Node with Subscription Point <insert_2> has received a message of type <insert_1>.
- Severity
- 0 : Information
- Explanation
- The Publication Node with Subscription Point <insert_2> has started processing a message.
- Response
- No user action required.
- BIP7081
- The Publication Node has matched <insert_1> subscriptions to topic <insert_2> for subscription point <insert_3>.
- Severity
- 0 : Information
- Explanation
- The Publication Node has matched subscriptions for the current publication and topic.
- Response
- No user action required.
- BIP7082
- Node <insert_3>: Publishing to destination <insert_1> for user <insert_2>.
- Severity
- 0 : Information
- Explanation
- A publication destination is being added to the list of destinations to <insert_1> for user <insert_2>.
- Response
- No user action required.
- BIP7083
- Node <insert_3>: The Publication Node with Subscription Point <insert_2> has received an error code <insert_1>.
- Severity
- 0 : Information
- Explanation
- The Publication Node with Subscription Point <insert_2> has received an error with code <insert_1>. A response message has been sent to the originator's reply queue.
- Response
- No user action required.
- BIP7084
- Node <insert_2>: The Publish/Subscribe service has received an error code <insert_1>.
- Severity
- 0 : Information
- Explanation
- The Publish/Subscribe service has received an error with code <insert_1>. A response message has been sent to the originator's reply queue.
- Response
- No user action required.
- BIP7085
- Node <insert_2>: The Publication Node has propagated a message to its output terminal for subscription point <insert_1>.
- Severity
- 0 : Information
- Explanation
- The Publication Node has propagated the current message to its output terminal.
- Response
- No user action required.
- BIP7086
- Node <insert_3>: The Publication Node with Subscription Point <insert_2> has received an error code <insert_1>.
- Severity
- 0 : Information
- Explanation
- The Publication Node with Subscription Point <insert_2> has received an error with code <insert_1>. No response message has been sent as one was not requested.
- Response
- No user action required.
- BIP7087
- Node <insert_2>: The Publish/Subscribe service has received an error code <insert_1>.
- Severity
- 0 : Information
- Explanation
- The Publish/Subscribe service has received an error with code <insert_1>. No response message has been sent because one was not requested.
- Response
- No user action required.
- BIP7088
- publish/subscribe configuration request <insert_1> cannot be processed until after WebSphere publish/subscribe migration has completed.
- Severity
- 10 : Warning
- Explanation
- The broker has been created as a replacement for an existing WebSphere publish/subscribe broker. Until all subscriptions and retained publications have been successfully migrated into the WebSphere Message Broker broker it is not possible to deploy any new publish/subscribe configuration changes.
- Response
- Redeploy the configuration changes after migration has completed successfully.
- BIP7089
- Publish/Subscribe migration logic error.
- Severity
- 30 : Severe error
- Explanation
- The broker has been created as a replacement for an existing WebSphere Publish/Subscribe broker. A logic error has been detected which has caused the broker to terminate.
- Response
- This error should be reported to your IBM support center. Until the problem is corrected you can not continue to use your existing WebSphere Publish/Subscribe broker.
- BIP7091
- Caught exception <insert_3> while deregistering subscriptions for client id <insert_1>: error code <insert_2>.
- Severity
- 20 : Error
- Explanation
- There was a problem while attempting to deregister all subscriptions for a client.
- Response
- Due to the error deregistering the subscription, the subscription state of the broker may be inconsistent. It may be necessary to restart the broker to eliminate the problem. If the problem persists, you should contact your IBM support center.
- BIP7092
- Problem removing expired retained publication.
- Severity
- 20 : Error
- Explanation
- An exception has occurred whilst removing an expired retained publication. Previous messages will indicate the exact nature of this exception and its severity. The Dynamic Subscription Engine state has been rolled back.
- Response
- Check the error messages which precede this error to determine why the failure occurred, and take action as described by those messages.
- BIP7093
- Attribute style properties not allowed in publish/subscribe message.
- Severity
- 20 : Error
- Explanation
- A publish/subscribe message was received where the properties were expressed like XML attributes. For example, <psc Command="Publish" />. This is not allowed - you should use the nested tag syntax to express the publish/subscribe information. The above example should be <psc><Command>Publish</Command></psc>. See the WebSphere Message Broker Programming Guide, for more information and examples.
- Response
- Change the application which generated the message to use syntax as described above.
- BIP7094
- Exception condition detected while publishing a broker status message.
- Severity
- 10 : Warning
- Explanation
- The broker has detected an error while publishing a status message. Status messages are used to monitor the status of the broker.
- Response
- Check the error messages that follow, to determine why the exception was generated, and take action as described by those messages.
- BIP7095
- Requested response cannot be sent for a message that does not include an MQRFH or MQRFH2 header.
- Severity
- 20 : Error
- Explanation
- A message requesting a response was received by the Publish/Subscribe Service. To send a response, the Publish/Subscribe Service requires that the message contains an MQRFH or MQRFH2 format header. The received message contains neither.
- Response
- Ensure that the message was placed on the correct queue for the required message flow. If the correct queue was used, ensure that the message sent for this operation has an MQRFH or MQRFH2 header, or ensure that the report options in the message descriptor are set so that a response is not requested.
- BIP7096
- Node <insert_1>: The ComIbmJmsIpInput Node has propagated a message to its output terminal.
- Severity
- 0 : Information
- Explanation
- The ComIbmJmsIpInput Node has propagated the current message to its output terminal.
- Response
- No user action required.
- BIP7097
- Java Virtual Machine OutOfMemoryError occurred.
- Severity
- 20 : Error
- Explanation
- The JVM has reported an OutOfMemoryError situation.
- Response
- It may be necessary to restart the Broker and increase the Java Virtual Machine Heap size.
- BIP7098
- Unable to find user <insert_1> for subscription registered to topic <insert_2>.
- Severity
- 10 : Warning
- Explanation
- While trying to recover a subscription, a user id could not be found. The subscription will be removed from the broker.
- Response
- None.
- BIP7099
- The Publication Node <insert_3> has passed a publish message to WebSphere MQ with topic <insert_1> for subscription point <insert_2>.
- Severity
- 0 : Information
- Explanation
- The Publication Node has passed a publish message to WebSphere MQ.
- Response
- No user action required.
- BIP7100
- The MQRFH2 header field NameValueCCSID contains a value that is not valid: <insert_1>.
- Severity
- 20 : Error
- Explanation
- The NameValueCCSID field in the MQRFH2 header must contain one of the following values: <insert_2>. Refer to the WebSphere MQ documentation.
- Response
- Ensure that the NameValueCCSID field contains a valid value.
- BIP7101
- Could not access MQConnectionManager resource.
- Severity
- 30 : Severe error
- Explanation
- The Publish/Subscribe Service, implemented in imbdfjps.lil, requires the presence of the WebSphere MQ library, imbdfmqm.lil. This library is either missing or invalid. Other messages may indicate the reasons for the failure to load imbdfmqm.lil.
- Response
- Ensure that imbdfmqm.lil is valid and in the correct location. Check other messages for reasons why imbdfmqm.lil might not have loaded.
- BIP7102
- Requesting broker <insert_1> has inconsistent Queue Manager value <insert_2>.
- Severity
- 10 : Warning
- Explanation
- A broker (identified by its UUID <insert_1> and Queue Manager <insert_2>) has been defined with this broker as a neighbor, and has attempted to make contact. This broker has been configured for the other broker, but with a different Queue Manager name. This may occur because a broker at one end of a connection in the broker topology has not been running for some time, and may receive old configuration messages from brokers which have since been reconfigured.
- Response
- Ensure that the communication paths exist between both brokers, and are running correctly. If the brokers do not subsequently connect successfully (which will be identified by another message), reestablish the broker topology by redeploying. If the problem persists, contact your IBM support center.
- BIP7103
- Requesting broker <insert_1> (Queue Manager <insert_2>) is currently unknown.
- Severity
- 10 : Warning
- Explanation
- A broker (identified by its UUID <insert_1> and Queue Manager <insert_2>) has been defined with this broker as a neighbor, and has attempted to make contact. As the requesting broker is not currently known by this broker, the request has been rejected. This message occurs because the configuration message updating the broker topology has reached one broker before the other. If the communication paths between the brokers are set up and running correctly, this message will be followed by another one which will indicate that the connection between the brokers has been successful. If the communication paths are not set up correctly, no such message will be produced, and publications will not flow between the brokers.
- Response
- If no message indicating the successful connection of the broker is produced, ensure that the communication paths exist between both brokers, and are running correctly. If the brokers do not subsequently connect successfully (which will be identified by another message), reestablish the broker topology by redeploying. If the problem persists, contact your IBM support center.
- BIP7104
- Interbroker message flow <insert_1> not found.
- Severity
- 30 : Severe error
- Explanation
- The message flow <insert_1> dedicated to serving interbroker function was not found.
- Response
- Examine the system log for errors on startup to see if there was an error which might have led to the interbroker message flow not being created. This problem may be resolved by stopping and restarting the broker. Otherwise contact your IBM support center.
- BIP7105
- Interbroker node not found in messageflow <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An attempt was made to locate the Interbroker node within message flow <insert_1>. This message flow is internally created and managed by the broker. This is an internal error.
- Response
- Examine the system log for errors on startup to see if there was an error which might have lead to the message flow not being created correctly. This problem may be resolved by stopping and restarting the broker. If the problem cannot be resolved contact your IBM support center.
- BIP7106
- Accepting broker <insert_1> (Queue Manager <insert_2>) is currently unknown.
- Severity
- 10 : Warning
- Explanation
- A broker (identified by its UUID <insert_1> and Queue Manager <insert_2>) has been defined with this broker as a neighbor, and has sent this broker a connection acceptance message. This broker is not currently configured for the other broker, although it was at some time in the past. This may occur because a broker at one end of a connection in the broker topology has not been running for some time, and may receive old configuration messages from brokers which have since been reconfigured.
- Response
- Ensure that the communication paths exist between both brokers, and are running correctly. If the brokers do not subsequently connect successfully (which will be identified by another message), reestablish the broker topology by redeploying. If the problem persists, contact your IBM support center.
- BIP7107
- The ComIbmJmsIpInput Node <insert_2> code caught an unknown exception on thread <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The exception was issued on thread <insert_1>. Further information may be in the exception information associated with this message.
- Response
- The broker should shutdown and restart automatically. If the problem continues to occur, then restart the system. If the problem still continues to occur, then contact your IBM support center.
- BIP7108
- The ComIbmJmsIpInput Node <insert_2> code caught a fatal exception on thread <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The exception was issued on thread <insert_1>. Further information may be in the exception information associated with this message.
- Response
- The broker should shutdown and restart automatically. If the problem continues to occur, then restart the system. If the problem still continues to occur, then contact your IBM support center. Exception details follow.
- BIP7109
- The ComIbmJmsIpInput Node <insert_2> code caught a recoverable exception on thread <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The exception was issued on thread <insert_1>. Further information may be in the exception information associated with this message.
- Response
- The broker should continue to operate normally. If the problem continues to occur, then shutdown and restart the broker. If the problem still continues to occur, then contact your IBM support center. Exception details follow.
- BIP7110
- A recoverable exception on thread <insert_1> was caught while trying to convert message.
- Severity
- 10 : Warning
- Explanation
- An exception was caught whilst trying to convert a message to or from a WebSphere MQ message. The exception was issued on thread <insert_1>. Further information may be in the exception information associated with this message.
- Response
- The broker should continue to operate normally. If the problem continues to occur, then shutdown and restart the broker. If the problem still continues to occur, then contact your IBM support center. Exception details follow.
- BIP7111
- A fatal exception on thread <insert_1> was caught while trying to convert message.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught whilst trying to convert a message to or from a WebSphere MQ message. The exception was issued on thread <insert_1>. Further information may be in the exception information associated with this message.
- Response
- The broker should shutdown and restart automatically. If the problem continues to occur, then shutdown and restart the system. If the problem still continues to occur, then contact your IBM support center. Exception details may follow.
- BIP7112
- Requesting broker (UUID <insert_1>, queue manager <insert_2>) has an incorrect value <insert_3> for this broker's UUID, which is <insert_4>.
- Severity
- 10 : Warning
- Explanation
- A broker (identified by its UUID and queue manager name) has been defined with this broker as a neighbor, and has attempted to make contact. However the neighboring broker's definition for this broker has used a different UUID from that which this broker is running under. This may occur because a broker at one end of a connection in the broker topology has not been running for some time, and may receive old configuration messages from brokers which have since been reconfigured.
- Response
- Ensure that the communication paths exist between both brokers, and are running correctly. If the brokers do not subsequently connect successfully (which will be identified by another message), reestablish the broker topology by redeploying. If the problem persists, contact your IBM support center.
- BIP7113
- Interbroker connection established with neighbor (Queue Manager <insert_1>).
- Severity
- 0 : Information
- Explanation
- A connection has been established with neighboring broker (Queue Manager <insert_1>) for the purposes of sending publications between the brokers.
- Response
- This message is for information only, to confirm that the interbroker connection has been made successfully.
- BIP7114
- Interbroker connection ended with neighbor (Queue Manager <insert_1>).
- Severity
- 0 : Information
- Explanation
- An active connection has been ended with the neighboring broker (Queue Manager <insert_1>). Publications will not flow between the brokers until the connection is reestablished.
- Response
- This message is for information only, to confirm that the connection has been ended.
- BIP7115
- Failure to create message flow for neighboring broker: error code <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An attempt to create a message flow to connect to a neighboring broker was unsuccessful.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7116
- Failure to modify message flow for neighboring broker: error code <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An attempt to modify a message flow to connect to a neighboring broker was unsuccessful.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7117
- Broker must be restarted for topology update to take effect.
- Severity
- 10 : Warning
- Explanation
- In some cases, updates to topology information require the broker to be restarted. The broker may produce unpredictable results until it is restarted.
- Response
- Restart the broker.
- BIP7118
- A recoverable exception was caught while trying to publish a subscription event message.
- Severity
- 10 : Warning
- Explanation
- A recoverable exception was caught whilst trying to publish a subscription event message. The exception was issued on thread <insert_1>. Further information may be in the exception information associated with this message.
- Response
- The broker should continue to operate normally. If the problem continues to occur, then shutdown and restart the broker. If the problem still continues to occur, then contact your IBM support center. Exception details follow.
- BIP7119
- A fatal exception was caught while trying publish a subscription event message
- Severity
- 30 : Severe error
- Explanation
- A fatal exception was caught whilst trying to publish a subscription event message. The exception was issued on thread <insert_1>. Further information may be in the exception information associated with this message.
- Response
- The broker should shutdown and restart automatically. If the problem continues to occur, then shutdown and restart the system. If the problem still continues to occur, then contact your IBM support center. Exception details may follow.
- BIP7120
- The Real-timeInput node <insert_1> is no longer supported in WebSphere Message Broker.
- Severity
- 20 : Error
- Explanation
- A Real-timeInput or a Real-timeOptimizedFlow node has been deployed to the broker. The node will not work because Real-time function is no longer supported.
- Response
- Remove all Real-timeInput and Real-timeOptimizedFlow nodes from this message flow, then redeploy the message flow.
- BIP7121
- The WebSphere MQ Queue Manager <insert_1> does not support the Clear Topic function.
- Severity
- 0 : Information
- Explanation
- The Publication Node is unable to locate the Clear Topic function in the WebSphere MQ library where it was expected.
- Response
- Check that the installed version of WebSphere MQ is supported with this version of WebSphere Message Broker. Check that you have a valid installation of WebSphere Message Broker and WebSphere MQ. If the problem persists, contact your IBM support center.
- BIP7122
- Failure occurred putting a message to the queue manager on topic <insert_2>. The WebSphere MQ reason code is <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Broker attempted to put a message to a WebSphere MQ topic and WebSphere MQ returned a failure reason code.
- Response
- Review the reason code to establish the cause of the error.
- BIP7123
- Failure occurred performing a delete publication request against the queue manager on topic <insert_2>. The WebSphere MQ reason code is <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The WebSphere Message Broker attempted to perform a publication deletion request on a WebSphere MQ topic. WebSphere MQ returned a failure reason code.
- Response
- Review the reason code to establish the cause of the error.
- BIP7140
- The cache components in this execution group will start with a blank domain name because the current fix pack function level of <insert_1> does not support specific domain names. These components are able to collaborate in a multi-broker cache that includes brokers at previous fix pack capability levels, but cannot collaborate with brokers where new function has already been enabled. To enable this functionality, run the following command: mqsichangebroker <brokerName> -f all
- Severity
- 10 : Warning
- Explanation
- The broker cannot set a specific or derived domain name because new functionality has not been enabled for this broker. To enable this (and all other) functionality, run the following command: mqsichangebroker <brokerName> -f all
- BIP7141
- The message flow cannot set the time to live for data in the global cache, because the current fix pack function level of <insert_1> does not support this capability. To enable this functionality, run the following command: mqsichangebroker <brokerName> -f all
- Severity
- 20 : Error
- Explanation
- The broker received an instruction to set the time to live for data in the global cache. The broker cannot set the time to live because new functionality has not been enabled for this broker. To enable this (and all other) functionality, run the following command: mqsichangebroker <brokerName> -f all
- Response
- Either change the flow to create the map object without a time to live, or enable new functionality by using the mqsichangebroker command.
- BIP7142
- The message flow cannot connect to a remote WebSphere eXtreme Scale grid, defined by configurable service <insert_1>, because the current fix pack function level of <insert_2> does not support remote grid connections. To enable this functionality, run the following command: mqsichangebroker <brokerName> -f all
- Severity
- 20 : Error
- Explanation
- The broker received an instruction to connect to a remote WebSphere eXtreme Scale grid, defined by configurable service <insert_1>. The broker cannot connect to remote WebSphere eXtreme Scale grids because new functionality has not been enabled for this broker. To enable this (and all other) functionality, run the following command: mqsichangebroker <brokerName> -f all
- Response
- Either change the flow to avoid using the remote WebSphere eXtreme Scale grid, or enable new functionality by using the mqsichangebroker command.
- BIP7143
- The message flow failed to connect to an external WebSphere eXtreme Scale grid. A client attempted to connect to WebSphere eXtreme Scale grid <insert_1>, defined by configurable service <insert_2>. This connection attempt failed because an SSL connection was requested, but the execution group is not set up correctly for SSL. For details of the error, see earlier error and warning messages from this execution group.
- Severity
- 20 : Error
- BIP7144
- The message flow failed to connect to an external WebSphere eXtreme Scale grid. A client attempted to connect to WebSphere eXtreme Scale grid <insert_1>, defined by configurable service <insert_2>, with SSLTransportType <insert_3>. This connection attempt failed because this execution group hosts a catalog or container server for the embedded global cache, and cannot make SSL connections to external WebSphere eXtreme Scale grids.
- Severity
- 20 : Error
- Response
- Correct the configurable service to disable SSL, or deploy this flow to an execution group that does not host a catalog or container server.
- BIP7145
- A problem was encountered opening the broker keystore or truststore file <insert_1>. Initialization of security settings for WebSphere eXtreme Scale external grid connections has failed. This execution group cannot make SSL connections to external WebSphere eXtreme Scale grids.
- Severity
- 10 : Warning
- Response
- Check that the file exists and has not been altered. Verify that the keystore and truststore password settings are correct.
- BIP7146
- A problem was encountered when verifying the sslProtocol value <insert_1>. This protocol is not supported by the IBMJSSE2 security provider. Initialization of security settings for WebSphere eXtreme Scale external grid connections has failed. This execution group cannot make SSL connections to external WebSphere eXtreme Scale grids.
- Severity
- 10 : Warning
- Response
- Change the sslProtocol value to a supported protocol. For example: TLS, TLSv1, SSL, SSLv3 or SSL_TLS.
- BIP7147
- The message flow failed to connect to an external WebSphere eXtreme Scale grid. A client attempted to connect to WebSphere eXtreme Scale grid <insert_1>, defined by configurable service <insert_2>. This connection attempt failed because the SSL Handshake failed with the following error: <insert_3>.
- Severity
- 20 : Error
- Response
- Ensure that this execution group and the WebSphere eXtreme Scale grid have the correct SSL or TLS (Transport Layer Security) setup to communicate securely.
- BIP7148
- The message flow failed to connect to an external WebSphere eXtreme Scale grid. A client attempted to connect to WebSphere eXtreme Scale grid <insert_1>, defined by configurable service <insert_2>. This connection attempt failed because the specified overrideObjectGridFile <insert_3> is invalid. The following error occurred while processing the specified file <insert_4>.
- Severity
- 20 : Error
- Response
- Correct the error in the overrideObjectGridFile and retry the connection.
- BIP7149
- The message flow failed to connect to an external WebSphere eXtreme Scale grid. A client attempted to connect to WebSphere eXtreme Scale grid <insert_1>, defined by configurable service <insert_2>. This connection attempt failed because the specified overrideObjectGridFile <insert_3> does not exist. Ensure that the specified override file exists in the specified location.
- Severity
- 20 : Error
- BIP7150
- User id <insert_3> not authorized to put to queue <insert_2> on queue manager <insert_1> using accounting token <insert_4>.
- Severity
- 20 : Error
- Explanation
- The user is not authorized to put a message on the named queue.
- Response
- Ensure the user is allowed to perform this operation. This may involve configuring the WebSphere MQ settings for this queue, or using an alternative userid which is authorized.
- BIP7151
- Tried to create two pub/sub user/group data stores.
- Severity
- 30 : Severe error
- Explanation
- The internal object which represents the data store for users or groups, must not be created more than once. This error indicates that an attempt was made to create a second instance of such a resource.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7152
- The message flow failed to connect to an external WebSphere eXtreme Scale grid. A client attempted to connect to WebSphere eXtreme Scale grid <insert_1>, defined by configurable service <insert_4>, using connection string <insert_2>. This connection attempt failed with the following error: <insert_3>.
- Severity
- 20 : Error
- Response
- Ensure that the grid is available, and that the connection parameters specified in the configurable service are correct. If the external WebSphere eXtreme Scale grid requires SSL, ensure that this execution group is correctly configured for SSL connections.
- BIP7153
- The broker global cache is attempting to use the listener host <insert_1>, but the host does not appear to be bound to any network interfaces on this system. Startup of the WebSphere eXtreme Scale server components will continue, but the components may not start correctly without a valid listener host.
- Severity
- 10 : Warning
- Response
- Configure the broker to use a listener host setting that is bound to a network interface on this system.
- BIP7154
- The shutdown mode <insert_1>, specified for the cache manager, is invalid.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Ensure that the shutdown mode specified for the cache manager is one of the following options:
"fast"
"safe"
- BIP7155
- The execution group has established a connection to the broker global cache.
- Severity
- 0 : Information
- Explanation
- A connection has been established to the broker global cache. The broker global cache is now available for use from message processing nodes.
- BIP7156
- This execution group has failed to establish a connection to the broker global cache. The attempt to connect to the remote server components has now been running for <insert_1> seconds. The connection is being made using the connection string <insert_2>.
- Severity
- 10 : Warning
- Explanation
- An attempt was made by this execution group to connect to one or more remote WebSphere eXtreme Scale server components that host the broker global cache, but the connection could not be established within the specified period of time. The attempt to connect to the remote server components will continue in the background. Until this execution group can establish a connection to the remote server components, the broker global cache will not be available for use with message processing nodes.
The remote server components may be hosted within other execution groups within the broker. If this execution group is part of a multi-broker global cache topology, then the other execution groups may be located in other brokers on remote systems.
- Response
- The remote server components might be slow to start up due to one or more of the following reasons:
1. This system, or the system that hosts the remote server components, is not capable of starting the remote server components within the specified time.
2. The configuration for this execution group is incorrect. Check the configured properties for this execution group.
3. Other execution groups containing WebSphere eXtreme Scale server components that communicate with this execution group have not started yet. Ensure that all execution groups are available.
- BIP7157
- The policy in the policy file <insert_1>, specified for the cache manager, is invalid.
The broker, with name <insert_2> and listener host <insert_3>, specifies an invalid port range of <insert_4>.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Ensure that the port range specified for the broker specified is valid according to the XML schema for policy files, and that the following conditions are met:
1. The values for startport and endport are valid numbers between 1 and 65536.
2. The value for startport is less than that for endport.
3. Enough ports are available between startport and endport.
- BIP7158
- The policy in the policy file <insert_1>, specified for the cache manager, is invalid.
The broker, with name <insert_2> and listener host <insert_3>, specifies an invalid port range of <insert_4>.
This port range conflicts with that of the broker with name <insert_5> and listener host <insert_6> which uses the port range <insert_7>.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Explanation
- It is invalid to define overlapping port ranges for brokers on a single listener host.
- Response
- Alter the port range for either of the brokers specified so that the port ranges do not conflict with each other.
- BIP7159
- The policy in the policy file <insert_1>, specified for the cache manager, is invalid.
The broker, with name <insert_2> and listener host <insert_3>, specifies an invalid port range of <insert_4>.
Only <insert_5> ports are available in this port range. At least <insert_6> ports are required.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Alter the port range for the broker specified so that the required number of ports are available.
- BIP7160
- Catalog server <insert_1> in execution group <insert_2> failed to start. Further details of the error are : <insert_3>. Check the configured properties for this server. Verify that the ports that are configured for this server are available on this computer.
- Severity
- 20 : Error
- Explanation
- The WebSphere eXtreme Scale catalog server in this execution group has failed to start. If this catalog server is the only one for the broker global cache, the cache will not be available for use with message processing nodes.
- BIP7161
- Container server <insert_1> in execution group <insert_2> failed to start. Further details of the error are : <insert_3>. Check that the catalog servers for this cache are started. Check the configured properties for this server. Verify that the ports that are configured for this server are available on this computer. Restart the execution group to restart this container server.
- Severity
- 20 : Error
- Explanation
- The WebSphere eXtreme Scale container server in this execution group has failed to start. If this container server is the only one for the broker global cache, the cache will not be available for use with message processing nodes.
- BIP7162
- Catalog server <insert_1> in execution group <insert_2> has started successfully.
- Severity
- 0 : Information
- Explanation
- A WebSphere eXtreme Scale catalog server has been started successfully in this execution group for use with the broker global cache.
- Response
- None
- BIP7163
- Container server <insert_1> in execution group <insert_2> has started successfully.
- Severity
- 0 : Information
- Explanation
- A WebSphere eXtreme Scale container server has been started successfully in this execution group for use with the broker global cache.
- Response
- None
- BIP7164
- The message flow failed to connect to the global cache. A client attempted to connect to WebSphere eXtreme Scale grid <insert_1> by using connection string <insert_2>. This connection attempt failed with the following error: <insert_3>. Ensure that the grid is available. If this grid is the broker global cache, look for any previous errors relating to the catalog servers or container servers.
- Severity
- 20 : Error
- BIP7165
- The message flow failed to retrieve map <insert_1> from the global cache. A client attempted to get map <insert_1> from grid <insert_2>. This attempt failed for the following reason: <insert_3>.
- Severity
- 20 : Error
- Response
- Ensure that the map is valid. If you are using WebSphere eXtreme Scale dynamic maps, ensure that the requested map matches a pattern in the deployment policy file.
- BIP7166
- A connectivity exception occurred while interacting with map <insert_1>. A client attempted operation <insert_2> with map <insert_1> from grid <insert_3>. This attempt failed for the following reason: <insert_4>.
- Severity
- 20 : Error
- Response
- Ensure that the grid is available. If this grid is the broker global cache, look for any previous errors relating to the catalog servers or container servers.
- BIP7167
- A duplicate key was encountered while interacting with map <insert_1>. A client attempted operation <insert_2> with map <insert_1> from grid <insert_3>, using key <insert_4>. This attempt failed because an entry already exists with the same key.
- Severity
- 20 : Error
- Response
- This operation requires that a key of the same name does not already exist in the map.
- BIP7168
- An unexpected exception occurred while interacting with map <insert_1>. A client attempted operation <insert_2> with map <insert_1> from grid <insert_3>. This attempt failed for the following reason: <insert_4>.
- Severity
- 20 : Error
- Response
- None
- BIP7169
- A key was not found while interacting with map <insert_1>. A client attempted operation <insert_2> with map <insert_1> from grid <insert_3>, using key <insert_4>. This attempt failed because the key was not found in the map.
- Severity
- 20 : Error
- Response
- This operation requires the specified key to be present in the map.
- BIP7170
- Operation <insert_1> on map <insert_2> has been completed successfully.
- Severity
- 0 : Information
- Explanation
- A client successfully completed operation <insert_1> on map <insert_2> in grid <insert_3>. The data processed by this action was <insert_4>.
- Response
- None
- BIP7171
- An unexpected exception occurred while interacting with grid <insert_1>. Further details of the error are : <insert_2>.
- Severity
- 20 : Error
- Explanation
- An unexpected exception was caught while interacting with a WebSphere eXtreme Scale grid.
- Response
- None
- BIP7172
- An unexpected exception occurred while interacting with map <insert_1>. A client attempted operation <insert_2> with map <insert_1> from grid <insert_3>. Review previous messages to find out why the error occurred.
- Severity
- 20 : Error
- Response
- None
- BIP7173
- An unexpected exception occurred while interacting with map <insert_1>. Review previous messages to find out why the error occurred.
- Severity
- 20 : Error
- Response
- None
- BIP7174
- The port range <insert_1>, specified for the cache manager, is invalid.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Ensure that the port range specified for the cache manager is of the form "startport-endport", and that the following conditions are met:
1. The values for startport and endport are valid numbers between 1 and 65536.
2. The value for startport is less than that for endport.
3. Enough ports are available between startport and endport.
- BIP7175
- The cache manager could not generate a port range.
A list of free ports could not be determined.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Investigate the port range settings for the cache manager on all other brokers on the system.
Specify the ports manually by using the '-r' parameter on the mqsicreatebroker or mqsichangebroker command. Alternatively, complete the following steps:
1. Determine whether one or more brokers are configured to use more ports than necessary.
2. Adjust those brokers to use a smaller port range, if possible, so that this broker can use them instead.
- BIP7176
- The port range <insert_1>, specified for the cache manager, is invalid.
This port range conflicts with that of broker <insert_2> which uses the port range <insert_3>.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Change this broker so that its cache manager port range does not conflict with that of other brokers on the system.
- BIP7177
- The cache manager properties of the execution group are being controlled by a broker level cache policy of <insert_1>, and cannot be changed at this time.
- Severity
- 20 : Error
- Response
- To disable the automatic configuration of the execution group cache manager properties, change the broker cache manager policy to 'none' by using either the 'mqsichangebroker' or 'mqsichangeproperties' commands, or the Message Broker Explorer.
When you have completed this change, configure the execution group cache manager properties again.
- BIP7178
- Authentication details for the security identity <insert_1> specified on the WebSphere eXtreme Scale configurable service <insert_2> cannot be found, or are invalid.
The connection to the remote WebSphere eXtreme Scale instance has failed.
- Severity
- 20 : Error
- Response
- Ensure that the security identity specified is correct, and has been set on the broker using 'mqsisetdbparms'.
If no security is configured on the remote WebSphere eXtreme Scale instance, then ensure that the 'securityIdentity' parameter on the configurable service is set to the empty string.
- BIP7179
- The broker-level port range <insert_1>, specified for the broker-level cache manager, does not contain enough ports to satisfy the requirements of the broker-level cache policy for one or more execution groups in this broker.
The broker global cache might not be available for use with message processing nodes in one or more execution groups in this broker.
- Severity
- 20 : Error
- Response
- Modify the port range settings for the cache manager, so that enough ports are available in the range to satisfy the requirements of the broker-level cache policy. Modify the settings by using either the 'mqsichangebroker' or 'mqsichangeproperties' commands, or the Message Broker Explorer. When you have completed this change, restart your broker.
- BIP7180
- An internal error occurred while processing a broker-level cache policy for one or more execution groups in this broker.
The error is: <insert_1>.
The broker global cache might not be available for use with message processing nodes in one or more execution groups in this broker.
- Severity
- 20 : Error
- Response
- This is an internal error. Please contact your IBM Support Center.
- BIP7181
- The policy <insert_1>, specified for the cache manager, is invalid.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Ensure that the policy specified for the cache manager is one of the following options:
"none"
"default"
"disabled"
- BIP7182
- The WebSphere eXtreme Scale configurable service <insert_1> cannot be found, or it is invalid.
- Severity
- 20 : Error
- Response
- Ensure that the configurable service specified is spelled correctly and that the configurable service is defined on this broker.
- BIP7183
- Container server <insert_1> in execution group <insert_2> failed to start, because the object grid XML file <insert_3> is missing.
- Severity
- 20 : Error
- Explanation
- The WebSphere eXtreme Scale container server in this execution group has failed to start. If this container server is the only one for the broker global cache, the cache will not be available for use with message processing nodes.
- Response
- Ensure that the object grid XML file specified by the property 'objectGridFile' exists and that the file can be accessed by the broker user ID.
- BIP7184
- Container server <insert_1> in execution group <insert_2> failed to start, because the deployment policy XML file <insert_3> is missing.
- Severity
- 20 : Error
- Explanation
- The WebSphere eXtreme Scale container server in this execution group has failed to start. If this container server is the only one for the broker global cache, the cache will not be available for use with message processing nodes.
- Response
- Ensure that the deployment policy XML file specified by the property 'deploymentPolicyFile' exists and that the file can be accessed by the broker user ID.
- BIP7185
- The port range <insert_1>, specified for the cache manager, is invalid.
Only <insert_2> ports are available in this port range. At least <insert_3> ports are required.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Ensure that the port range specified for the cache manager is of the form "startport-endport", and that the following conditions are met:
1. The values for startport and endport are valid numbers between 1 and 65536.
2. The value for startport is less than that for endport.
3. Enough ports are available between startport and endport.
- BIP7186
- Provides administrative information and control for the global cache.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsicacheadmin (brokerName | [-n brokerFileName] | [-cep connectionEndPoints]) -c command [-m mapName]
Command Options:
'brokerName' The name of the broker.
'-n brokerFileName' File containing remote broker connection parameters (*.broker).
'-cep connectionEndPoints' Connection details for the cache catalog server running in a broker. The format of the connectionEndPoints string is <hostname>:<listenerPort>.
'-c command' The command to run against the embedded cache. Valid values for the command are: clearGrid, showMapSizes, placementServiceStatus, routetable, showPlacement, listHosts.
'-m mapName' The name of the map against which to perform the command. This property is required only if the command specified is clearGrid.
- BIP7187
- Output from the mqsicacheadmin command. The output from the WebSphere eXtreme Scale xscmd utility is <insert_1>
- Severity
- 0 : Information
- BIP7188
- The command cannot determine connection details for the WebSphere eXtreme Scale catalog server in broker <insert_1>
- Severity
- 20 : Error
- Response
- Check that the global cache in this broker is enabled, and the broker is running. Alternatively, retry the command, setting the following property, specifying the host name of the computer where the catalog server is located, and the listener port of the catalog server:
-cep hostname&colon.port
- BIP7190
- The WebSphere eXtreme Scale server components in this execution group have not started. The attempt to start the server components has now been running for <insert_1> seconds.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to start one or more WebSphere eXtreme Scale server components in this execution group, but the components failed to start within the specified period of time. The attempt to start the server components will continue in the background. Until the server components start successfully, the broker global cache might not be available for use with message processing nodes in one or more execution groups in this broker.
- Response
- The server components might be slow to start up due to one or more of the following reasons:
1. This system is not capable of starting the server components within the specified time.
2. The configuration for this execution group is incorrect. Check the configured properties for this execution group.
3. Other execution groups containing WebSphere eXtreme Scale server components that communicate with this execution group have not started yet. Ensure that all execution groups are available.
- BIP7191
- The message flow failed to connect to the broker global cache.
The broker has a cache policy of 'disabled'. All cache components in this broker are unavailable.
- Severity
- 20 : Error
- Response
- In order to enable the broker global cache, change the broker cache policy and restart the broker.
Note that the broker cache policy defaults to 'disabled' for brokers migrated from version '8.0.0.0' or earlier.
- BIP7192
- The policy file <insert_1>, specified for the cache manager, is invalid. The file cannot be found or the file cannot be accessed by the broker.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Ensure that the policy file specified for the cache manager exists, and that it can be accessed by the broker.
Alternatively, specify one of the following built-in policies for the cache manager:
"none"
"default"
"disabled"
- BIP7193
- The policy file <insert_1>, specified for the cache manager, is invalid.
The policy file does not contain valid XML, or the XML does not validate against the XML schema for policy files.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Review previous messages to find out why the error occurred.
Ensure that the policy file specified for the cache manager is valid XML, and that it validates against the XML schema for policy files.
The XML schema for policy files is available in the installation directory.
- BIP7194
- The policy in the policy file <insert_1>, specified for the cache manager, is invalid.
No catalog servers are defined in the policy. At least one catalog server must be defined in the policy.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Ensure that at least one catalog server is defined in the policy.
- BIP7195
- The policy in the policy file <insert_1>, specified for the cache manager, is invalid.
The broker, with name <insert_2> and listener host <insert_3>, is not defined in the policy.
The policy must include a definition for this broker.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Ensure that this broker is defined in the policy.
If the broker is already defined, check that the name and listener host specified for this broker match the name and listener host specified in the policy.
- BIP7196
- The current JVM minimum heap size setting of <insert_1> for this execution group is insufficient to run WebSphere eXtreme Scale components that support the global cache.
The JVM minimum heap size will be reset to the default value, and the default value will be stored in the execution group configuration.
The default JVM minimum heap size setting for execution groups that have a broker-level cache manager policy of 'disabled' is <insert_2>.
The default JVM minimum heap size setting for execution groups that have a broker-level cache manager policy that is not 'disabled' is <insert_3>.
It is not possible to configure a JVM minimum heap size smaller than the default setting unless the broker-level cache manager policy is first set to 'disabled'.
- Severity
- 0 : Information
- BIP7197
- An invalid key was encountered while interacting with map <insert_1>. A client attempted operation <insert_2> with map <insert_1> from grid <insert_3> using key <insert_4>.
The type of the key is <insert_5>, which is not valid for use with the global cache.
- Severity
- 20 : Error
- Explanation
- Only certain types of key are valid for use with the global cache.
When using the Java interface, a key must be either a primitive type (byte, boolean, char, short, int, long, float and double), or a string.
Any other Java objects and Java arrays are invalid keys.
- Response
- Change the message flow so that a valid key is used when interacting with the global cache.
- BIP7198
- An invalid value was encountered while interacting with map <insert_1>. A client attempted operation <insert_2> with map <insert_1> from grid <insert_3> using value <insert_4>.
The type of the value is <insert_5>, which is not valid for use with the global cache.
- Severity
- 20 : Error
- Explanation
- Only certain types of values are valid for use with the global cache.
When using the Java interface, a value must implement either the 'Serializable' or 'Externalizable' interface.
Any other Java objects are invalid values.
- Response
- Change the message flow so that a valid value is used when interacting with the global cache.
- BIP7199
- The policy in the policy file <insert_1>, specified for the cache manager, is invalid.
The broker, with name <insert_2> and listener host <insert_3>, is defined more than once in the policy.
The policy must include at most one definition for an individual broker.
The broker configuration has not been changed.
- Severity
- 20 : Error
- Response
- Remove the duplicate entry for the specified broker from the policy file.
- BIP7201
- Tried to create two PubSubResources.
- Severity
- 30 : Severe error
- Explanation
- The internal object which represents state information for publish subscribe resources, must not be created more than once. This error indicates that an attempt was made to create a second instance of such a resource.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7202
- Invalid tag <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- A tag (<insert_1>) found in a configuration message was not understood.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7203
- Missing tag <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- A <insert_1> tag in a configuration message was expected, but not found.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7204
- Exception while creating <insert_1> message flow <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- A problem occurred while trying to create a <insert_1> type of message flow. The exception detail was <insert_2>2
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7205
- Attribute <insert_1> of tag <insert_2> missing from the configuration message.
- Severity
- 30 : Severe error
- Explanation
- The configuration message is invalid. The attribute <insert_1> is required for the <insert_2> tag.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7250
- Unexpected message received on WebSphere Publish/Subscribe interbroker communications queue <insert_1>: PutApplName <insert_2>; additional diagnostic data <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- The broker has read a message from a queue used by the broker to receive messages from WebSphere Publish/Subscribe neighbors and command line requests. The format of the message received by the broker has not been recognized. It may have been put on the wrong queue by an application.
- Response
- The message will be left on the queue and will need to be removed from the queue before the broker will continue to operate normally. Browse queue <insert_1> to determine the source of the invalid message. Remove the offending message from the queue and restart your broker. If the offending message was not put onto the queue by one of your applications, capture the message and all other diagnostic data contained within this message and contact your IBM support center.
- BIP7251
- Invalid state <insert_2> detected for WebSphere Publish/Subscribe neighbor <insert_1> whilst processing control message of type <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- This is an internal error within the broker.
- Response
- Keep all diagnostic information contained within this message and contact your IBM support center.
- BIP7252
- Failed to map <insert_1> parameter/value <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- This is an internal error within the broker.
- Response
- Keep all diagnostic information contained within this message and contact your IBM support center.
- BIP7255
- WebSphere Publish/Subscribe broker <insert_1> is already a neighbor.
- Severity
- 30 : Severe error
- Explanation
- An internal error has occurred while adding WebSphere Publish/Subscribe broker <insert_1> as a neighbor. Broker <insert_1> is already a neighbor.
- Response
- Contact your IBM support center.
- BIP7256
- WebSphere Publish/Subscribe broker <insert_1> is not a neighbor.
- Severity
- 30 : Severe error
- Explanation
- An internal error has occurred within the broker which has resulted in an attempt to remove a WebSphere Publish/Subscribe broker which is not a neighbor.
- Response
- Contact your IBM support center.
- BIP7257
- WebSphere Publish/Subscribe neighbor <insert_1> state <insert_2> unsuitable to be made active.
- Severity
- 30 : Severe error
- Explanation
- An internal error has occurred within the broker which has resulted in an attempt to activate a WebSphere Publish/Subscribe broker which not in a valid state.
- Response
- Contact your IBM support center.
- BIP7258
- A message has been received from unknown WebSphere Publish/Subscribe broker: link identifier <insert_1>.
- Severity
- 10 : Warning
- Explanation
- A message was received from a WebSphere Publish/Subscribe broker which is not known to this broker. A failure response will be sent to the sending broker.
- Response
- No user action required.
- BIP7259
- Message broker <insert_1> has failed to import a migrated subscription: diagnostic information <insert_2>, <insert_3>.
- Severity
- 20 : Error
- Explanation
- The migmqbrk command has been issued to migrate a WebSphere Publish/Subscribe broker. The message broker has failed to import a subscription. The diagnostic information associated with this error is <insert_2> and <insert_3>
- Response
- Contact your IBM support center.
- BIP7260
- Message broker <insert_1> already has a parent WebSphere Publish/Subscribe broker <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The mqsijoinmqpubsub command has been used to join this message broker to a WebSphere Publish/Subscribe broker. This broker already has a parent broker so the command has been rejected.
- Response
- Reissue the mqsijoinmqpubsub command specifying the correct broker to be joined with.
- BIP7261
- An invalid control message from a WebSphere Publish/Subscribe neighbor has been detected: diagnostic information <insert_1>, <insert_2>.
- Severity
- 20 : Error
- Explanation
- This is an internal error.
- Response
- Contact your IBM support center.
- BIP7262
- A WebSphere Publish/Subscribe control message intended for broker <insert_2> has been detected: diagnostic information <insert_1>.
- Severity
- 20 : Error
- Explanation
- This is an internal error.
- Response
- Contact your IBM support center.
- BIP7263
- Unexpected communication received from WebSphere Publish/Subscribe broker <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The broker has received an inter-broker communication from a WebSphere Publish/Subscribe broker that it did not expect. The message was sent by broker <insert_1>. The most likely reason for this message is that the broker topology has been changed while inter-broker communication messages were in transit (for example, on a transmission queue) and that a message relating to the previous broker topology arrived at a broker in the new topology.
- Response
- If the broker topology has changed and the broker named in the message is no longer related to the broker issuing this message, this message can be ignored. If the mqsiclearmqpubsub was issued to unilaterally remove knowledge of broker <insert_1> from this broker, the clrmqbrk command should also be used at broker <insert_1> to remove knowledge of this broker.
- BIP7264
- Message broker could not send completion code <insert_1> to a command line request.
- Severity
- 10 : Warning
- Explanation
- An mqsijoinmqpubsub or mqsiclearmqpubsub request has been made from the command line. The request has been processed by the message broker, but a failure has occurred when trying to respond to the reply queue used by the command line program. If the completion code is zero, the request succeeded. A nonzero completion code means that the request failed or was rejected by the message broker.
- Response
- Look for a previous error message, usually BIP2623, outlining the cause of the problem. If message BIP2623 reports a WebSphere MQ reason code of 2085 or 2052, this means that the temporary reply queue used by the command line program no longer exists, perhaps because Ctrl-C has been pressed or the request has timed out. Any other reason code is unexpected and should be looked up in the WebSphere MQ Application Programming Reference manual.
- BIP7265
- Bad data returned from WebSphere Publish/Subscribe database table: diagnostic information <insert_1>, <insert_2>.
- Severity
- 20 : Error
- Explanation
- This is an internal error within the broker.
- Response
- Keep all diagnostic information contained within this message and contact your IBM support center.
- BIP7266
- Invalid WebSphere publish/subscribe migration message detected on queue <insert_3>: diagnostic information <insert_1>, <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker has been processing migration messages arriving on a queue as a result of the migmqbrk command being issued against an WebSphere publish/subscribe broker. The message broker has detected an invalid message on this queue.
- Response
- This is an internal error, contact your IBM support center with the diagnostic information. The migration attempt can be retried by issuing the migmqbrk command again. If repeated attempts all fail with this error, providing both WebSphere and WebSphere Message Broker traces will help with problem resolution.
- BIP7267
- Invalid WebSphere Publish/Subscribe control message detected on queue <insert_3>: diagnostic information <insert_1>, <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- The message broker has been processing messages on a queue. Messages are sent to the queue by neighboring WebSphere Publish/Subscribe brokers or as a result of the mqsijoinmqpubsub or mqsiclearmqpubsub commands being issued. The message broker has detected an invalid message on the queue. The message will be backed out and retried until such time as the backout threshold of the queue has been exceeded at which time it will be put to the dead letter queue.
- Response
- This is an internal error, contact your IBM support center. The diagnostic information will need to be reported along with the message which is causing the problem. To recover from this problem, set an appropriate backout threshold for the queue which will cause the invalid message to be put to the dead letter queue. From here the message can be captured by running the amqsbcg sample program against the dead letter queue and saving the output to a file. If you do not have a dead letter queue, you will need to remove the invalid message manually from the queue. The message broker will need to be stopped and again you should capture the invalid message by running the amqsbcg sample program against the queue before the message is removed.
- BIP7268
- WebSphere Publish/Subscribe broker <insert_1> is not known by this message broker.
- Severity
- 10 : Warning
- Explanation
- The mqsiclearmqpubsub command has been used to remove WebSphere Publish/Subscribe broker <insert_1>. This broker is not known by this message broker so the command has been rejected.
- Response
- Reissue the mqsiclearmqpubsub command specifying the correct broker to be removed.
- BIP7269
- WebSphere Publish/Subscribe broker <insert_1> is already known by this message broker.
- Severity
- 10 : Warning
- Explanation
- The mqsijoinmqpubsub command has been used to join this message broker to WebSphere Publish/Subscribe broker <insert_1>. This broker is already known so the command has been rejected.
- Response
- Reissue the mqsijoinmqpubsub command specifying the correct broker to be joined with.
- BIP7270
- Attempt to join with parent WebSphere Publish/Subscribe broker <insert_1> failed because a parent <insert_2> already exists.
- Severity
- 10 : Warning
- Explanation
- The mqsijoinmqpubsub command has been used to join this message broker to WebSphere Publish/Subscribe broker. The attempt has been rejected because the message broker already has a parent broker.
- Response
- The message broker can only be joined to a single parent WebSphere Publish/Subscribe broker. To change the parent broker you will need to remove the existing parent. This can be achieved by issuing mqsiclearmqpubsub at this broker and clrmqbrk at the WebSphere Publish/Subscribe broker.
- BIP7271
- Loop joining message broker <insert_1> to WebSphere Publish/Subscribe broker <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The mqsijoinmqpubsub command has been used to join a message broker to a parent WebSphere Publish/Subscribe broker. The action has caused a loop to created in the WebSphere Publish/Subscribe hierarchy.
- Response
- Use the mqsiclearmqpubsub at the broker and clrmqbrk at the WebSphere Publish/Subscribe broker to remove the loop from the hierarchy.
- BIP7272
- WebSphere Publish/Subscribe migration has started for message broker <insert_1>.
- Severity
- 0 : Information
- Explanation
- The migmqbrk command has been issued to start migration of a WebSphere Publish/Subscribe broker.
- Response
- No user action required. A further message will be issued when the migration has finished.
- BIP7273
- WebSphere publish/subscribe migration has completed successfully for message broker <insert_1>.
- Severity
- 0 : Information
- Explanation
- The migration of the WebSphere publish/subscribe broker has been successful.
- Response
- All subscriptions, retained publications and local publisher registrations have been loaded into message broker <insert_1>. The message broker will automatically start to process new subscription messages arriving on queue SYSTEM.BROKER.CONTROL.QUEUE. You now need to manually deploy publication message flows for each of the stream queues which were supported by the WebSphere publish/subscribe broker. Guidance for this task can be found in the WebSphere Message Broker Introduction and Planning guide.
- BIP7274
- WebSphere Publish/Subscribe migration has failed for message broker <insert_1> with reason code <insert_2>.
- Severity
- 20 : Error
- Explanation
- An attempt has been made to migrate a WebSphere Publish/Subscribe broker. This has failed with a reason code of <insert_2>.
- Response
- Investigate the reason for the failure. Look for previous messages issued by message broker <insert_1> and also look for any WebSphere MQ messages issued by the migmqbrk command. The migration can be retried by issuing the migmqbrk command again. If repeated migration attempts all fail then you should contact your IBM support center.
- BIP7275
- Unexpected message of type <insert_2> received from WebSphere Publish/Subscribe broker <insert_1>.
- Severity
- 20 : Error
- Explanation
- A unexpected message has been received from a neighboring WebSphere Publish/Subscribe broker.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7276
- WebSphere Message Broker broker has failed to join with WebSphere publish/subscribe broker <insert_1>1 for reason <insert_2>.
- Severity
- 20 : Error
- Explanation
- The mqsijoinmqpubsub command has been issued to join with WebSphere publish/subscribe broker <insert_1>. The WebSphere Message Broker broker attempted to register as a child of the WebSphere publish/subscribe broker but received an exception response indicating that this was not possible.
- Response
- Investigate why the problem occurred and take appropriate action to correct the problem. The problem is likely to be caused by the parent broker not yet existing, or a problem with the SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS queue at the parent broker. Once the problem has been resolved, the mqsijoinmqpubsub command should be reissued to retry the joining of the two brokers.
- BIP7277
- WebSphere Message Broker broker has failed to subscribe to WebSphere publish/subscribe broker <insert_1>. Reason codes <insert_2> and <insert_3>.
- Severity
- 20 : Error
- Explanation
- The strmqbrk command has been issued at WebSphere publish/subscribe broker <insert_1> nominating this WebSphere Message Broker broker as its parent. While handling the resultant join request the WebSphere Message Broker broker sent an internal subscription to the administration stream of broker <insert_1>. The subscription failed and as a result the two brokers are not yet joined together. The broker will reissue the subscription immediately.
- Response
- Investigate why the problem occurred and take appropriate action to correct the problem. The most likely cause of this failure is a problem with the SYSTEM.BROKER.CONTROL.QUEUE at broker <insert_1>, or a problem with the definition of route between this broker and broker <insert_1>. When the problem has been rectified this error message will no longer be issued. If you cannot rectify the problem then consider reversing the attempted joining of the two brokers. This can be achieved using the clrmqbrk command at broker <insert_1>1 and the mqsiclearmqpubsub command at this broker.
- BIP7278
- WebSphere Message Broker broker has failed to propagate a subscription to WebSphere publish/subscribe broker <insert_1>. Reason codes <insert_2> and <insert_3>.
- Severity
- 20 : Error
- Explanation
- An application has either registered or deregistered a global subscription. The broker has attempted to propagate the subscription change to WebSphere publish/subscribe broker <insert_1> but the request has not been successful. The WebSphere Message Broker broker will immediately attempt to refresh the state of all global subscriptions at broker <insert_1>. Until the subscription state has been successfully refreshed, messages published through broker <insert_1> might not reach this broker.
- Response
- Investigate why the problem occurred and take appropriate action to correct the problem. The most likely cause of this failure is a problem with the SYSTEM.BROKER.CONTROL.QUEUE at broker <insert_1>, or a problem with the definition of route between this broker and broker <insert_1>. When the problem has been rectified, this error message will no longer be issued.
- BIP7279
- WebSphere Message Broker broker failed to inform parent WebSphere publish/subscribe broker <insert_1>1 of a new broker for reason <insert_2>.
- Severity
- 10 : Warning
- Explanation
- When a new broker is added to an WebSphere publish/subscribe network the integrity of the new hierarchy is checked by forwarding notification of the new broker to other brokers in the network. The WebSphere Message Broker broker has failed to notify its parent on queue manager <insert_1> of the new broker. A failure to notify a broker of a new broker will mean that loop detection cannot be performed for the new broker.
- Response
- Diagnose and correct the problem on the parent queue manager. One possible reason for this is that the parent broker does not yet exist.
- BIP7280
- Message broker failed to propagate a delete publication command on topic <insert_3> to WebSphere Publish/Subscribe broker <insert_1> for reason <insert_2>.
- Severity
- 20 : Error
- Explanation
- When an application issues a delete publication command to delete a global publication, the command is propagated to all neighboring WebSphere Publish/Subscribe brokers. The delete publication command has failed to be forwarded to from the broker, and as such the retained publication on the topic will not have been deleted.
- Response
- Investigate why the delete publication for the topic has failed, and take the appropriate action to recover the failed command. It is likely that the delete publication message sent to the broker will be present on a dead letter queue either at one or other broker.
- BIP7281
- Request <insert_1> from WebSphere publish/subscribe broker <insert_3> contains an invalid topic <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The broker has received a request from neighboring a WebSphere publish/subscribe broker. The request contained an invalid topic and will be ignored.
- Response
- In a mixed network of WebSphere Message Broker and WebSphere publish/subscribe brokers it is not possible for information to flow between the two types of broker on topics which contain wildcard characters # or +. Client applications within the WebSphere publish/subscribe network need to be modified to use topics which do not contain characters which are invalid to the WebSphere Message Broker broker.
- BIP7282
- mqsijoinmqpubsub command from broker <insert_1> rejected because it named a WebSphere Message Broker broker <insert_2> instead of an WebSphere publish/subscribe broker as parent.
- Severity
- 10 : Warning
- Explanation
- The command mqsijoinmqpubsub named an WebSphere publish/subscribe broker as its parent. This has been rejected because the named broker is an WebSphere Message Broker broker. The two brokers have not been joined together.
- Response
- Use the Message Broker Toolkit to join the two WebSphere Message Broker brokers together.
- BIP7283
- Message broker is waiting for WebSphere Publish/Subscribe migration.
- Severity
- 0 : Information
- Explanation
- The broker has been created in migration mode. No publication message flows should be created until migration has completed successfully.
- Response
- Use the migmqbrk command to migrate the WebSphere Publish/Subscribe broker. If the broker has been created incorrectly, the broker will need to be deleted and recreated.
- BIP7284
- WebSphere publish/subscribe inter-broker queue <insert_1> cannot be accessed.
- Severity
- 10 : Warning
- Explanation
- The broker has WebSphere publish/subscribe neighbors. These neighbors communicate with this broker using queue <insert_1>. The queue cannot be accessed which will affect inter-operability with all WebSphere publish/subscribe neighbors.
- Response
- Check whether queue <insert_1> exists. If it does exist, ensure that the queue manager is running and restart the broker. This will allow the broker to process messages from WebSphere publish/subscribe neighbors. If the queue does not exist, consult the WebSphere Message Broker Introduction and Planning manual for guidance about how to define the queue. After the queue has been defined the broker will need to be restarted.
- BIP7285
- Subscription to topic <insert_1> will not be propagated to WebSphere publish/subscribe neighbors.
- Severity
- 10 : Warning
- Explanation
- A subscription to topic <insert_1> has been received. This will not be propagated to any of the WebSphere publish/subscribe neighbors of this broker.
- Response
- You can ignore this message if the client making the subscription to topic <insert_1> is not interested in any potential matching publications made within the WebSphere publish/subscribe part of your mixed broker network. If this is not the case, the client will need to change its subscription to something more specific. Consult the WebSphere Message Broker Introduction and Planning guide for more information about using wildcard subscriptions in a mixed broker network.
- BIP7286
- Message broker needs to be restarted after Publish/Subscribe migration.
- Severity
- 0 : Information
- Explanation
- The Message Broker <insert_1> has been created in migration mode. Once migration has completed, the Message Broker needs to be restarted
- Response
- Use the migmqbrk command to migrate the WebSphere Publish/Subscribe broker. Once the migration is complete, The Message Broker needs to be restarted.
- BIP7350
- Tried to create two data flow stores.
- Severity
- 30 : Severe error
- Explanation
- The internal object which represents the data store for publish/subscribe information, must not be created more than once. This error indicates that an attempt was made to create a second instance of such a resource.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7351
- No data source supplied, so data flow configuration will not be persistent.
- Severity
- 10 : Warning
- Explanation
- The start up parameters for the broker did not include a database name, so this configuration will not be saved anywhere.
- Response
- If persistence is required, ensure a database name is provided in the start up parameters for the broker.
- BIP7352
- Some (but not all) tables exist, pub/sub state will not be persistent.
- Severity
- 10 : Warning
- Explanation
- Some of the tables the broker requires in the database were missing so the broker state will not be saved anywhere.
- Response
- The database may need to be rebuilt.
- BIP7353
- Tried to access a nonexistent data flow store.
- Severity
- 30 : Severe error
- Explanation
- An attempt was made to read from or write to a database that has not been properly initialized.
- Response
- Examine the system log for indications of a startup failure.
- BIP7354
- The multicast topics file name is empty.
- Severity
- 30 : Severe error
- Explanation
- The property MULTICAST_TOPICS_CONFIG_FILE does not contain a file name.
- Response
- Set the property MULTICAST_TOPICS_CONFIG_FILE to a valid multicast topics file name.
- BIP7355
- Unable to locate file: <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The broker was unable to find the multicast topics file: <insert_1>.
- Response
- Check that the multicast topic file exists and try again.
- BIP7356
- Unable to parse entry for topic <insert_1>, <insert_2> is not a valid boolean. Entries must of the form <topic>=<true|false>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred while parsing the multicast topics file.
- Response
- Correct the multicast topics file and restart the broker.
- BIP7357
- Message protection (Quality of Protection) has been enabled for the JMS/IP Input Node.
- Severity
- 0 : Information
- Explanation
- The broker has enabled message protection (Quality of Protection) for the JMS/IP Input Node.
- Response
- No user action required.
- BIP7358
- The new message protection (Quality of Protection) updates deployed have been deferred.
- Severity
- 10 : Warning
- Explanation
- The new message protection (Quality of Protection) updates deployed have been deferred.
- Response
- The broker must be restarted before the updated Quality of Protection settings will take effect.
- BIP7359
- The keyring file was not found at it's specified location.
- Severity
- 30 : Severe error
- Explanation
- The keyring file used for SSL Authentication was not found at it's specified location.
- Response
- Ensure that this file exists and that the broker has sufficient permission to access this file.
- BIP7360
- The pass phrase file was not found at it's specified location.
- Severity
- 30 : Severe error
- Explanation
- The pass phrase file used for SSL Authentication was not found at it's specified location.
- Response
- Ensure that this file exists and that the broker has sufficient permission to access this file.
- BIP7361
- The pass phrase file specified is either invalid or does not contain the correct password to access the SSL keyring file.
- Severity
- 30 : Severe error
- Explanation
- The pass phrase file specified is either invalid or does not contain the correct password to access the SSL keyring file.
- Response
- The pass phrase file specified is either invalid or does not contain the correct password to access the SSL keyring file.
- BIP7362
- The keyring file used for SSL Authentication has expired.
- Severity
- 30 : Severe error
- Explanation
- The keyring file used for SSL Authentication has expired.
- Response
- The keyring file used for SSL Authentication has expired.
- BIP7363
- The keyring file specified is invalid and cannot be read.
- Severity
- 30 : Severe error
- Explanation
- The keyring file specified is invalid and cannot be read.
- Response
- The keyring file specified is invalid and cannot be read.
- BIP7364
- The usernameserver has propagated an authentication protocol requiring SSL certificates although the certificate and / or pass phrase have not been specified.
- Severity
- 30 : Severe error
- Explanation
- The usernameserver has propagated an authentication protocol requiring SSL certificates although the certificate and / or pass phrase have not been specified.
- Response
- The usernameserver has propagated an authentication protocol requiring SSL certificates although the certificate and / or pass phrase have not been specified.
- BIP7365
- An error occurred starting SSL Authentication: <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Refer to previous event messages for likely causes of this failure
- Response
- An SSL Exception occurred. Please correct the problem then restart the broker.
- BIP7366
- An error occurred starting Real-time node with name <insert_1> listening on port <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred starting Real-time node with name <insert_1> listening on port <insert_2>. This is normally because the Real-time node can not open the port specified.
- Response
- Find a port that is not being used by another application or node. Change the Real-time node in the Message Broker Toolkit and redeploy the messageflow.
- BIP7370
- A new multicast configuration has been deployed. The new configuration will not take effect until the broker is restarted.
- Severity
- 10 : Warning
- Explanation
- A new multicast configuration has been deployed. The new configuration will not take effect until the broker is restarted.
- Response
- The broker must be restarted for the settings to take effect.
- BIP7371
- The broker has bound to interface <insert_1> for multicast.
- Severity
- 0 : Information
- Explanation
- The broker will use interface <insert_1> for multicast transmission.
- Response
- This message is for information only, no response is required.
- BIP7372
- An attempt to <insert_1> one or more multicast topics failed as the broker is not enabled for multicast.
- Severity
- 10 : Warning
- Explanation
- Although a deploy to the broker was successful, an attempt to <insert_1> one or more multicast topics failed because the broker is not enabled for multicast. The <insert_1> request(s) will not be performed.
- Response
- To correct this action, the broker needs to be enabled for multicast and a complete re-deploy of the topic tree needs to be made.
- BIP7373
- RMM Warning: <insert_1>1
- Severity
- 10 : Warning
- Explanation
- RMM Warning: <insert_1>1
- Response
- This is a warning message. No user action required.
- BIP7374
- RMM Error: <insert_1>1
- Severity
- 30 : Severe error
- Explanation
- RMM Error: <insert_1>1
- Response
- This is an internal error. Contact your IBM support center.
- BIP7375
- RMM Error: Missing configuration entry: <insert_1>1
- Severity
- 30 : Severe error
- Explanation
- The configuration entry <insert_1> is missing.
- Response
- Change the multicast configuration and try again.
- BIP7376
- RMM Error: Bad argument. Parameter <insert_1>, value: <insert_2>2
- Severity
- 30 : Severe error
- Explanation
- Multicast support failed to start because of illegal configuration values.
- Response
- Check multicast configuration and try again.
- BIP7377
- RMM Error: Socket creation failed. Port:<insert_1>1
- Severity
- 30 : Severe error
- Explanation
- Failed to create a socket. This may indicate a host network configuration problem.
- Response
- Failed to create a socket. This may indicate a host network configuration problem. For example, trying to create a multicast socket when multicast is disabled on the host.
- BIP7378
- RMM Error: Multicast interface setting to <insert_1> failed
- Severity
- 30 : Severe error
- Explanation
- Failed to set the interface on the multicast socket. This may indicate a wrong configured interface address.
- Response
- This may indicate a wrong configured interface address. Check the multicast interface setting and try again.
- BIP7379
- RMM Error: Service <insert_1> interrupted
- Severity
- 30 : Severe error
- Explanation
- The multicast service <insert_1> was interrupted.
- Response
- This is an internal error. Contact your IBM support center.
- BIP7380
- RMM Error: Failed to set Time-To-Live to: <insert_1>1
- Severity
- 30 : Severe error
- Explanation
- Failed to set the Time-To-Live parameter on the multicast socket
- Response
- This is an internal error. Contact your IBM support center.
- BIP7381
- RMM Error: Failed to join multicast group <insert_1>1
- Severity
- 30 : Severe error
- Explanation
- Failed to join a multicast group address. This may indicate of a multicast network configuration problem.
- Response
- A possible cause for this problem is a configured system limit on the maximum number of multicast groups.
- BIP7382
- RMM Error: Failed to leave multicast group <insert_1>1
- Severity
- 30 : Severe error
- Explanation
- Failed to leave a multicast group address. This may indicate a multicast network configuration problem.
- Response
- Check your multicast group address configuration and try again.
- BIP7383
- RMM Error: Failed to allocate memory: <insert_1> bytes
- Severity
- 30 : Severe error
- Explanation
- Failed to allocate enough memory to deal with an incoming message. Stream data reception stops.
- Response
- Consider increasing the JVM memory heap size or lowering messaging rate of other transmitters.
- BIP7384
- RMM Error: Encoding <insert_1> not supported on this host
- Severity
- 30 : Severe error
- Explanation
- Failed to encode/decode a String because the local operating system does not support the specified encoding.
- Response
- This is an internal error. Contact your IBM support center.
- BIP7385
- RMM Error: Failed to resolve the address: <insert_1>1
- Severity
- 30 : Severe error
- Explanation
- Failed to resolve an internet address.
- Response
- This is probably because of a DNS problem, check your DNS setting and try again.
- BIP7386
- RMM Error: Failed to set socket buffer <insert_1> to <insert_2>2
- Severity
- 30 : Severe error
- Explanation
- Failed to set the buffer size on the socket.
- Response
- This probably indicates a configured limitation in the operating system. This warning may lead to inferior transport performance. Check operating system network configuration.
- BIP7387
- RMM Error: Received packet larger than configured PacketBufferLength <insert_1> from <insert_2>2
- Severity
- 30 : Severe error
- Explanation
- Another machine sent a packet longer than the configured buffer length for incoming packets.
- Response
- This might indicate that another application is using multicast with a larger configured packet size or that a malicious sender attempts to send large packets to local machine. Check identity and configuration of the specified sending machine.
- BIP7388
- RMM Error: Terminating Service/Thread <insert_1> following unrecoverable problem
- Severity
- 30 : Severe error
- Explanation
- A multicast thread had to stop, due to a general unexpected error.
- Response
- This is an internal error. Contact your IBM support center.
- BIP7389
- RMM Error: Failed to send a packet to <insert_1>1
- Severity
- 30 : Severe error
- Explanation
- Failed to send a data packet because of a network connectivity problem.
- Response
- Check network connectivity and try again.
- BIP7390
- RMM Error: Clock moved <insert_1>1
- Severity
- 30 : Severe error
- Explanation
- RMM Error: Clock moved <insert_1>1
- Response
- No user action required.
- BIP7391
- RMM Error: Failed to set socket parameter <insert_1> to <insert_2>2
- Severity
- 30 : Severe error
- Explanation
- Failed to set socket parameter <insert_0> to <insert_1>. Exception is <insert_2>.
- Response
- Check operating system network configuration.
- BIP7392
- The broker was unable to load the native library required for PGM/IP.
- Severity
- 30 : Severe error
- Explanation
- A native library required for PGM/IP could not be loaded. The broker will not be able to provide multicast support.
- Response
- Check that the broker has been installed correctly and contact you IBM support center
- BIP7393
- The broker multicast protocol has been set to PGM/IP. However, the broker is not running with sufficient authority. The broker will revert to UDP encapsulated PGM.
- Severity
- 10 : Warning
- Explanation
- PGM/IP requires the broker to be run with administrator privileges. The broker has been started without this authority. PGM/IP will not be available.
- Response
- Restart the broker with administrator privileges to use PGM/IP.
- BIP7401
- Successfully cloned broker.
- Severity
- 0 : Information
- Explanation
- Broker <insert_1> has been successfully registered as a publish/subscribe clone of broker <insert_2>.
- Response
- No user action required.
- BIP7402
- Failed to connect to cloned broker's Queue Manager <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The Queue Manager <insert_1> specified by the publish/subscribe clone broker request could not be opened.
- Response
- Check that the queue manager specified is the correct one for the broker you want to register as a clone.
- BIP7403
- Incorrect Broker name received during publish/subscribe cloning registration.
- Severity
- 30 : Severe error
- Explanation
- The Broker name <insert_1> specified by the publish/subscribe clone broker request did not match the broker associated with Queue Manager <insert_2>.
- Response
- Check that the queue manager specified is the correct one for the broker you want to register as a clone.
- BIP7404
- Neighbor (<insert_1>) is already known as a publish/subscribe neighbor.
- Severity
- 30 : Severe error
- Explanation
- The Neighbor <insert_1> is already known as a publish/subscribe neighbor and can not be created as a clone.
- Response
- Either remove broker <insert_1> as a Neighbor and retry the command, or choose another broker to be a clone.
- BIP7405
- Blank Broker Name <insert_1> or blank Queue Manager Name <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- Blank Broker Name <insert_1> or blank Queue Manager Name <insert_2>.
- Response
- Check that you have specified values for the Broker Name, or Queue Manager name. Also check that the command contains \" for the value data. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n clonedPubSubBrokerList -v \\"Broker1,QM1\\"
- BIP7406
- The following database table is missing: <insert_1>.
- Severity
- 10 : Warning
- Response
- Take corrective action and re-try the operation.
- BIP7407
- Publish/Subscribe subscriptions recovery started. Found <insert_1> subscriptions.
- Severity
- 0 : Information
- Explanation
- The Publish/Subscribe broker is recovering subscriptions from the broker's database.
- Response
- This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
- BIP7408
- The broker is being run using Java version <insert_1>, not the version it was shipped with.
- Severity
- 10 : Warning
- Explanation
- The broker is running a version of Java it was not shipped with. This may result in unexpected behavior.
- Response
- Check that the broker profile has been run before starting the broker and insure that the library path contains the broker JRE lib directories.
- BIP7409
- The broker was unable to create a JVM. The return code indicates that an unrecognized option was passed in to it. The broker may be being run with a different level of Java than it was shipped with.
- Severity
- 30 : Severe error
- Explanation
- The creation of the broker JVM failed with a return code indicating that an argument was not recognized. It is likely that this has been cause by the broker trying to run a different level of Java than it was shipped with.
- Response
- Check that the broker profile has been run before starting the broker and insure that the library path contains the broker JRE lib directories.
- BIP7410
- Publish/Subscribe subscriptions recovery. Recovered <insert_1> subscriptions.
- Severity
- 0 : Information
- Explanation
- The Publish/Subscribe broker is recovering subscriptions from the broker's database.
- Response
- This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
- BIP7411
- Process <insert_1>(ID) could not be initialized with a JVM heap space request of (<insert_2>(min), <insert_3>(max)). Instead, the process has been started with a request of (<insert_4>(min), <insert_5>(max)).
- Severity
- 10 : Warning
- Explanation
- The original requested JVM heap space requirements could not be satisfied because of a shortage of physical memory.
- Response
- Check that the JVM heap space requirements have been correctly specified and ensure that the machine has enough memory to support the request.
- BIP7412
- Broker JVM startup: the specified JVM debug port (<insert_1>) is already in use.
- Severity
- 10 : Warning
- Explanation
- The broker JVM has been requested to use a TCPIP port for attaching a program to debug your code. The specified TCPIP port number is in use by another application so no tool to debug your code can be attached.
- Response
- Stop other applications from using the specified port, or use the mqsichangeproperties command to change the JVM debug port. You must restart the broker, in either case, for the changes to take effect.
- BIP7413
- Broker JVM startup: an exception occurred while trying to verify whether the specified JVM debug port (<insert_1>) is already in use. Exception details: <insert_2>
- Severity
- 10 : Warning
- Explanation
- The broker JVM has been requested to use a TCPIP port for attaching a program to debug your code, but an exception occurred while trying to verify whether the specified TCPIP port number is in use by another application. The port will therefore not be enabled for debug purposes.
- Response
- Check the exception details, and also look for other system log messages that may indicate a problem with accessing the socket information for the port. Verify that the Domain Name Server is available.
- BIP7451
- HotSwap deploy succeeded. The following AppDomains were reloaded: <insert_1>.
- Severity
- 0 : Information
- Explanation
- As a result of a HotSwap deploy to the ApplicationBase directory <insert_2> the specified AppDomains were reloaded.
- Response
- No user action required.
- BIP7452
- A HotSwap deploy failed. The assembly <insert_1> could not be loaded in the AppDomain <insert_2> for the ESQL routine <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- An exception was found while reloading the AppDomain <insert_2> following a HotSwap deploy of the assembly <insert_1>.
- Response
- Check the error messages that follow to determine why the assembly failed to load then HotSwap deploy a new version of the assembly that fixes the problems found.
- BIP7453
- (<insert_1>, <insert_2>) : The ESQL routine <insert_3> tried to call the .NET method <insert_4> from assembly <insert_5> in AppDomain <insert_6>. This routine cannot be called as a previous HotSwap deploy failed.
- Severity
- 30 : Severe error
- Explanation
- The routine <insert_3> cannot be called as there is an error from a previous HotSwap deploy failure.
- Response
- See the previous messages to determine why the HotSwap deploy failed. Correct the HotSwap deploy failure and complete a HotSwap deploy of a new version of the assembly that fixes the problems found during the HotSwap deploy.
- BIP7454
- The HotSwap deploy facility found an error while monitoring the Application Base <insert_2> and is stopping. The error code found was <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An error was found that required the HotSwap deploy facility to stop. The execution group can continue, but new HotSwap deploys for any AppDomain cannot be processed until after the execution group is restarted.
- BIP7455
- The HotSwap deploy facility found an error while monitoring an Application Base and is stopping. The error code encountered was <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An error was found that required the HotSwap deploy facility to stop. The execution group can continue, but new HotSwap deploys for any AppDomain cannot be processed until after the execution group is restarted.
- BIP7456
- (<insert_1>, <insert_2>) : The .NET CLR has not been loaded, so ESQL cannot run the .NET method <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- The ESQL routine <insert_4> could not run the .NET method <insert_3> from the assembly <insert_5>.
- Response
- Check that the full .NET framework V4 is installed correctly and that the Message Broker assemblies are present in the GAC.
- BIP7457
- The .NET CLR has not been loaded, so the .NETCompute node <insert_1> cannot start the class <insert_2> from the assembly <insert_3> in the AppDomain <insert_4>.
- Severity
- 30 : Severe error
- Explanation
- The .NETCompute node <insert_1> could not start the class <insert_2> from the assembly <insert_3> as the CLR has not been loaded by the execution group.
- Response
- Check that the full .NET framework V4 is installed correctly and that the Message Broker assemblies are present in the GAC.
- BIP7458
- (<insert_1>, <insert_2>) : An error was found when trying to resolve the .NET class and method <insert_3> from assembly <insert_5>, which is referred to by the ESQL routine <insert_4>.
- Severity
- 20 : Error
- Explanation
- The .NET method <insert_3> from assembly <insert_5> in location <insert_6> could not be found. Further messages are generated that explain the error in more detail.
- Response
- Correct the error in node <insert_1>, around line and column <insert_2>, then redeploy. Make sure that the assembly is present and accessible in the location specified. If the assembly is on a "mapped drive" or on a UNC path, make sure that the drive or path is visible in the session the execution group is running in. Also ensure that the broker's user id has permission to execute the assembly. If you are using a Configurable Service, ensure that its ApplicationBase is set to the correct location of the assembly.
- BIP7459
- (<insert_1>, <insert_2>) : An error was found when trying to resolve the .NET class or method <insert_3> from assembly <insert_5>, which is referred to by the ESQL routine <insert_4>.
- Severity
- 20 : Error
- Explanation
- The .NET method <insert_3> from assembly <insert_5> could not be found. Further messages are generated that explain the error in more detail.
- Response
- Correct the error in node <insert_1>, around line and column <insert_2>, then redeploy. You might be able to correct the error by specifying the full path to the assembly or by using a configurable service to set the Application Base.
- BIP7460
- (<insert_1>, <insert_2>) : The routine <insert_3> made an attempt to pass a REFERENCE to a SHARED ROW variable to a .NET method. This is not supported.
- Severity
- 20 : Error
- Explanation
- A REFERENCE to a SHARED ROW variable cannot be passed to a .NET method.
- Response
- Correct the error in node <insert_1>, around line and column <insert_2>, then redeploy.
- BIP7461
- Node <insert_8>: Running .NET method <insert_3> in AppDomain <insert_7> derived from (<insert_1>, <insert_2>). Parameters passed <insert_4>. Resulting parameter values <insert_5>. Return value <insert_6>.
- Severity
- 0 : Information
- BIP7462
- (<insert_1>, <insert_2>) : An error occurred while running the .NET method <insert_3> in AppDomain <insert_5>. The parameters passed to the method were <insert_4>.
- Severity
- 20 : Error
- Explanation
- See other error messages for more information about this error.
- BIP7463
- (<insert_1>, <insert_2>) : LANGUAGE 'CLR' and LANGUAGE '.NET' routines are only supported on Windows.
- Severity
- 30 : Severe error
- Explanation
- The ESQL routines can only call .NET methods on Windows.
- Response
- Correct the LANGUAGE error and redeploy.
- BIP7464
- The .NET method <insert_1> has an invalid parameter type that is not in the list of supported CLR parameter types or is of the wrong direction.
- Severity
- 20 : Error
- Explanation
- One or more of the parameters to the specified .NET method <insert_1> are not in the list of supported CLR parameter types or are of the wrong direction. Ensure that all parameters to the CLR method are in the list of supported parameter datatypes and directions.
- Response
- Examine and correct the SQL program.
- BIP7465
- AppDomain <insert_1> tried to use <insert_2> as its Application Base when loading assembly <insert_3>. This location cannot be used as an Application Base.
- Severity
- 30 : Severe error
- Explanation
- The root of a drive cannot be used for the Application Base of an AppDomain.
- Response
- Change the Application Base and redeploy.
- BIP7466
- AppDomain <insert_1> tried to load an assembly <insert_2> which has a relative path.
- Severity
- 30 : Severe error
- Explanation
- Assemblies can be specifed with a fully qualified path or as a simple name but they cannot be specified with a relative path.
- Response
- Qualify the assembly name and redeploy.
- BIP7467
- The AppDomain <insert_1> (Id: <insert_4>) with the Application Base <insert_2> was referenced with a different Application Base of <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- An AppDomain can be referenced by more than one user, but each user must specify the same Application Base. Although an AppDomain can have only one Application Base, multiple AppDomains can share that Application Base.
- Response
- Change one of the Application Bases so that both are the same, or rename one of the AppDomains to create two different AppDomains.
- BIP7468
- An error <insert_1> was found while unloading the AppDomain <insert_2> with ID <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- If this error continues, restart the execution group.
- BIP7469
- The HotSwap deploy facility found an error while reloading an AppDomain and is stopping. The error code found was <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An error was found that required the HotSwap deploy facility to stop. The execution group can continue, but new HotSwap deploys for any AppDomain cannot be processed until after the execution group is restarted.
- BIP7470
- The Version, Culture and PublicKeyToken properties for the assembly <insert_1> must all be specifed together, or none of them should be specified.
- Severity
- 30 : Severe error
- Explanation
- Specify all three assembly properties for Version, Culture and PublicKeyToken, or remove them. The missing property or properties are <insert_2>.
- BIP7471
- The .NETCompute Node <insert_1> tried to call the Evaluate method from the class <insert_4> within the assembly <insert_2> in the AppDomain <insert_3>. This method cannot be called as a previous HotSwap deploy failed.
- Severity
- 30 : Severe error
- Explanation
- The Evaluate method for this node cannot be called as there is an error from a previous HotSwap deploy failure.
- Response
- See the previous messages to determine why the HotSwap deploy failed. Correct the HotSwap deploy failure and complete a HotSwap deploy of a new version of the assembly that fixes the problems found during the HotSwap deploy.
- BIP7472
- Running the Evaluate method of the .NETCompute node <insert_1> from the assembly <insert_2> in the AppDomain <insert_3>.
- Severity
- 10 : Warning
- Explanation
- Passing a message to the Evaluate method of the specified node.
- BIP7473
- A HotSwap deploy failed. The assembly <insert_1> could not be loaded in the AppDomain <insert_2> for the .NETCompute node <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- An exception occurred while reloading the AppDomain <insert_2> after a HotSwap deploy of the assembly <insert_1>.
- Response
- Check the error messages that follow to determine why the assembly failed to load and HotSwap deploy a new version of the assembly that fixes the problems found.
- BIP7474
- An error occurred when trying to resolve the .NETCompute node class <insert_1> from the assembly <insert_2>.
- Severity
- 20 : Error
- Explanation
- The .NETCompute node class <insert_1> from assembly <insert_2> in location <insert_3> could not be loaded. See other error messages for more information about this error.
- Response
- Correct the error and redeploy. Make sure that the assembly is present and accessible in the location specified. If the assembly is on a "mapped drive" or on a UNC path, make sure that the drive or path is visible in the session the execution group is running in. Also ensure that the broker's user id has permission to execute the assembly. If you are using a Configurable Service, ensure that its ApplicationBase is set to the correct location of the assembly.
- BIP7475
- An error was found when trying to resolve the .NETCompute node class <insert_1> in the assembly <insert_2>.
- Severity
- 20 : Error
- Explanation
- The .NETCompute node class <insert_1> in assembly <insert_2> could not be loaded. See other error messages for more information about this error.
- Response
- Correct the error in node <insert_1>, around line and column <insert_2>, then redeploy. You might be able to correct the error by specifying the full path to the assembly or by using a configurable service to set the Application Base.
- BIP7476
- An attempt was made to call a .NET method in the AppDomain <insert_2>, but the method name specified was invalid.
- Severity
- 30 : Severe error
- Explanation
- The name <insert_1> is invalid for a .NET method. The method name must be qualified by a class name and must not be empty.
- Response
- Correct the method name and redeploy.
- BIP7477
- The .NET method <insert_1> with <insert_2> parameters could not be found in the assembly <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- The method must be public, static, and must have a signature that matches the broker datatype mappings for .NET types.
- Response
- Correct the method and redeploy.
- BIP7478
- The .NET method <insert_1> has an invalid parameter type that is not in the list of supported CLR parameter types or is of the wrong direction.
- Severity
- 20 : Error
- Explanation
- One or more of the parameters to the specified .NET method <insert_1> are not in the list of supported CLR parameter types or are of the wrong direction. Ensure that all parameters to the .NET method are in the list of supported parameter datatypes and directions.
- Response
- Examine and correct the SQL program.
- BIP7479
- The integer value <insert_1> cannot be converted to a CLR 'int' as it would overflow or underflow a 32 bit value.
- Severity
- 20 : Error
- Explanation
- The CLR 'int' type is 32 bit and so can cannot contain the value <insert_1>.
- Response
- Examine and correct the SQL program.
- BIP7480
- The character value <insert_1> cannot be converted to a CLR 'Char' type as it is too long.
- Severity
- 20 : Error
- Explanation
- The CLR 'Char' type can only hold a single character and so cannnot contain the value <insert_1>.
- Response
- Examine and correct the SQL program.
- BIP7481
- The NULL value was returned as an OUT, INOUT or RETURN value from a .NET method when the parameter in question was marked as 'NOT NULL'.
- Severity
- 20 : Error
- Explanation
- A NULL value cannot be returned to a 'NOT NULL' paramater or RETURN value. The type of the returned parameter was <insert_1>.
- Response
- Examine and correct the SQL program.
- BIP7482
- A NULL value was passed as the <insert_1> parameter to a .NET method when the parameter in question was marked as 'NOT NULL'.
- Severity
- 20 : Error
- Explanation
- A NULL value cannot be passed to a 'NOT NULL' parameter. The type of the parameter was <insert_2>.
- Response
- Examine and correct the SQL program.
- BIP7483
- There is more than one possible match in the assembly <insert_1> for the specified NBComputeNode of type <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- If multiple NBComputeNodes are present in the same assembly, use the "ClassName" property to choose between them by specifying either the class name, the namespace, or both.
- Response
- Set the "ClassName" property to identify the required node in a group of nodes of the same name and redeploy.
- BIP7484
- No NBComputeNode could be found in the assembly <insert_1> for the specified class name <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- A class that is directly or indirectly derived from the class NBComputeNode must exist in the assembly <insert_1> for the .NETCompute node to function.
- Response
- Ensure the assembly name and class name properties are correct and redeploy.
- BIP7485
- The specified NBComputeNode in the assembly <insert_1> does not have a default public constructor.
- Severity
- 30 : Severe error
- Explanation
- The specified class <insert_2> must have a default public constructor.
- Response
- Ensure the class has a default constructor and redeploy.
- BIP7486
- The broker encounted an unexpected error calling into the CLR as it was unable to get the current AppDomain ID. The error code was <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that explain this problem or restart the broker.
- Response
- Ensure that the .NET Framework is installed correctly and that the broker plug-in and support assemblies are installed into the GAC correctly.
- BIP7487
- The broker found an unexpected error returning from a CLR call. The error code returned was <insert_1>. The source AppDomain ID for the call was <insert_2> and the target AppDomain ID was <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that explain this problem or restart the broker.
- Response
- Ensure that the .NET Framework is installed correctly and that the broker plug-in and support assemblies are installed into the GAC correctly.
- BIP7488
- The broker found an unknown C++ exception whilst calling the CLR. The message was <insert_1>, the type of the exception was <insert_2> and the stack trace was <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that explain this problem or restart the broker.
- Response
- Ensure that the code that is called does not throw C++ exceptions back to the broker; instead convert them to CLR exceptions.
- BIP7489
- The broker found a nested exception while processing an unknown C++ exception. The message was <insert_1>, the type of the exception was <insert_2> and the stack trace was <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that explain this problem or restart the broker.
- BIP7490
- The broker found a System.OutOfMemoryException exception while calling the CLR. The message was <insert_1>, the type of the exception was <insert_2> and the stack trace was <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that explain this problem or restart the broker.
- BIP7491
- The broker found a nested exception while processing a System.OutOfMemoryException exception. The message was <insert_1>, the type of the exception was <insert_2> and the stack trace was <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that explain this problem or restart the broker.
- BIP7492
- The broker found an exception while processing a previous exception. The outer exception message was <insert_1>, the type of the outer exception was <insert_2> and the stack trace of the outer exception was <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that explain this problem or restart the broker.
- BIP7493
- The broker found a CLR exception that was not derived from System.Exception while calling the CLR. The type of the exception was <insert_1> and the exception ToString is <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that explain this problem or restart the broker.
- Response
- Ensure that all exceptions that are thrown back to the broker derive from System.Exception.
- BIP7494
- The INTERVAL <insert_1> has the wrong qualifier <insert_2>. Only INTERVALs within the range DAY - SECOND are supported.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that indicate the source of this problem.
- Response
- Correct the error and redeploy.
- BIP7495
- The HotSwap deploy facility has started.
- Severity
- 0 : Information
- Explanation
- The HotSwap deploy facility is now available and is monitoring all .NET AppDomains that have HotSwap enabled.
- Response
- No user action required.
- BIP7496
- Invalid parser for the target, the parser of the target must be of type <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Look for other error messages that indicate the source of this problem.
- Response
- Correct the error and redeploy.
- BIP7497
- A disposed message was propagated.
- Severity
- 20 : Error
- Explanation
- A node tried to propagate a message that has already been disposed. Disposing a message releases all resources associated with it, so it can no longer be used.
- Response
- Modify the node to ensure that no disposed messages are propagated.
- BIP7498
- Exception generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>, <insert_9>.
- Severity
- 20 : Error
- Explanation
- This exception was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7499
- Exception generated by user code. Additional information : <insert_1>, <insert_2>.
- Severity
- 20 : Error
- Explanation
- This exception was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7510
- Informational event generated by user code. No additional information provided.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7511
- Informational event generated by user code. Additional information : <insert_1>.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7512
- Informational event generated by user code. Additional information : <insert_1>, <insert_2>.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7513
- Informational event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7514
- Informational event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7515
- Informational event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7516
- Informational event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7517
- Informational event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7518
- Informational event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7519
- Informational event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>, <insert_9>.
- Severity
- 0 : Information
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7520
- Warning event generated by user code. No additional information provided.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7521
- Warning event generated by user code. Additional information : <insert_1>.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7522
- Warning event generated by user code. Additional information : <insert_1>, <insert_2>.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7523
- Warning event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7524
- Warning event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7525
- Warning event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7526
- Warning event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7527
- Warning event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7528
- Warning event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7529
- Warning event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>, <insert_9>.
- Severity
- 10 : Warning
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7530
- Exception event generated by user code. No additional information provided.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7531
- Exception event generated by user code. Additional information : <insert_1>.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7532
- Exception event generated by user code. Additional information : <insert_1>, <insert_2>.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7533
- Exception event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7534
- Exception event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7535
- Exception event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7536
- Exception event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7537
- Exception event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7538
- Exception event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7539
- Exception event generated by user code. Additional information : <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>, <insert_9>.
- Severity
- 20 : Error
- Explanation
- This event was generated as a CLR exception by user code running in .NET. This is the normal behavior of these statements.
- Response
- Because this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP7540
- The <insert_1> object has been disposed.
- Severity
- 30 : Severe error
- Explanation
- The node has attempted to reference an object that has been disposed.
- Response
- Contact the node provider for further details.
- BIP7541
- An attempt was made to modify an NBElement that is read-only.
- Severity
- 30 : Severe error
- Explanation
- The node has attempted to change an NBElement that is read-only.
- Response
- Contact the node provider for further details.
- BIP7542
- An attempt was made to modify an NBMessage that is read-only.
- Severity
- 30 : Severe error
- Explanation
- The node has attempted to change an NBMessage that is read-only.
- Response
- Contact the node provider for further details.
- BIP7543
- An attempt was made to dispose an NBMessage that is read-only.
- Severity
- 30 : Severe error
- Explanation
- The node has attempted to dispose an NBMessage that is read-only.
- Response
- Contact the node provider for further details.
- BIP7544
- An attempt was made to call the RootElement property of an NBMessage that has been disposed.
- Severity
- 30 : Severe error
- Explanation
- The node has attempted to obtain the root element of an NBMessage that is disposed.
- Response
- Contact the node provider for further details.
- BIP7545
- An attempt was made to copy an NBMessage that has been disposed.
- Severity
- 30 : Severe error
- Explanation
- The node has attempted to copy an NBMessage that is disposed.
- Response
- Contact the node provider for further details.
- BIP7546
- An attempt was made to copy an NBMessage, but the target of the copy is read-only.
- Severity
- 30 : Severe error
- Explanation
- The node has attempted to copy an NBMessage but the target of the copy is read-only.
- Response
- Contact the node provider for further details.
- BIP7547
- An attempt was made to use the GetBuffer method on an NBMessage, after the message has been disposed.
- Severity
- 30 : Severe error
- Explanation
- The node has attempted call GetBuffer on an NBMessage but the message has been disposed.
- Response
- Contact the node provider for further details.
- BIP7548
- An attempt was made to construct an NBMessageAssembly using an NBMessage that has been disposed.
- Severity
- 30 : Severe error
- Explanation
- The node has attempted to pass a disposed NBMessage object to the constructor of an NBMessageAssembly.
- Response
- Contact the node provider for further details.
- BIP7549
- HotSwap deploy Failed. The following AppDomains failed to be reloaded: <insert_1>.
- Severity
- 20 : Error
- Explanation
- As a result of a HotSwap deploy to the ApplicationBase directory <insert_2> an attempt was made to reload the specified AppDomains, but this attempt failed.
- Response
- Look for other error messages that may explain this problem in more detail.
- BIP7550
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7551
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the insert <insert_6>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7552
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the inserts <insert_6>, <insert_7>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7553
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the inserts <insert_6>, <insert_7>, <insert_8>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7554
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the inserts <insert_6>, <insert_7>, <insert_8>, <insert_9>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7555
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the inserts <insert_6>, <insert_7>, <insert_8>, <insert_9>, <insert_10>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7556
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the inserts <insert_6>, <insert_7>, <insert_8>, <insert_9>, <insert_10>, <insert_11>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7557
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the inserts <insert_6>, <insert_7>, <insert_8>, <insert_9>, <insert_10>, <insert_11>, <insert_12>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7558
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the inserts <insert_6>, <insert_7>, <insert_8>, <insert_9>, <insert_10>, <insert_11>, <insert_12>, <insert_13>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7559
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the inserts <insert_6>, <insert_7>, <insert_8>, <insert_9>, <insert_10>, <insert_11>, <insert_12>, <insert_13>, <insert_14>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7560
- A <insert_2> was thrown from the .NET AppDomain <insert_4> to the broker from the source <insert_3> with the message <insert_1> and the first nine inserts are <insert_6>, <insert_7>, <insert_8>, <insert_9>, <insert_10>, <insert_11>, <insert_12>, <insert_13>, <insert_14>.
- Severity
- 20 : Error
- Explanation
- The stack trace for the exception is <insert_5>.
- Response
- Check the error messages that follow to determine where the exception was thrown from.
- BIP7561
- HotSwap deploy partially succeeded. The following AppDomains were reloaded <insert_1>, but these AppDomains failed to reload successfully: <insert_2>.
- Severity
- 10 : Warning
- Explanation
- As a result of a HotSwap deploy to the ApplicationBase directory <insert_3> an attempt was made to reload the specified AppDomains, not all of the reloads were successful.
- Response
- Look for other error messages that may explain this problem in more detail.
- BIP7562
- A HotSwap deploy was triggered, but no AppDomains were reloaded.
- Severity
- 10 : Warning
- Explanation
- As a result of a HotSwap deploy to the ApplicationBase directory <insert_1> an attempt was made to reload the registred AppDomains but no AppDomains were reloaded.
- Response
- Look for other error messages that may explain this problem in more detail.
- BIP7563
- The AppDomain <insert_1> could not be created because a broker assembly is mising from the GAC. The assembly <insert_2> could not be loaded from the GAC.
- Severity
- 30 : Severe error
- Explanation
- A broker assembly missing from the GAC caused the creation of the AppDomain <insert_1> with the base directory <insert_3> to fail.
- Response
- Check that Message Broker is installed correctly and ensure that the listed assemblies are present in the GAC. The 'mqsiAssemblyInstall -l' command can be used see if the assembly is in the GAC. The 'mqsiAssemblyInstall -i' command can be used to put the assembly into the GAC if necessary.
- BIP7564
- The HotSwap deploy facility encountered an error while trying to monitor the Application Base <insert_2> and is stopping monitoring this directory.
- Severity
- 30 : Severe error
- Explanation
- An error <insert_1> was found that required the HotSwap deploy facility to stop monitoring the specified directory. Other AppDomains (if any) will continue to be monitored.
- BIP7565
- A System.IO.FileNotFoundException was thrown whilst trying to load the assembly <insert_1> by code running in AppDomain <insert_3>.
- Severity
- 20 : Error
- Explanation
- The fusion log for the load attempt was <insert_2>.
- Response
- Check the error messages that follow to determine why the file failed to load and make sure the file can be located.
- BIP7566
- The Application Base directory <insert_1> could not be created for the AppDomain <insert_2>. The error code was <insert_3>.
- Severity
- 20 : Error
- Explanation
- The Application base could not be created for AppDomain <insert_2>.
- Response
- Stop and restart the Broker.
- BIP7567
- The .NET AppDomain <insert_1> cannot be deployed as .NET AppDomains can only be deployed to Windows brokers.
- Severity
- 20 : Error
- Explanation
- Only Windows brokers can accept .NET AppDomains.
- Response
- Make sure that .NET AppDomain <insert_1> is deployed to a Windows broker.
- BIP7568
- The .NET AppDomain <insert_1> cannot be deployed as .NET AppDomains can only be deployed to Windows brokers.
- Severity
- 20 : Error
- Explanation
- Only Windows brokers can accept AppDomains.
- Response
- Make sure that .NET AppDomain <insert_1> is deployed to a Windows broker.
- BIP7569
- The AppDomain <insert_1> could not be deleted as it is still in use.
- Severity
- 20 : Error
- Explanation
- AppDomains can only be deleted after all nodes or ESQL routines using them have been deleted or stopped. The AppDomain base for this domain is <insert_2>.
- Response
- Delete use other users of this AppDomain before deleting the AppDomain itself.
- BIP7570
- The AppDomain <insert_1> was deployed, but no AppDomains were reloaded.
- Severity
- 10 : Warning
- Explanation
- As a result of a deploy of the AppDomain <insert_1> an attempt was made to reload the registred AppDomains but no AppDomains were reloaded.
- Response
- Look for other error messages that may explain this problem in more detail.
- BIP7571
- A deploy of the .NET AppDomain <insert_1> succeeded. The following AppDomains were reloaded: <insert_2>.
- Severity
- 0 : Information
- Explanation
- Following a deploy of a .NET AppDomain, the following AppDomains were reloaded <insert_2>.
- Response
- No user action required.
- BIP7572
- The AppDomain <insert_1> was deployed, but the registered domains <insert_2> could not be reloaded.
- Severity
- 20 : Error
- Explanation
- As a result of a deploy of the AppDomain <insert_1> an attempt was made to reload the registered AppDomains <insert_2>, but this attempt failed.
- Response
- Look for other error messages that may explain this problem in more detail.
- BIP7573
- The deployment of the AppDomain <insert_1> only partially succeeded. The following AppDomains were reloaded <insert_2>, but these AppDomains failed to reload successfully: <insert_3>.
- Severity
- 10 : Warning
- Explanation
- As a result of a deploy of the AppDomain <insert_1> an attempt was made to reload the specified registered AppDomains, but not all of the reloads were successful.
- Response
- Look for other error messages that may explain this problem in more detail.
- BIP7574
- An error was encountered when deploying the AppDomain <insert_1>. The Error code was <insert_2>.
- Severity
- 10 : Warning
- Explanation
- As a result of a deploy of the AppDomain <insert_1> an attempt was made to reload the registred AppDomains but an error with code <insert_2> was encountered during reloading.
- Response
- Look for other error messages that may explain this problem in more detail.
- BIP7575
- The configuration file <insert_1> is not a valid configuration file and will be ignored by the broker for the AppDomain <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The configration file <insert_1> is not valid because it does not have a root <configuration> tag. Therefore it will be ignored.
- Response
- If you wish this configuration file to be used by this AppDomain, correct the configuration file and redeploy.
- BIP7576
- The configuration file <insert_1> is not a valid configuration file and will be ignored by the broker for AppDomain <insert_2>.
- Severity
- 20 : Error
- Explanation
- An exception of type <insert_3> was encountered when trying to process the configration file <insert_1>. Therefore it will be ignored.
- Response
- If you wish this configuration file to be used by this AppDomain, correct the configuration file and redeploy. Also look for other error messages that may explain this problem in more detail.
- BIP7577
- An exception of type <insert_3> was caught whilst processing the brokers configuration file <insert_1> for AppDomain <insert_2>. This may cause subsequent problems when assemblies are loaded into the AppDomain.
- Severity
- 10 : Warning
- Explanation
- An exception of type <insert_3> was encountered when trying to process the broker configration file <insert_1> which is based on the user configuration file <insert_4>. The configuration file will be used, but there could be problems when assemblies are loaded.
- Response
- Try to correct the error and redeploy if there are subsequent errors whilst loading assemblies. Also look for other error messages that may explain this problem in more detail.
- BIP7578
- The assembly <insert_1> appears to be linked to a version of the IBM.Broker.Plugin assembly that is older than the current version for this broker. The current broker version is <insert_2>, but the version the assembly links to is <insert_3>.
- Severity
- 20 : Error
- Explanation
- Ideally the linked version should be the same as the current version. However, a previous attempt by the broker to setup a binding redirect from version <insert_3> to version <insert_2> for this assembly may have failed which is why this exception has occurred.
- Response
- Ensure that the configuration file for this AppDomain is valid so that the automatic binding redirect can succeed or alternatively relink the assembly with the curent version of the IBM.Broker.Plugin assembly. Taking a UserTrace of the deploy may also show extra details such as a Fusion log of the error. Also look for other error messages that may explain this problem in more detail.
- BIP7579
- The assembly <insert_1> appears to be linked to a version of the IBM.Broker.Plugin assembly that is newer than the current version for this broker. The current broker version is <insert_2>, but the version the assembly links to is <insert_3>.
- Severity
- 20 : Error
- Explanation
- Ideally the linked version should be the same as the current version. However, a previous attempt by the broker to setup a binding redirect for this assembly may have failed which is why this exception has occurred. Note that if the assembly <insert_1> uses APIs from the newer IBM.Broker.Plugin assembly that are different to those in the current version <insert_2> then this is not supported and will not work and could be the cause of a binding redirect failure.
- Response
- Ensure that the configuration file for this AppDomain is valid so that the binding redirect can succeed (if possible) or alternatively relink the assembly with the curent version of the IBM.Broker.Plugin assembly. Taking a UserTrace of the deploy may also show extra details such as a Fusion log of the error. Also look for other error messages that may explain this problem in more detail.
- BIP7580
- No NBComputeNode could be found in the assembly <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- A class that is directly or indirectly derived from the class NBComputeNode must exist in the assembly <insert_1> for the .NETCompute node to function.
- Response
- Ensure the assembly name is correct and redeploy.
- BIP7581
- The assembly <insert_1> appears to be linked to a version of the IBM.Broker.Plugin assembly that is different to the current version for this broker which is <insert_2>.
- Severity
- 20 : Error
- Explanation
- Ideally the versions should match. However, a previous attempt by the broker to setup a binding redirect for this assembly may have failed which is why this exception has occurred.
- Response
- Ensure that the configuration file for this AppDomain is valid so that the automatic binding redirect can succeed or alternatively relink the assembly <insert_1> with the curent version of the IBM.Broker.Plugin assembly. Taking a UserTrace of the deploy may also show extra details such as a Fusion log of the error. Also look for other error messages that may explain this problem in more detail.
- BIP7582
- The specified NBComputeNode in the assembly <insert_1> does not have a default public constructor.
- Severity
- 30 : Severe error
- Explanation
- The NBComputeNode class in the assembly <insert_1> must have a default public constructor.
- Response
- Ensure the class has a default constructor and redeploy.
- BIP7950
- Failed to run a process on IBM Sterling Connect:Direct server due to error: <insert_1>. Process attempted: <insert_2>.
- Severity
- 20 : Error
- Explanation
- The IBM Sterling Connect:Direct server failed to run the command given above.
- Response
- Review the cause of the error given.
- BIP7951
- Failed to connect to IBM Sterling Connect:Direct server on hostname <insert_1> using port <insert_2> and username <insert_3>. Reason <insert_4>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to connect to the IBM Sterling Connect:Direct server.
- Response
- Check that the IBM Sterling Connect:Direct server is running on the hostname and port given.
- BIP7952
- Failed to find the security identity <insert_1> required to connect to IBM Sterling Connect:Direct server.
- Severity
- 20 : Error
- Explanation
- To use the WebSphere Message Broker CD nodes, you must set the security identity with details of a user that can connect to the IBM Sterling Connect:Direct server.
- Response
- Use the mqsisetdbparms command to define a security identity.
For example: mqsisetdbparms MB7BROKER -n cd&colon.&colon.default -u mqbroker -p xxxxxxx
- BIP7953
- Failed to find netmap to remote IBM Sterling Connect:Direct server <insert_1>
- Severity
- 20 : Error
- Explanation
- An attempt was made by the PNODE to find a connection to the required SNODE.
- Response
- Check that the IBM Sterling Connect:Direct server has a netmap definition allowing the PNODE to connect to the required SNODE.
- BIP7954
- CDOutput node <insert_1> in message flow <insert_2> has successfully sent a command to the IBM Sterling Connect:Direct server <insert_3> to start the transfer of the file to the remote system. Process script used: <insert_4>.
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- BIP7955
- An attempt was made to transfer to an unsupported operating system type <insert_1>.
- Severity
- 20 : Error
- Explanation
- Not all types of remote IBM Sterling Connect:Direct server operating systems are supported.
- Response
- Check the Statement of Environment for message broker for a full list of supported remote operating systems.
- BIP7956
- Failed to deploy the flow because configurable service name: <insert_1> is not valid.
- Severity
- 20 : Error
- Explanation
- The configurable service name specified in the property for the node does not exist.
- Response
- Specify the correct configurable service name in the property for the WebSphere Message Broker CD node.
- BIP7957
- Queue prefix <insert_1> specified in the CDServer configurable service is not valid.
- Severity
- 20 : Error
- Explanation
- A queue prefix can have a maximum length of 16 characters.
- Response
- Review the cause of the error given.
- BIP7958
- Queue prefix <insert_1> specified in the CDServer configurable service is not valid.
- Severity
- 20 : Error
- Explanation
- A queue prefix cannot start or end with the period (.) character.
- Response
- Review the cause of the error given.
- BIP7959
- Queue prefix <insert_1> specified in the CDServer configurable service is not valid.
- Severity
- 20 : Error
- Explanation
- Queue prefix contains a character that is not valid; the valid chararacters are
A-Z
a-z
0-9
period (.)
forward slash (/)
underscore (_)
%.
- Response
- Review the cause of the error given.
- BIP7960
- Port number <insert_1> specified in the CDServer configurable service is not valid.
- Severity
- 20 : Error
- Explanation
- Port number must not contain any character values.
- Response
- Review the cause of the error given.
- BIP7961
- Port number <insert_1> specified in the CDServer configurable service is not valid.
- Severity
- 20 : Error
- Explanation
- The port value must be between 0 and 65535.
- Response
- Review the cause of the error given.
- BIP7962
- File path <insert_1> specified for the property <insert_2> in the CDServer configurable service is not valid.
- Severity
- 20 : Error
- Explanation
- The file path must exist in the local or remote system.
- Response
- Review the cause of the error given.
- BIP7963
- Failed to collect copy statistics for transfers to IBM Sterling Connect&colon.Direct server <insert_1> using configurable service <insert_2>.
- Severity
- 20 : Error
- Explanation
- It has not been possible to collect copy statistics for the given server. See previous error message for the possible cause.
- Response
- Check the previous error message for the cause of the issue.
- BIP7964
- Error received from IBM Sterling Connect&colon.Direct when trying to retrieve copy statistics. Error message: <insert_1>
- Severity
- 20 : Error
- Explanation
- It has not been possible to collect copy statistics because of the IBM Sterling Connect&colon.Direct error given.
- Response
- Try to resolve the given IBM Sterling Connect&colon.Direct error.
- BIP7965
- WebSphere MQ error when trying to store state about IBM Sterling Connect&colon.Direct transfers. Queue name: <insert_1>, return code: <insert_2>.
- Severity
- 20 : Error
- Explanation
- It has not been possible to collect copy statistics because of the WebSphere MQ error given.
- Response
- Try to resolve the given error caused by IBM Sterling Connect&colon.Direct.
- BIP7966
- The properties for CDServer configurable service <insert_1> are not valid, either <insert_2>:<insert_3>, or <insert_4>:<insert_5> are incorrect.
- Severity
- 20 : Error
- Explanation
- One or more of the values for <insert_2> and <insert_4> are incorrect.
These properties must be set, either both to valid values, or both to an empty string.
- Response
- Correct the CDServer configurable service properties.
- BIP7967
- The file <insert_2> is not within the directory <insert_1> specified as the cdPathToInputDir in the configurable service. IBM Sterling Connect:Direct transfer is ignored for the file.
- Severity
- 0 : Information
- Explanation
- The IBM Sterling Connect:Direct destination file path must start with the cdPathToInputDir specified in the configurable service.
- Response
- Ensure that the cdPathToInputDir property value specified in the CDServer configurable service is correct.
- BIP7968
- An error occurred while accessing dataset <insert_1>.
- Severity
- 0 : Information
- Explanation
- The following exception occurred, <insert_2>.
- Response
- Ensure that the dataset exists and is not currently in use.
- BIP7969
- An error occurred when writing dataset <insert_1> to the uss file <insert_2>.
- Severity
- 0 : Information
- Explanation
- The following exception occurred, <insert_3>.
- Response
- Ensure that the broker has permission to write to the file.
- BIP7970
- Dataset <insert_1> is of a type that is not supported by a CDInput node.
- Severity
- 0 : Information
- Explanation
- Only sequential, pds, and pdse dataset types are supported.
- Response
- Check the type of dataset being transferred.
- BIP7971
- An error occurred when processing dataset <insert_1>. Adding a timestamp to a dataset is not a valid option for "Action on successful processing" or "Failed file action".
- Severity
- 0 : Information
- Explanation
- Adding a timestamp to a dataset is not a valid option for "Action on successful processing" or "Failed file action".
- Response
- Change the option on either process to one that is valid.
- BIP7972
- The filter directory (<insert_1>) on CDInput node (<insert_2>) is not an absolute path, either by itself, or relative to the configurable service property brokerPathToInputDir (<insert_3>).
- Severity
- 0 : Information
- Explanation
- The filter expression must, either be an absolute path on the broker machine, or a relative path to the configurable service property brokerPathToInputDir.
- Response
- Either change the filter expression to be an absolute path, or modify brokerPathToInputDir to be an absolute path to one that the filter expression can be relative to.
- BIP7973
- Missing destination file name for CDOutput node <insert_1> in message flow <insert_2>.
- Severity
- 0 : Information
- Explanation
- The CDOutput node has recieved a request to build or transfers a destination file with an empty or null name.
- Response
- Ensure that the node destination file name property is set correctly.
- BIP7974
- Received statistic from IBM Sterling Connect&colon.Direct for file <insert_1>, which does not specify a directory. The file will be ignored.
- Severity
- 10 : Warning
- Explanation
- A transfer has been performed to the IBM Sterling Connect&colon.Direct server without specifying the directory to use and the CD server does not have a default download directory defined.
- Response
- For the CDInput node to be able to process this transfer, the default download directory must be defined on the IBM Sterling Connect&colon.Direct server. Modify the IBM Sterling Connect&colon.Direct userfile.cfg to set the pstmt.download_dir property to the required download directory.
- BIP7975
- The FileOutput node <insert_1> in messageflow <insert_2> is about to execute the FTP/SFTP Precommand/Postcommand <insert_3> with parameters <insert_4> and ignoreErrors set to <insert_5>.
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- BIP7976
- The FTP command <insert_1> completed with the FTP return code <insert_2>.
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- BIP7977
- There are two or more transfer commands in the local environment for a given pre or post command. First command called <insert_1>; Second command called <insert_2>. There must only be one command per pre or post command entry in the local environment.
- Severity
- 20 : Error
- Explanation
- There must only be one command per pre or post command entry in the local environment.
- Response
- Remove the second command and place it in its own pre or post command.