com.ibm.ws.sib.admin.internal.CWSIDMessages

CWSID0001I: Messaging engine {0} is initializing.
CWSID0003E: An internal error occurred; reason: {0}
CWSID0009E: Destination {0} cannot be created.
CWSID0011W: It is not possible to activate JMX {0} MBean named {1}.
CWSID0012W: It is not possible to deactivate JMX {0} MBean named {1}.
CWSID0013W: It is not possible to load class {0}.
CWSID0027E: Messaging engine {0} cannot be restarted because a serious error has been reported.
CWSID0028W: Messaging engine {0} cannot be stopped from current state {1}.
CWSID0029E: Messaging engine {0} suffered a common mode error.
CWSID0031E: Messaging engine {0} suffered a common mode error and has been stopped.
CWSID0033E: Messaging engine {0} cannot be initialized; caught exception thrown by {1} {2}
CWSID0034E: Messaging engine {0} cannot be started: caught exception thrown by {1} {2}
CWSID0035E: Messaging engine {0} cannot be started; detected error reported during {1} {2}
CWSID0036E: Messaging engine {0} caught exception thrown by {1} {2} method during cleanup of failed start
CWSID0037E: Messaging engine {0} caught exception thrown by {1} {2} method
CWSID0043W: It is not possible to send an Event Notification from JMX {0} MBean named {1}.
CWSID0044I: Messaging Engine {0} with UUID {1} has been started.
CWSID0045I: Messaging Engine {0} with UUID {1} has stopped.
CWSID0046E: Messaging engine {0} detected an error and cannot continue to run in this server.
CWSID0048W: The value for the receiveExclusive attribute has been overridden to become "true" for the {0} destination.
CWSID0049I: Messaging Engine {0} with UUID {1} is starting.
CWSID0050I: Messaging Engine {0} with UUID {1} is stopping.
CWSID0052I: Messaging Engine {0} with UUID {1} failed to stop.
CWSID0100I: No ID provided for messagingEngine tag in the server configuration file. Default ID {0} will be considered.
CWSID0102E: No ID is defined in the server configuration file for the destination of type {0}.
CWSID0104I: fileStore tag has not been defined in the server configuration file, hence defaults will be used.
CWSID0105I: Messaging engine ID cannot be changed after the server is started.
CWSID0106I: Attempting to start the messaging engine.
CWSID0107I: Starting the JMS server.
CWSID0108I: JMS server has started.
CWSID0109E: An internal messaging error occurred. JMS server could not be started.
CWSID0110E: No target Destination provided for Alias Destination {0}.
CWSID0113E: Exception found during destination {0} localization.
CWSID0114E: Destination {0} cannot be populated in cache.
CWSID0115E: An internal error occurred because the messaging engine configuration properties are not received. Hence the messaging engine will not be started.
CWSID0116E: An internal error occurred because the messaging engine configuration properties are not received. Hence, no modification will be done to the messaging engine.
CWSID0117E: The system received an internal effort after a modification to the messaging engine configuration did not complete successfully
CWSID0118E: The value specified for defaultReliability is greater than the value specified for maxReliability.
CWSID0119I: The filestore path: {0}
CWSID0120E: The Messaging engine could not be started because an invalid file path {0} was specified in server configuration file.
CWSID0121I: JMS server stopped.
CWSID0122I: No messaging engine ID is provided in the server configuration file.
CWSID0123W: {0} is used for multiple destinations.
CWSID0124E: The log file size of {0} megabytes should be less than half the size of the file store {1} megabytes. Either increase the size of the file store or decrease the size of the log file.
CWSID0125E: The alias destination ID {0} is already defined for a Queue or TopicSpace, hence the alias destination will not be created.
CWSID9999E: {0}