The error messages that might be generated during a deployment are listed below with an explanation:
alter ql(transmit_queue_name) maxmsgl(104857600)See the WebSphere MQ System Administration Guide for more information on this command.
alter chl(CM_to_BRK) chltype(sdr) MAXMSGL(104857600) alter chl(BRK_to_CM) chltype(rcvr) MAXMSGL(104857600)
alter chl(BRK_to_CM) chltype(sdr) MAXMSGL(104857600) alter chl(CM_to_BRK) chltype(rcvr) MAXMSGL(104857600)
The size of an exported message set is not a good indication of the size of the message set dictionary that is generated at the time of deployment because the exported message set is stored as XML. This can be very verbose, but the dictionary has a much more compact internal format.
Each broker is identified by a universally unique identifier (UUID), which is allocated when the Message Brokers Toolkit or Configuration Manager Proxy creates a definition for the broker. When the deployment occurs, a UUID check is made to help prevent accidental deployment of changes to brokers that are not under the control of the Configuration Manager. If you have received error BIP2045, the deployment message was addressed to a broker with one UUID, but the message was processed by a broker that was expecting a different UUID.
If this is not possible, use the Configuration Manager Proxy API BrokerProxy.setUUID() method to set the UUID of the Configuration Manager's broker definition to be the UUID that the broker is expecting. This API can also be invoked using the Configuration Manager Proxy API Exerciser sample. Invoking this method allows the Configuration Manager to deploy to the broker, although any resources that were previously deployed to the broker are not monitored by the Configuration Manager (unless they were already being monitored).
To prevent this problem from recurring when you delete or re-create brokers, always remove the broker definition from the domain and deploy the topology successfully before the running broker component is stopped and deleted.
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
Error messages are displayed indicating that the style sheets were not found
You get unexpected transformation results.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au16540_ |