WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems that occur during deployment of message flows
Use the advice given here to help you to resolve problems that can arise during deployment of message flows or message sets.
- You receive a warning message about your broker mode
- The message flow deploys on the test system, but not elsewhere
- Error messages about your broker mode are issued when you create an execution group
- Error messages about your broker mode are issued when you deploy
- Error messages about your function level are issued when you deploy
- Error messages are issued when you deploy to z/OS
- Expected serialization of input is not occurring for a shared queue that serves multiple instances of a message flow on z/OS
- You create a configurable service, then deploy a message flow and inbound adapter, but the deployment fails
- You have created a WebSphere Adapters message flow that uses secondary adapters, and a naming clash has occurred in the secondary adapters or message sets
- You get an authority check failure when you deploy to z/OS
- Deployment fails when you have circular project dependencies
- Error messages are issued when you deploy
You receive a warning message about your broker mode
Message BIP1806
- Scenario: Warning message BIP1806 is displayed.
The broker 'Broker_Name' did not reveal its mode in time; any reported information might not be up-to-date.
- Explanation: Your broker timed out before the command completed. You can set the timeout value on the -w parameter of the mqsimode command, or accept the default value of 60 seconds; see mqsimode command.
- Solution: Check that the broker is started: if it is not started, start it by using the mqsistart command. If it is started, increase the timeout value and run the command again.
Message BIP1808
- Scenario: Warning message BIP1808 is displayed.
Broker 'Broker_Name' is not at the required software level to change the mode.
- Explanation: Your broker is running in a previous version of the product. You must migrate brokers that you created in a version earlier than V6.1.0.2 before you can change the operation mode.
- Solution: Upgrade your broker to at least V6.1.0.2, and run the command again.
Message BIP1821
- Scenario: Warning message BIP1821 is displayed.
WARNING: Broker 'Broker_Name' is in 'Mode_Name' mode but has 'x' execution groups, which exceeds the allowed maximum for this mode.
- Explanation: Your broker is running in a mode that restricts the number of execution groups that you can use; see Restrictions that apply in each operation mode.
- Solution: Contact your IBM® representative to upgrade your license, or remove the required number of execution groups; see Deleting an execution group by using the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer.
Message BIP1822
- Scenario: Warning message BIP1822 is displayed.
WARNING: Broker 'Broker_Name' is in 'Mode_Name' mode but has 'x' message flows deployed, which exceeds the allowed maximum for this mode.
- Explanation: Your broker is running in a mode that restricts the number of message flows that you can use; see Restrictions that apply in each operation mode.
- Solution: Contact your IBM representative to upgrade your license, or delete the required number of message flows; see Deleting a message flow or subflow.
Message BIP1823
- Scenario: Warning message BIP1823 is displayed.
WARNING: Broker 'Broker_Name' has a message flow called 'Message_Flow' in execution group 'Execution_Group', which contains one or more nodes that are not valid in this mode: Mode_Name
- Explanation: Your broker is running in a mode that restricts the types of node that you can use in a message flow; see Restrictions that apply in each operation mode.
- Solution: Contact your IBM representative to upgrade your license, rework your message flow to use nodes that are valid in the current mode, or remove the message flows that contain unsupported nodes; see Deleting a message flow or subflow.
Message BIP1824
- Scenario: Warning message BIP1824 is displayed.
WARNING: The trial period for broker 'Broker_Name' expired on 'Day_Month_Year'.
- Explanation: Your broker is running in the Trial Edition mode and your trial period of 90 days has expired; see Restrictions that apply in each operation mode.
- Solution: Contact your IBM representative to upgrade your license.
The message flow deploys on the test system, but not elsewhere
Error messages about your broker mode are issued when you create an execution group
Message BIP1825
- Scenario: Error message BIP1825 is displayed.
You attempted to create an execution group 'Execution_Group' on broker 'Broker_Name', but the broker is running in 'Mode_Name' mode which limits the number of execution groups that can exist at any one time. The execution group cannot be created.
- Explanation: The execution group cannot be created because the maximum number of execution groups for the mode of the target broker has been reached, and creating the execution group causes this limit to be exceeded; see Restrictions that apply in each operation mode. The execution group was not created.
- Solution: Reuse an existing execution group, or delete an existing execution group and try the command again; see Deleting an execution group by using the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer. Alternatively, contact your IBM representative to upgrade your license.
Error messages about your broker mode are issued when you deploy
Message BIP1826
- Scenario: Error message BIP1826 is displayed.
You attempted to deploy a broker archive (BAR) file to execution group 'Execution_Group' on broker 'Broker_Name', but the broker is running in 'Mode_Name' mode which limits the number of message flows that can exist at any one time. The BAR file cannot be deployed.
- Explanation: The BAR file cannot be deployed because it causes the broker to run more message flows than are valid for the current mode of operation of the target broker; see Restrictions that apply in each operation mode. The BAR file was not deployed.
- Solution: Delete message flows from the broker and try the command again; see Deleting a message flow or subflow. Alternatively, contact your IBM representative to upgrade your license.
Message BIP1827
- Scenario: Error message BIP1827 is displayed.
You attempted to deploy a broker archive (BAR) file to execution group 'Execution_Group' on broker 'Broker_Name', but the broker is running in 'Mode_Name' mode which has a restriction on the types of node that can be deployed. The BAR file cannot be deployed. The set of node types found in the BAR file that are not valid are: Node_Type.
- Explanation: The BAR file cannot be deployed because it contains nodes that are not valid for the current mode of the target broker; see Restrictions that apply in each operation mode. The BAR file was not deployed.
- Solution: Rework your message flow to use nodes that are valid in the current mode, or remove the message flows that contain unsupported nodes; see Deleting a message flow or subflow. Alternatively, contact your IBM representative to upgrade your license.
Message BIP1828
- Scenario: Error message BIP1828 is displayed.
You attempted to deploy a broker archive (BAR) file to execution group 'Execution_Group' on broker 'Broker_Name', but the trial period for the broker has expired. The BAR file cannot be deployed.
- Explanation: The target broker is running in a trial mode that has expired; see Restrictions that apply in each operation mode. The BAR file was not deployed.
- Solution: Contact your IBM representative to upgrade your license. If you have already purchased a valid license for the target broker, change the broker to the correct mode by using the mqsimode command; see mqsimode command.
Message BIP1829
- Scenario: Error message BIP1829 is displayed.
You attempted to deploy a broker archive (BAR) file to execution group 'Execution_Group' on broker 'Broker_Name', but the broker is running in 'Mode_Name' mode which limits the number of execution groups that can exist at any one time. The BAR file cannot be deployed.
- Explanation: The BAR file cannot be deployed because the maximum number of execution groups for the mode of the target broker has been reached; see Restrictions that apply in each operation mode. The BAR file was not deployed.
- Solution: Delete an existing execution group and try the command again; see Deleting an execution group by using the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer. Alternatively, contact your IBM representative to upgrade your license.
Error messages about your function level are issued when you deploy
Message BIP2276
- Scenario: Error message BIP2276 is displayed.
The flow 'Message_flow', which includes a message flow of node type 'Node_type', cannot be deployed because the current fix pack function level of '<version>.<release>.<modification>.<fix>' does not support this node. Use mqsichangebroker -f all' to enable this functionality.
- Explanation: The broker received an instruction to create
a message flow node of type Node_type in message
flow Message_flow. The broker cannot create nodes
of this type because the new functions have not been enabled for this
broker. Use the following command to enable this function, and all
other functions:
mqsichangebroker MB8BROKER -f all
- Solution: Either change the flow to avoid using the unavailable node, or enable the new functions by using the mqsichangebroker command; see mqsichangebroker command.
Error messages are issued when you deploy to z/OS
Expected serialization of input is not occurring for a shared queue that serves multiple instances of a message flow on z/OS
You create a configurable service, then deploy a message flow and inbound adapter, but the deployment fails
- Scenario: You create a configurable service, then deploy a message flow and inbound adapter, but the deployment fails.
- Explanation: When you create a configurable service for an adapter that has not yet been deployed, the connection properties are not fully validated until you deploy the adapter and the message flow that uses that adapter. Therefore, the properties that you set on the configurable service might be invalid.
- Solution: Inspect the error message that is returned from the deployment and determine whether the deployment failed because of invalid connection properties on the configurable service. If so, use the mqsichangeproperties command to correct the properties, or use the mqsideleteconfigurableservice command to use the properties that are set on the adapter. Restart the broker and redeploy the message flow.
You have created a WebSphere Adapters message flow that uses secondary adapters, and a naming clash has occurred in the secondary adapters or message sets
You get an authority check failure when you deploy to z/OS
Deployment fails when you have circular project dependencies
Error messages are issued when you deploy
Additional error messages that might be generated during a deployment are explained in this section.
Message BIP1106 with WebSphere MQ reason code 2030
- Scenario: Error message BIP1106 is issued with reason code 2030 when you are deploying a large message set.
- Explanation: The size of the message exceeds the maximum message length of the transmission queue to the broker queue manager.
- Solution: Increase the maximum message length for the transmission
queue using the WebSphere MQ alter
qlocal command, where the maximum message length (maxmsgl)
is in bytes:
For more information about this command, see the System Administration Guide section of the WebSphere MQ Version 7 Information Center online.alter ql(transmit_queue_name) maxmsgl(104857600)
Message BIP2066
- Scenario: You have initiated a deployment request; for example, you have deployed a BAR file to an execution group. Error message BIP2066 is returned one or more times.
- Explanation: The deployment request was not acknowledged by the execution group before the sum of the values for the broker timeout parameters ConfigurationChangeTimeout and InternalConfigurationTimeout expired.
- Solution: Increase these timeout values by specifying the -g and -k parameters of the mqsicreatebroker or mqsichangebroker command. See Setting configuration timeout values for information about factors that affect timeout values, and how to set appropriate values.
Message BIP2080
- Scenario: The broker has started an execution group; for example, if you have issued mqsistart for the broker, or an error has occurred and the execution group is being recovered. Error message BIP2080 is displayed one or more times.
- Explanation: The internal configuration request was not acknowledged by the execution group before the value of the InternalConfigurationTimeout (default 60 seconds) expired.
- Solution: Change the configuration timeout by specifying the -k parameter of the mqsicreatebroker or mqsichangebroker command. See Setting configuration timeout values for information about factors that affect timeout values, and how to set appropriate values.
Message BIP2241
- Scenario: Error message BIP2241 is displayed.
- Explanation: You are attempting to deploy a message flow containing a node that is not available on the target broker.
- Solution: Ensure that the version of the WebSphere Message Broker Toolkit in which the message flow has been developed matches the version of the broker to which the message flow is being deployed. If the message flow is using a user-defined node, or a node supplied in a SupportPac, ensure that the runtime node implementation has been correctly installed on the computer on which the broker is running. If your message flow includes a user-defined node, see Installing user-defined extension runtime files on a broker. If your message flow includes a node provided in a SupportPac, see the installation information, if supplied, for the SupportPac.
Message BIP2242
- Scenario: Error message BIP2242 is displayed.
- Explanation: The deployment request (configuration change) was not accepted before the timeout value set by the broker parameter ConfigurationChangeTimeout expired. This configuration timeout value must be long enough for the message flow to complete processing its current message, then accept the deploy request; the default is 300 seconds.
- Solution: Set the configuration timeout values by specifying the -g and -k parameters of the mqsicreatebroker or mqsichangebroker command.
Message BIP3226
- Scenario: Error message BIP3226 is displayed;
for example:
The first insert in BIP3226 (in this example, Semipersistent_Compute1.Main) identifies the node and routine in which the statement occurs. The second insert (in this example, 27.89) identifies the approximate line and column of the index value shown in the third insert (in this example, '0').(Semipersistent_Compute1.Main, 27.89) : Array index evaluated to '0' but must evaluate to a positive, nonzero integer value.
- Explanation: The validity of using a field reference index
of zero was corrected in WebSphere Message
Broker Version 7.0.
If you have statements in your ESQL modules that include an index
of zero, error BIP3226E is generated.
For example, your ESQL module might contain the following statement:
SET OutputRoot.XMLNSC.Top.A[0].B = 42;
- Solution:
You must correct all ESQL statements that use an index of zero to use an index of 1. Statements might use a variable as well as a literal value for the index; check for both possible situations. For example, your changed code might read:
SET OutputRoot.XMLNSC.Top.A[1].B = 42;
Message BIP7053S
- Scenario: When you deploy to a broker, error message BIP7053S is displayed.
- Explanation: This error occurs in a multi TCP/IP stack
environment, and indicates that the UNIX System
Services (USS) TCP/IP environment has not been set up correctly.WebSphere Message Broker uses USS functions to obtain the host name for a particular system. The following error message is displayed if the default host name is not set up correctly in the USS environment:
The host name that is reported in the error message is the one that has been returned to the broker as a result of the gethostname call.BIP7053S: Broker $SYS_mqsi 0 unexpected Java exception java.lang.Error: -2103399272!java.net.UnknownHostException : Hostname: Hostname
- Solution: Ensure that the TCP/IP environment is configured correctly in USS.
Tagged/Delimited String (TDS) Validator error
- Scenario: You try to deploy a message set with a TDS wire format that has an error.
- Explanation: The following extract from an error log illustrates
what you might see for a TDS Validator error. In this case, the cause
of the problem is that the element Town does not
have a tag defined.
TDS Extractor Trace File ======================== Beginning Extract.. Extracting Identification Info Extracting Project Info Extracting Messages Extracting Elements Extracting Compound Types Extracting Type Members Extracting Type Members Extracting Type Members Extracting Type Members Extracting Type Members Beginning Indexing.. Creating Member IDs to Tags Index Table. Beginning Validation.. Validating Project Validating Types ERROR: TDSValidator::ValidateTypeMemberSimpleElement: Simple elements in a type with Data Element Separation attribute = Tagged Delimited must have the following attribute set: Element Level - Tag (Element ID: Town) (Type ID: AddressType) Return Code: -80 Validating Messages Trace Info =========== EXCEPTION: TDSValidator::Validate: TDS Validation failed. 1 errors 0 warnings Return Code: -1
- Solution: Use the information in the error log to correct the problem.