Express (Distributed operating systems), v8.0 > Reference > Messages
CWSIL
CWSIL0001E: A subscription could not be registered on event broker {0} for profile {1} due to reason code {2}.
Explanation The reason code was returned by an event broker. Action Refer to the WebSphere MQ Event Broker Programming Guide for an explanation of the reason code. For further information on resolving this error, consult the IBM WAS Support Web site available at: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
CWSIL0002E: A message received from the event broker {0} was neither a publication nor a response to a command. The message received was of type {1} and corresponds to profile {2}
Explanation Only responses to register and deregister subscriptions and publication messages are expected from the event broker. Action More info at:
CWSIL0003E: A subscription could not be deregistered on event broker {0} for profile {1} due to reason code {2}.
Explanation The reason code was returned by an event broker. Action Refer to the WebSphere MQ Event Broker Programming Guide for explanation of the reason code. For further information on resolving this error, consult the IBM WAS Support Web site available at: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
CWSIL0004E: A message of the unsupported type {0} was received from topic space {1} on the topic {2} but could not be republished.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIL0005E: A message of type {1} from event broker {0} could not be published. The message corresponds to profile {2}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIL0006E: A message received from event broker {0} for publishing did not contain a topic. The message received was of type {1} and corresponds to profile {2}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIL0007E: Topic mangling is not supported in this version. Inconsistent topics were specified for inbound and outbound profiles in the mapping {0}.
Explanation Inbound and outbound profiles should specify the same topics. Action Modify the mapping profiles to use same topics for both inbound and outbound profiles.
CWSIL0008W: The duplicate mapping for profile {0} was removed.
Explanation Only a single profile is registered for each topic in one direction to avoid duplicate messages. Messages will not be lost as a result of this removal. Action Remove the duplicate mapping from the configuration.
CWSIL0009W: Overlapping mapping for profile {0} was removed due to profile {1}.
Explanation Overlapping profiles are not registered to avoid duplicate messages. Messages will not be lost as a result of this removal. Action Remove the overlapping profile from the configuration.
CWSIL0010E: The topic for mapping {0} contains a single level wildcard, which is not supported.
Explanation The only wildcard supported is # at the end of a topic. Action Update the configuration to use valid topics.
CWSIL0011E: The topic for mapping {0} contains a multi-level wildcard in the middle, which is not supported.
Explanation The only wildcard supported is # at the end of a topic. Action Update the configuration to use valid topics.
CWSIL0012E: The attribute {1} to value {2} for object of type {0} cannot be set.
Explanation The attribute value has been ignored. Action More info at:
CWSIL0013E: The following incomplete topic mapping has been provided - {0}.
Explanation All mandatory fields should be filled in for topic mappings. Action Complete the topic mapping configuration.
CWSIL0016E: The response message received from the event broker {0} contained unexpected command {1} ({2}). The response corresponds to mapping profile {3}.
Explanation Only responses to register and deregister subscriptions are expected from the event broker. Action More info at:
CWSIL0017W: A response message received from the event broker {0} did not specify a command. The response corresponds to mapping profile {1}.
Explanation Only full responses containing request details of register and deregister subscriptions are expected from the event broker. Action More info at:
CWSIL0018E: Correlation ID {2} received in a response message from the event broker {0} does not match the expected correlation ID {1} for profile {3}.
Explanation The correlation ID for responses to commands from event broker should match the correlation ID specified in the command. Action More info at:
CWSIL0019E: The topic mapping could not be activated because topic space {0} does not exist. The mapping profile is {1}.
Explanation Topic spaces referenced by topic mappings should be created explicitly to create a mapping. Action Create the missing topic space.
CWSIL0020W: It is not possible to set up automatic routing of reply messages due to a missing broker input queue name on topic mapping {0}
Explanation The broker input queue name is required to automatically route reply messages. This warning may be ignored if reply messages are not required. Action The administrator must correctly fill in the broker input queue name in the named topic mapping.
CWSIL0021W: Allocated storage space for the broker profile associated with MQ link UUID {0} and broker queue manager {1} could not be immediately released.
Explanation A broker profile could not be immediately deleted when the user issued a deletion request, because there were active subscriptions associated with the broker profile. Action No action is necessary, the system will automatically request that the subscriptions be deactivated then it will try again later.
CWSIL0022W: It was not possible to release allocated storage space for the broker profile associated with MQ link UUID {0} and broker queue manager {1} because active subscriptions remained after an unsubscribe attempt.
Explanation A broker profile was not completely deleted when the user issued a deletion request, because active subscriptions remained associated with the broker profile following an automatic attempt to unsubscribe the active subscriptions. Action Restart the MQ link that the broker profile is associated with, the remaining persistent state will be deleted during the restart process.
CWSIL0023I: Allocated storage space for the broker profile associated with MQ link UUID {0} and broker queue manager {1} was successfully released after successful unsubscription processing.
Explanation It was not initially possible to release allocated storage space associated with the broker profile, but the successful completion of unsubscription processing for the profile has now allowed the storage space to be released. Action No action is necessary
CWSIL9999E: {0}
Explanation If the message does not give sufficient information, check previous messages for further help. Action See previous messages for further information.