BIP7000-7999: Runtime components - Publish Subscribe
- BIP7001
- ACL already exists for topic <insert_0> and principal <insert_1>.
- 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 respecify 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_0> and principal <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error caused the update on the ACL for topic <insert_0> and principal <insert_1> 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.
- BIP7003
- Syntax error in topic, reason code <insert_0>.
- Severity
- 20 : Error
- Explanation
- There is a syntax error in the filter expression. Possible reason codes are: (1245) Internal Error. (1246) A topic wildcard character was used incorrectly. (1247) A topic segment separator appears in an incorrect position.
- Response
- Refer to the online help for more information on allowable topics, correct the syntax error and repeat the operation. If an internal error has been reported you should contact your IBM support center.
- BIP7005
- ACL not found for topic <insert_0> and principal <insert_1>.
- Severity
- 20 : Error
- Explanation
- The ACL operation failed because there is no ACL for topic <insert_0> and principal <insert_1>.
- 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_0>.
- Severity
- 20 : Error
- Explanation
- The operation failed because principal <insert_0> 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.
- BIP7007
- Syntax error in filter, reason code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The topic contains a syntax error. Possible reason codes are: (1233) An exception occurred in the matching engine. (1249) An exception occurred while parsing a subscription selector.
- Response
- Refer to the online help for more information on allowable SQL expressions, correct the syntax error and repeat the operation.
- 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_0> <insert_1> <insert_2>.
- 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.
- BIP7011
- Duplicate broker (Queue Manager <insert_0>).
- Severity
- 30 : Severe error
- Explanation
- The attempt to add a neighboring broker was unnecessary because the neighbor with Queue Manager <insert_0> is already known. This could indicate that the Configuration Manager is in an invalid state.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7012
- Duplicate connection to broker (Queue Manager <insert_0>) with id <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- A connection with id <insert_1> to broker (Queue Manager <insert_0>) was not created because it already exists. This could indicate that the Configuration Manager is in an invalid state.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7013
- Unknown broker (Queue Manager <insert_0>).
- Severity
- 30 : Severe error
- Explanation
- The operation failed because the broker (Queue Manager <insert_0>) is unknown.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7014
- Unknown connection with id <insert_1> to broker (Queue Manager <insert_0>).
- Severity
- 30 : Severe error
- Explanation
- The operation failed because the connection with id <insert_1> to broker (Queue Manager <insert_0>) is unknown.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7015
- Permission conflict <insert_0>.
- Severity
- 20 : Error
- Explanation
- The operation failed because of an attempt to set incompatible permissions <insert_0>.
- 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_0>.
- 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_0>.
- Severity
- 10 : Warning
- Explanation
- The user <insert_0> 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_0>) not registered.
- Severity
- 20 : Error
- Explanation
- An attempt was made to deregister a subscription registered by the client with id <insert_0>, 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_0>.
- 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_0>.
- 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_1> was not found for client <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- During processing of a RegisterSubscriber or a RequestUpdate request the subscription which client <insert_0> had for topic <insert_1> 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_0>.
- 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_0>.
- 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_0>.
- 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.
- BIP7028
- A Type Exception occurred in the PubSub Matching Engine when processing a publication against a filter: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The PubSub Matching Engine encountered a mismatch in data types when driving a publication against a filter.
- Response
- Check the types of the subscription filter's fields against those supplied in the corresponding publications and retry the operation.
- BIP7029
- A Parsing Exception occurred when processing a published message to see if it matched a subscriber's filter.
- Severity
- 10 : Warning
- Explanation
- The PubSub Matching Engine requested that a message be parsed in order to determine whether it matched a subscriber's filter. The parsing operation was unsuccessful.
- Response
- See related messages.
- 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.
- BIP7040
- Unknown parameter name <insert_0>.
- Severity
- 20 : Error
- Explanation
- The parameter name <insert_0> is not a valid configuration parameter of the node.
- Response
- If this error has occurred as a result of an action from the Message Brokers 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_0> <insert_1>.
- Severity
- 20 : Error
- Explanation
- The parameter <insert_0> had a value <insert_1> 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 Brokers Toolkit, it is an internal error and you should contact your IBM support center. Otherwise, correct the invalid value, then retry the operation.
- BIP7047
- Neighbor (Queue Manager <insert_0>) failed to register the subscription request with reason code <insert_1>.
- 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_0>.
- 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_0>.
- Severity
- 30 : Severe error
- Explanation
- The Java class <insert_0> 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_0> in class <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The Java method <insert_0> in class <insert_1> 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_0>.
- Severity
- 30 : Severe error
- Explanation
- The Java object <insert_0> could not be created.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7053
- Unexpected Java exception <insert_0>.
- 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_0>.
- Severity
- 30 : Severe error
- Explanation
- An unexpected null pointer exception was thrown from Java code on an object of class <insert_0>.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7055
- Invalid attribute value <insert_0> <insert_1>.
- Severity
- 20 : Error
- Explanation
- The attribute <insert_0> had a value <insert_1> 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 Brokers 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_0>.
- Severity
- 20 : Error
- Explanation
- The attribute <insert_0> 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 Brokers 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_0>.
- Severity
- 20 : Error
- Explanation
- The queue manager <insert_0> 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_0>.
- Severity
- 30 : Severe error
- Explanation
- While attempting to build a message a failure occurred on creating element <insert_0>.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7059
- Failed to navigate to message element <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- While attempting to explore the contents of a message an error occurred because the element <insert_0> was missing or unreachable.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7060
- Unexpected filter in RFH message.
- Severity
- 20 : Error
- Explanation
- A filter was found in an RFH message, for which filters are not supported.
- Response
- Review the message and remove the filter, then retry the operation.
- BIP7061
- Invalid client identifier <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The client identifier <insert_0> 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_0>.
- 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_0>.
- 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_0> <insert_1>.
- 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_0> 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_1>) on incorrect queue <insert_0>.
- Severity
- 20 : Error
- Explanation
- An application put a message of type <insert_1> on queue <insert_0>. 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_0>) is already an WebSphere publish/subscribe neighbor.
- Severity
- 20 : Error
- Explanation
- An attempt has been made to join this broker with a WebSphere Message Brokers broker on queue manager <insert_0>. This request was unsuccessful because the broker is already joined as an WebSphere publish/subscribe neighbor.
- Response
- If queue manager <insert_0> is a WebSphere Message Brokers 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_1> condition detected while recovering client <insert_0> 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_0> for subscription registered to topic <insert_1>.
- 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_0> for publisher registered to topic <insert_1>.
- 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_1>: The Publish/Subscribe service has received a message of type <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Publish/Subscribe service has started processing a control message.
- Response
- No user action required.
- BIP7080
- Node <insert_2>: The Publication Node with Subscription Point <insert_1> has received a message of type <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Publication Node with Subscription Point <insert_1> has started processing a message.
- Response
- No user action required.
- BIP7081
- The Publication Node has matched <insert_0> subscriptions to topic <insert_1> for subscription point <insert_2>.
- Severity
- 0 : Information
- Explanation
- The Publication Node has matched subscriptions for the current publication and topic.
- Response
- No user action required.
- BIP7082
- Node <insert_2>: Publishing to destination <insert_0> for user <insert_1>.
- Severity
- 0 : Information
- Explanation
- A publication destination is being added to the list of destinations to <insert_0> for user <insert_1>.
- Response
- No user action required.
- BIP7083
- Node <insert_2>: The Publication Node with Subscription Point <insert_1> has received an error code <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Publication Node with Subscription Point <insert_1> has received an error with code <insert_0>. A response message has been sent to the originator's reply queue.
- Response
- No user action required.
- BIP7084
- Node <insert_1>: The Publish/Subscribe service has received an error code <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Publish/Subscribe service has received an error with code <insert_0>. A response message has been sent to the originator's reply queue.
- Response
- No user action required.
- BIP7085
- Node <insert_1>: The Publication Node has propagated a message to its output terminal for subscription point <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Publication Node has propagated the current message to its output terminal.
- Response
- No user action required.
- BIP7086
- Node <insert_2>: The Publication Node with Subscription Point <insert_1> has received an error code <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Publication Node with Subscription Point <insert_1> has received an error with code <insert_0>. No response message has been sent as one was not requested.
- Response
- No user action required.
- BIP7087
- Node <insert_1>: The Publish/Subscribe service has received an error code <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Publish/Subscribe service has received an error with code <insert_0>. No response message has been sent because one was not requested.
- Response
- No user action required.
- BIP7088
- publish/subscribe configuration request <insert_0> 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 Brokers 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.
- BIP7090
- Configuration Manager's subscription cannot be processed at this time.
- Severity
- 0 : Information
- Explanation
- The broker has been created as a replacement for an existing WebSphere Publish/Subscribe broker. As part of its normal processing for newly created brokers the Configuration Manager has subscribed to event publications at the new broker. It is not possible for the migrating broker to process this request at this time.
- Response
- None. This is an expected occurrence when deploying to a broker which is being migrated. The Configuration Manager will reissue its subscription the next time you deploy to this broker. This should be done after migration has completed.
- BIP7091
- Caught exception <insert_2> while deregistering subscriptions for client id <insert_0>: error code <insert_1>.
- 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 Brokers 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 sending deferred message of type <insert_0>. Failure count is <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The publish/subscribe service detected an error whilst sending a deferred message of type <insert_0>, where 1 indicates an administrative event publication, 2 indicates a command message destined for another broker, and 3 indicates an internal command message destined for another execution group. The number of times this message has been tried is <insert_1>. The attempt to send the message will be retried later, unless the message is an administrative event publication, in which case it will only be retried three times before being discarded. Following messages will indicate the cause of this exception.
- Response
- Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
- BIP7095
- Requested response cannot be sent for non-RFH message.
- Severity
- 20 : Error
- Explanation
- A message requesting a response was received by the Publish/Subscribe Service. In order to send a response, the Publish/Subscribe Service requires that the message contains an RFH or RFH2 format header. The received message contained 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 RFH or RFH2 header, or ensure that the report options in the message descriptor are set so that a response is not requested.
- BIP7096
- Node <insert_0>: 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 neccasary to stop and restart the Broker and increase the Java Virtual Machine Heap size
- BIP7098
- Unable to find user <insert_0> for subscription registered to topic <insert_1>.
- 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.
- 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_0> has inconsistent Queue Manager value <insert_1>.
- Severity
- 10 : Warning
- Explanation
- A broker (identified by its UUID <insert_0> and Queue Manager <insert_1>) 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_0> (Queue Manager <insert_1>) is currently unknown.
- Severity
- 10 : Warning
- Explanation
- A broker (identified by its UUID <insert_0> and Queue Manager <insert_1>) 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_0> not found.
- Severity
- 30 : Severe error
- Explanation
- The message flow <insert_0> 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_0>.
- Severity
- 30 : Severe error
- Explanation
- An attempt was made to locate the Interbroker node within message flow <insert_0>. 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_0> (Queue Manager <insert_1>) is currently unknown.
- Severity
- 10 : Warning
- Explanation
- A broker (identified by its UUID <insert_0> and Queue Manager <insert_1>) 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_1> code caught an unknown exception on thread <insert_0>.
- 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_0>. Futher 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_1> code caught a fatal exception on thread <insert_0>.
- 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_0>. Futher 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_1> code caught a recoverable exception on thread <insert_0>.
- 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_0>. Futher 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_0> was caught while trying to convert message.
- Severity
- 10 : Warning
- Explanation
- An exception caught whilst trying to convert a message to or from a WebSphere MQ message. The exception was issued on thread <insert_0>. Futher 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_0> was caught while trying to convert message.
- Severity
- 30 : Severe error
- Explanation
- An exception caught whilst trying to convert a message to or from a WebSphere MQ message. The exception was issued on thread <insert_0>. Futher 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_0>, queue manager <insert_1>) has an incorrect value <insert_2> for this broker's UUID, which is <insert_3>.
- 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_0>).
- Severity
- 0 : Information
- Explanation
- A connection has been established with neighboring broker (Queue Manager <insert_0>) 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_0>).
- Severity
- 0 : Information
- Explanation
- An active connection has been ended with the neighboring broker (Queue Manager <insert_0>). 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_0>.
- 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_0>.
- 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 unpredicatable 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 caught whilst trying to publish a subscription event message. The exception was issued on thread <insert_0>. Futher 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 caught whilst trying to publish a subscription event message. The exception was issued on thread <insert_0>. Futher 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.
- BIP7150
- User id <insert_2> not authorized to put to queue <insert_1> on queue manager <insert_0> using accounting token <insert_3>.
- 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.
- 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_0>.
- Severity
- 30 : Severe error
- Explanation
- A tag (<insert_0>) 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_0>.
- Severity
- 30 : Severe error
- Explanation
- A <insert_0> 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_0> message flow <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- A problem occurred while trying to create a <insert_0> type of message flow. The exception detail was <insert_1>
- Response
- This is an internal error and you should contact your IBM support center.
- BIP7205
- Attribute <insert_0> of tag <insert_1> missing from the configuration message.
- Severity
- 30 : Severe error
- Explanation
- The configuration message is invalid. The attribute <insert_0> is required for the <insert_1> 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_0>: PutApplName <insert_1>; additional diagnostic data <insert_2>.
- 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_0> 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_1> detected for WebSphere Publish/Subscribe neighbor <insert_0> whilst processing control message of type <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.
- BIP7252
- Failed to map <insert_0> parameter/value <insert_1>.
- 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_0> is already a neighbor.
- Severity
- 30 : Severe error
- Explanation
- An internal error has occurred while adding WebSphere Publish/Subscribe broker <insert_0> as a neighbor. Broker <insert_0> is already a neighbor.
- Response
- Contact your IBM support center.
- BIP7256
- WebSphere Publish/Subscribe broker <insert_0> 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_0> state <insert_1> 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_0>.
- 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_0> has failed to import a migrated subscription: diagnostic information <insert_1>, <insert_2>.
- 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_1> and <insert_2>
- Response
- Contact your IBM support center.
- BIP7260
- Message broker <insert_0> already has a parent WebSphere Publish/Subscribe broker <insert_1>.
- 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_0>, <insert_1>.
- 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_1> has been detected: diagnostic information <insert_0>.
- 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_0>.
- 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_0>. 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_0> from this broker, the clrmqbrk command should also be used at broker <insert_0> to remove knowledge of this broker.
- BIP7264
- Message broker could not send completion code <insert_0> 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_0>, <insert_1>.
- 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_2>: diagnostic information <insert_0>, <insert_1>.
- 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 Brokers traces will help with problem resolution.
- BIP7267
- Invalid WebSphere Publish/Subscribe control message detected on queue <insert_2>: diagnostic information <insert_0>, <insert_1>.
- 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_0> is not known by this message broker.
- Severity
- 10 : Warning
- Explanation
- The mqsiclearmqpubsub command has been used to remove WebSphere Publish/Subscribe broker <insert_0>. 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_0> 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_0>. 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_0> failed because a parent <insert_1> 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_0> to WebSphere Publish/Subscribe broker <insert_1>.
- 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_0>.
- 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_0>.
- 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_0>. 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 Brokers Introduction and Planning guide.
- BIP7274
- WebSphere Publish/Subscribe migration has failed for message broker <insert_0> with reason code <insert_1>.
- 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_1>.
- Response
- Investigate the reason for the failure. Look for previous messages issued by message broker <insert_0> 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_1> received from WebSphere Publish/Subscribe broker <insert_0>.
- 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 Brokers broker has failed to join with WebSphere publish/subscribe broker <insert_0> for reason <insert_1>.
- Severity
- 20 : Error
- Explanation
- The mqsijoinmqpubsub command has been issued to join with WebSphere publish/subscribe broker <insert_0>. The WebSphere Message Brokers 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 Brokers broker has failed to subscribe to WebSphere publish/subscribe broker <insert_0>. Reason codes <insert_1> and <insert_2>.
- Severity
- 20 : Error
- Explanation
- The strmqbrk command has been issued at WebSphere publish/subscribe broker <insert_0> nominating this WebSphere Message Brokers broker as its parent. While handling the resultant join request the WebSphere Message Brokers broker sent an internal subscription to the admininstration stream of broker <insert_0>. 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_0>, or a problem with the definition of route between this broker and broker <insert_0>. Once 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_0> and the mqsiclearmqpubsub command at this broker.
- BIP7278
- WebSphere Message Brokers broker has failed to propagate a subscription to WebSphere publish/subscribe broker <insert_0>. Reason codes <insert_1> and <insert_2>.
- 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_0> but the request has not been successful. The WebSphere Message Brokers broker will immediately attempt to refresh the state of all global subscriptions at broker <insert_0>. Until the subscription state has been successfully refreshed, messages published through broker <insert_0> 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_0>, or a problem with the definition of route between this broker and broker <insert_0>. When the problem has been rectified, this error message will no longer be issued.
- BIP7279
- WebSphere Message Brokers broker failed to inform parent WebSphere publish/subscribe broker <insert_0> of a new broker for reason <insert_1>.
- 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 Brokers broker has failed to notify its parent on queue manager <insert_0> 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_2> to WebSphere Publish/Subscribe broker <insert_0> for reason <insert_1>.
- 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_0> from WebSphere publish/subscribe broker <insert_2> contains an invalid topic <insert_1>.
- 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 Brokers 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 Brokers broker.
- BIP7282
- mqsijoinmqpubsub command from broker <insert_0> rejected because it named a WebSphere Message Brokers broker <insert_1> 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 Brokers broker. The two brokers have not been joined together.
- Response
- Use the Message Brokers Toolkit to join the two WebSphere Message Brokers 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_0> cannot be accessed.
- Severity
- 10 : Warning
- Explanation
- The broker has WebSphere publish/subscribe neighbors. These neighbors communicate with this broker using queue <insert_0>. The queue cannot be accessed which will affect inter-operability with all WebSphere publish/subscribe neighbors.
- Response
- Check whether queue <insert_0> 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 Brokers 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_0> will not be propagated to WebSphere publish/subscribe neighbors.
- Severity
- 10 : Warning
- Explanation
- A subscription to topic <insert_0> 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_0> 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 Brokers 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_0> 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 vaild multicast topics file name.
- BIP7355
- Unable to locate file: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The broker was unable to find the multicast topics file: <insert_0>.
- Response
- Check that the multicast topic file exists and try again.
- BIP7356
- Unable to parse entry for topic <insert_0>, <insert_1> is not a valid boolean. Entries must of the form <topic>=<true|false>.
- Severity
- 30 : Severe error
- Explanation
- An error occured 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_0>.
- Severity
- 30 : Severe error
- Explanation
- Refer to previous event messages for likely causes of this failure
- Response
- An SSL Exception occured. Please correct the problem then restart the broker.
- BIP7366
- An error occurred starting Real-time node with name <insert_0> listening on port <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred starting Real-time node with name <insert_0> listening on port <insert_1>. 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 Brokers 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_0> for multicast.
- Severity
- 0 : Information
- Explanation
- The broker will use interface <insert_0> for multicast transmission.
- Response
- This message is for information only, no response is required.
- BIP7372
- An attempt to <insert_0> 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_0> one or more multicast topics failed because the broker is not enabled for multicast. The <insert_0> 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_0>
- Severity
- 10 : Warning
- Explanation
- RMM Warning: <insert_0>
- Response
- This is a warning message. No user action required.
- BIP7374
- RMM Error: <insert_0>
- Severity
- 30 : Severe error
- Explanation
- RMM Error: <insert_0>
- Response
- This is an internal error. Contact your IBM support center.
- BIP7375
- RMM Error: Missing configuration entry: <insert_0>
- Severity
- 30 : Severe error
- Explanation
- The configuration entry <insert_0> is missing.
- Response
- Change the multicast configuration and try again.
- BIP7376
- RMM Error: Bad argument. Parameter <insert_0>, value: <insert_1>
- 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_0>
- 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_0> 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_0> interrupted
- Severity
- 30 : Severe error
- Explanation
- The multicast service <insert_0> was interrupted.
- Response
- This is an internal error. Contact your IBM support center.
- BIP7380
- RMM Error: Failed to set Time-To-Live to: <insert_0>
- 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_0>
- 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_0>
- 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_0> 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_0> 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 addess: <insert_0>
- 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_0> to <insert_1>
- 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_0> from <insert_1>
- 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_0> 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_0>
- 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_0>
- Severity
- 30 : Severe error
- Explanation
- RMM Error: Clock moved <insert_0>
- Response
- No user action required.
- BIP7391
- RMM Error: Failed to set socket parameter <insert_0> to <insert_1>
- 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_0> has been successfully registered as a publish/subscribe clone of broker <insert_1>.
- Response
- No user action required.
- BIP7402
- Failed to connect to cloned broker's Queue Manager <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Queue Manager <insert_0> 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 widh to register as a clone.
- BIP7403
- Incorrect Broker name received during publish/subscribe cloning registration.
- Severity
- 30 : Severe error
- Explanation
- The Broker name <insert_0> specified by the publish/subscribe clone broker request did not match the broker associated with Queue Manager <insert_1>.
- Response
- Check that the queue manager specified is the correct one for the broker you widh to register as a clone.
- BIP7404
- Neighbor (<insert_0>) is already known as a publish/subscribe neighbor.
- Severity
- 30 : Severe error
- Explanation
- The Neighbor <insert_0> is already known as a publish/subscribe neighbor and can not be created as a clone.
- Response
- Either remove broker <insert_0> as a Neighbor and retry the command, or choose another broker to be a clone.
- BIP7405
- Blank Broker Name <insert_0> or blank Queue Manager Name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Blank Broker Name <insert_0> or blank Queue Manager Name <insert_1>.
- Response
- Check that you have specified values for the Broker Name, or Queue Manager name. Also check that the command contains &bsl;" for the value data. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n clonedPubSubBrokerList -v &bsl;"Broker1,QM1&bsl;"
- BIP7406
- The following database table is missing: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- Take corrective action and re-try the operation.
- BIP7407
- Publish/Subscribe subscriptions recovery started. Found <insert_0> 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_0>, 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_0> 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.