Use the advice given here to help you to resolve problems that can arise during deployment of message flows or message sets.
The broker 'Broker_Name' did not reveal its mode in time;
any reported information might not be up-to-date.
Broker 'Broker_Name' is not at the required software level
to change the mode.
WARNING: Broker 'Broker_Name' is in 'Mode_Name' mode but has 'x' integration servers,
which exceeds the allowed maximum for this mode.
WARNING: Broker 'Broker_Name' is in 'Mode_Name' mode but has 'x' message flows
deployed, which exceeds the allowed maximum for this mode.
WARNING: Broker 'Broker_Name' has a message flow called 'Message_Flow' in integration
server 'Execution_Group', which contains one or more nodes that
are not valid in this mode: Mode_Name
WARNING: The trial period for broker 'Broker_Name' expired on 'Day_Month_Year'.
You attempted to create an integration server 'Execution_Group' on broker 'Broker_Name',
but the broker is running in 'Mode_Name' mode which
limits the number of integration servers that can exist at any one time.
The integration server cannot be created.
You attempted to deploy a broker archive (BAR) file to integration server
'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.
You attempted to deploy a broker archive (BAR) file to integration server
'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.
You attempted to deploy a broker archive (BAR) file to integration server
'Execution_Group' on broker 'Broker_Name',
but the trial period for the broker has expired.
The BAR file cannot be deployed.
You attempted to deploy a broker archive (BAR) file to integration server
'Execution_Group' on broker 'Broker_Name',
but the broker is running in 'Mode_Name' mode which
limits the number of integration servers that can exist at any one time.
The BAR file cannot be deployed.
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.
mqsichangebroker IB9NODE -f all
Additional error messages that might be generated during a deployment are explained in this section.
alter ql(transmit_queue_name) maxmsgl(104857600)
For
more information about this command, see the System Administration
Guide section of the WebSphere MQ Version 7 product documentation online.(Semipersistent_Compute1.Main, 27.89) : Array index evaluated to '0' but must
evaluate to a positive, nonzero integer value.
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').For example, your ESQL module might contain the following statement:
SET OutputRoot.XMLNSC.Top.A[0].B = 42;
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;
BIP7053S: Broker $SYS_mqsi 0 unexpected Java exception java.lang.Error:
-2103399272!java.net.UnknownHostException :
Hostname: Hostname
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.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