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 thealter ql(transmit_queue_name) maxmsgl(104857600)
WebSphere MQ Version 7 product documentation online.
Message BIP2066
- Scenario: You have initiated a deployment request; for example, you have deployed a BAR file to an integration server. Error message BIP2066 is returned one or more times.
- Explanation: The deployment request was not acknowledged by the integration server 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 integration server; for example, if you have issued mqsistart for the broker, or an error has occurred and the integration server is being recovered. Error message BIP2080 is displayed one or more times.
- Explanation: The internal configuration request was not acknowledged by the integration server 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 IBM Integration 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.IBM Integration Bus 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.
Last updated Friday, 21 July 2017