WMSG

WMSG0001I: JMS Listener started successfully
WMSG0002I: JMS Listener stopped successfully
WMSG0003E: Error initializing JMSListenerStub: {0}
WMSG0004E: Error initializing JMSListenerStub: {0}
WMSG0005E: Error creating MDBListener for JMS Listener {0}, JMSDestination {1} : {2}
WMSG0006E: Error creating MDBListener for JMS Listener {0}, JMSDestination {1} : {2}
WMSG0007E: Error starting JMSListenerStub: {0}
WMSG0008E: Error starting JMSListenerStub: {0}
WMSG0009W: Error terminating JMSListenerStub : {0}
WMSG0010E: Error parsing JMSListener config file: {0}, {1}
WMSG0011W: Warnings parsing JMS Listener config file: {0}, {1}
WMSG0012E: Errors parsing JMS Listener config file: {0}, {1}
WMSG0013E: Errors parsing JMS Listener config file: {0}, {1}
WMSG0014E: Error parsing JMSListener config file: {0}, line: {1}, column: {2}, message: {3}
WMSG0015E: Error parsing JMSListener config file: {0}, message: {1}
WMSG0016E: postInvoke exception for MDB {0} listening upon JMSDestination {1}, exception: {2}
WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: {0}
WMSG0018E: Error on JMSConnection for MDB {0}, JMSDestination {1} : {2}
WMSG0019E: Unable to start MDB Listener {0}, JMSDestination {1} : {2}
WMSG0020E: Unable to stop MDB Listener {0}, JMSDestination {1} : {2}
WMSG0021E: Exception constructing MDBListenerImpl {0}, JMSDestination {1} : {2}
WMSG0022E: Duplicate MDBListener definition for {0}, JMSDestination {1}
WMSG0023W: Exception closing MDBListener {0}, JMSDestination {1} : {2}
WMSG0024W: Exception terminating MDBListener {0}, JMSDestination {1} : {2}
WMSG0025E: MessageDrivenBean does not have any security permissions configured
WMSG0026E: Exception invoking MessageDrivenBean.onMessage() for MDB {0} : {1}
WMSG0027E: Exception invoking MessageDrivenBean.onMessage() for MDB {0} : {1}
WMSG0028E: Exception creating JMS ServerSession for MDB {0}, JMSDestination {1} : {2}
WMSG0029E: Error during JMSListener server login for MDB {0}, JMSDestination {1} : {2}
WMSG0030E: Exception beginning JMS ServerSession transaction for MDB {0}, JMSDestination {1} : {2}
WMSG0031E: Exception processing JMS Message for MDB {0}, JMSDestination {1} : {2}
WMSG0032E: Unable to rollback JMS ServerSession transaction for MDB {0}, JMSDestination {1} : {2}
WMSG0033E: Exception committing JMS ServerSession transaction for MDB {0}, JMSDestination {1} : {2}
WMSG0034E: Exception rollingback JMS Session for MDB {0}, JMSDestination {1} : {2}
WMSG0035E: Exception committing JMS Session for MDB {0}, JMSDestination {1} : {2}
WMSG0036E: Maximum message delivery retry count of {0} reached for MDB {1}, JMSDestination {2}, MDBListener stopped
WMSG0037E: Exception starting JMS ServerSession for MDB {0}, JMSDestination {1} : {2}
WMSG0038E: Exception in MDBPooledThread: {0}
WMSG0039E: Exception in MDBPooledThread: {0}
WMSG0040W: JMS Listener started with warnings
WMSG0041E: JMS Listener failed to start
WMSG0042I: MDB Listener {0} started successfully for JMSDestination {1}
WMSG0043I: MDB Listener {0} stopped for JMSDestination {1}
WMSG0044W: MDB Listener listening on JMSDestination {1} has not started as the EJB {0} is not installed
WMSG0045E: JMS Listener initialization failed
WMSG0046E: Unable to find Listener Port {1} for binding MDB {0}
WMSG0047E: MessageDrivenBeanBinding does not exist for MDB {0}
WMSG0048W: Exception activating JMX MBean {0}, exception {1}
WMSG0049E: Failed to start MDB {0} against listener port {1}
WMSG0050E: Exception checking JMS durable subscriptions {0}
WMSG0051E: Exception updating the JMS durable subscriptions log {0}
WMSG0052E: Exception unsubscribing JMS durable subscription {0} : {1}
WMSG0053I: Redundent JMS durable subscription {0} has been unsubscribed
WMSG0054E: Exception writing to the Late Response Message Consumer Log {0}, {1}
WMSG0055E: Exception reading the Late Response Message Consumer Log {0}, {1}
WMSG0056W: MDB Listener Port {0} maximum sessions size of {1} is greater than its JMS Connection Factory {2} Session Pool size of {3}, setting maximum sessions to {3}
WMSG0057E: Error on JMSConnection for MDB {0}, JMSDestination {1}, JMS Linked Exception : {2}
WMSG0058I: Listener Port {0} will attempt to restart in {1} seconds
WMSG0059E: Maximum restart retry count of {0} reached for Listener Port {1}
WMSG0060W: Unknown activation config property {1} specified for binding MDB {0}.
WMSG0061W: An Internal error has occured. The activation config expected a param of type {2} but got a {1} in MDB {0}
WMSG0062W: The JNDI specified in the listener port ({1}) is not the same as that specifed in the bindings {2} for MDB {0}
WMSG0063E: Unable to start message-driven bean (MDB) {0} against listener port {1}. It is not valid to specify a default messaging Java Message Service (JMS) resource for a listener port; either use a different JMS resource with a listener port or use a default messaging JMS resource with an activation specification.
WMSG0064E: Unable to start message-driven bean (MDB) {0} against listener port {1}. It is not valid to specify a Java Message Service (JMS) resource adapter resource for a listener port; either use a different JMS resource with a listener port or use a default messaging JMS resource with an activation specification.
WMSG0100E: User is not authorised to access Command Queue
WMSG0101I: Invalid default priority specified. reason = {0}, parameter = {1}.
WMSG0102I: Invalid maximum Queue depth specified. reason = {0}, parameter = {1}.
WMSG0103I: Invalid maximum message length specified. reason = {0}, parameter = {1}.
WMSG0104I: Invalid backout threshold specified. reason = {0}, parameter = {1}.
WMSG0105I: Invalid Queue name specified. reason = {0}, parameter = {1}.
WMSG0106I: Invalid Queue description specified. reason = {0}, parameter = {1}.
WMSG0107I: Invalid Cluster name specified. reason = {0}, parameter = {1}.
WMSG0108I: Invalid Cluster name list specified. reason = {0}, parameter = {1}.
WMSG0109I: Invalid backout Queue name specified. reason = {0}, parameter = {1}.
WMSG0110I: Invalid remote Queue Manager name specified. reason = {0}, parameter = {1}.
WMSG0111I: Invalid remote Queue name specified. reason = {0}, parameter = {1}.
WMSG0112I: Invalid transmission Queue name specified. reason = {0}, parameter = {1}.
WMSG0113I: Unrecognised parameter is invalid. reason = {0}, parameter = {1}.
WMSG0114I: Queue name is over 48 characters long. reason = {0}, parameter = {1}.
WMSG0115I: Queue description is over 64 characters long. reason = {0}, parameter = {1}.
WMSG0117I: Cluster name list is over 48 characters long. reason = {0}, parameter = {1}.
WMSG0118I: Backout Queue name is over 48 characters long. reason = {0}, parameter = {1}.
WMSG0119I: Remote Queue Manager name is over 48 characters long. reason = {0}, parameter = {1}.
WMSG0120I: Cluster name is over 48 characters long. reason = {0}, parameter = {1}.
WMSG0121I: Transmission Queue name is over 48 characters long. reason = {0}, parameter = {1}.
WMSG0122I: Unknown Parameter is too long. reason = {0}, parameter = {1}.
WMSG0123I: An error occurred that is not recognised. reason = {0}, parameter = {1}.
WMSG0124E: An internal MQ queue definer MBean error has occurred.
WMSG0300E: The {0} setting was not a valid value.
WMSG0301E: The settings you chose would have made the Queue a cluster Queue and a transmission Queue.
WMSG0302E: The action you tried did not complete. Check the other errors to determine the cause.
WMSG0303E: The Queue you tried to create already existed.
WMSG0304E: The Queue name you specified contained invalid characters.
WMSG0305E: Unable to perform the action as the Queue was open.
WMSG0306E: Unexpected error occurred. PCF reason code {0}, please check the WebSphere MQ documentation for a description of the error.
WMSG0307E: Unable to connect to the Queue Manager.
WMSG0308E: The message was too big for the Queue.
WMSG0309E: You are not authorized to perform these actions.
WMSG0310E: Deletion of the Queue failed as it contains some messages that could not be removed.
WMSG0311E: There has been a selector error.
WMSG0312E: There is not enough main storage to perform the action.
WMSG0313E: The Queue you tried to modify does not exist.
WMSG0314E: Unexpected error occurred. MQ reason code {0}, please check the WebSphere MQ Information Center for a description of the error.
WMSG0315E: Unexpected IO error occurred.
WMSG0316E: You tried to view a Queue that was not a local Queue. Only administration of local Queues is supported.
WMSG0317E: The Command Server has returned some invalid Queue settings.
WMSG0318E: The Command Server has returned some attributes of the incorrect type.
WMSG0319E: The Queue name you have specified is invalid.
WMSG0320E: Internal Queue Manager error.
WMSG0321E: Internal Queue Manager error.
WMSG0322E: The Queue Manager name was either invalid or not known.
WMSG0323E: The Queue Manager is not available.
WMSG0324E: The Queue Manager is inactive.
WMSG0325E: The Queue Manager is stopping.
WMSG0326E: The Port number specifed was not a valid number.
WMSG0327E: The Queue Depth specified was not a valid number.
WMSG0328E: The Maximum Message Length specified was not a valid number.
WMSG0329E: The Backout Threshold specified was not a valid number.
WMSG0330E: The specified priority was not a number.
WMSG0331E: The MQ Client is required for this functionality, but it is not installed.
WMSG0332E: The Name of the MQ Queue is required by the WMQQueueDefiner MBean
WMSG0333E: The Name of the MQ Queue Manager is required by the WMQQueueDefiner MBean.
WMSG0334E: The Host name that the Queue Manager is running on is required by the WMQQueueDefiner MBean.
WMSG0335E: The Host name that the Queue Manager is running on is required by the WMQQueueDefiner MBean.
WMSG0336E: You specified a null value where a String was required.
WMSG0337E: A value that was too short was specified.
WMSG0338E: The Queue Name was set twice.
WMSG0339E: The value specified was not one of the valid value
WMSG0340E: The value specified was less than zero
WMSG0341E: The Cluster name you specified contained invalid characters.
WMSG0342E: The Cluster Namelist you specified contained invalid characters.
WMSG0343E: The Backout Re-Queue Queue Name you specified contained invalid characters.
WMSG0344E: The Queue Description you specified contained invalid characters.
WMSG0345E: An unknown Parameter contained invalid characters.
WMSG0346E: A value that was too long was specified.
WMSG0500E: It is not possible to set a javax.jms.MessageListener on a javax.jms.MessageConsumer of the type {0}.
WMSG0501E: An internal error occurred. The javax.jms.MessageConsumer implementation {0} is invalid for use with the {1} com.ibm.wsspi.JmsMessageListenerSupport.MessageListenerSetter.
WMSG0900W: JMS resource binder for resource type {0} is disabled
WMSG0901E: The WebSphere MQ JMS Binders have been disabled as the WebSphere MQ JMS Client has not been installed.
WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set.
WMSG1152E: Unable to define JMS Destination {0} as the Queue name is too long - maximum length is {1} characters
WMSG1300E: An error occurred building the reference for JNDI deployment of {0}. Error code {1} was returned from MQ with the error messages [{2}] and [{3}]
WMSG1301E: An exception occurred building the reference for JNDI deployment of {0}
WMSG1303E: Unable to define JMS Destination {0} as neither WebSphere Embedded Messaging nor WebSphere MQ JMS is available
WMSG1600E: An exception occurred determining the WebSphere MQ JMS paths: {0}
WMSG1601I: WebSphere MQ JMS has not been installed
WMSG1602I: WebSphere MQ JMS Client only has been installed
WMSG1603E: An internal error occurred. It was not possible to register the WebSphere MQ JMS client with the application server due to exception {0}.
WMSG1604E: It was not possible to use the specified WebSphere MQ JMS client at path {0} because it is at version {1}, the minimum supported version is {2}.
WMSG1605E: It was not possible to detect the MQ JMS client at the specified path {0}.
WMSG1606E: An internal error occurred.
WMSG1607E: An internal error occurred. Unexpected object type {0}.
WMSG1608E: An internal error occurred.
WMSG1609E: An internal error occurred. Unexpected object type {0}.
WMSG1610E: An exception occurred instantiating a WebSphere MQ JCA RA type connection factory.
WMSG1611I: The installed level of the WebSphere MQ messaging provider is {0}.
WMSG1612E: The MQ_INSTALL_ROOT has been updated from {0} to {1}. The WebSphere MQ Messaging Provider has been disabled. A server restart is required to re-enable the function.
WMSG1613W: The WebSphere MQ installed at {0} has been updated from version {1} to version {2}. A server restart may be required to properly register this update.
WMSG1614E: The WebSphere MQ installed at {0} has been updated and a server restart is required for the the WebSphere MQ Messaging Provider to work with this update. The WebSphere MQ Messaging Provider has been disabled.
WMSG1622E: The installation directory of the WebSphere MQ messaging provider has been updated from {0} to {1}. The WebSphere MQ messaging provider has been disabled. A server restart is required to re-enable this function.
WMSG1623E: The WebSphere MQ messaging provider installed at {0} has been updated and an application server restart is required to pick up this update. The WebSphere MQ messaging provider has been disabled.
WMSG1624E: It was not possible to use the specified WebSphere MQ messaging provider at path {0} because it is at version {1}. The minimum supported version is {2}.
WMSG1625E: It was not possible to detect the WebSphere MQ messaging provider code at the specified path {0}.
WMSG1626W: The WebSphere MQ messaging provider installed at {0} has been updated from version {1} to version {2}. A server restart may be required to properly register this update.
WMSG1627I: Native libraries for the WebSphere MQ messaging provider will be loaded from the following directory: {0}.
WMSG1700I: Currently active WebSphere MQ messaging provider configuration in WebSphere Application Server {0}, report at {1});
WMSG1701I: Using the WebSphere MQ messaging provider
WMSG1702I: Using the WebSphere MQ Resource Adapter
WMSG1703I: RAR implementation version {0}
WMSG1705I: Information from WebSphere MQ messaging provider follows:
WMSG1707I: Unable to obtain any version information from WebSphere MQ messaging provider because of exception: {0}
WMSG1708I: WebSphere MQ messaging provider configuration is not valid
WMSG1709I: WebSphere MQ messaging provider is not configured
WMSG1710I: Install Directory is {0}.
WMSG1711I: Native File Directory is {0}.
WMSG1712I: Version is {0}.
WMSG1713I: Jar Files: {0}.
WMSG1714I: Native Libraries {0}
WMSG1715I: Name is {0}.
WMSG1716I: Title is {0}.
WMSG1717I: Type is {0}.
WMSG1718I: Version is {0}.
WMSG1719I: Implementation info is {0}.
WMSG1720I: All WebSphere MQ functionality on this server has been disabled.
WMSG3000E: The mandatory property JmsActSpecJndiName is not set on the activation specification {0} of the resource adapter wrapper.
WMSG3001E: The mandatory property ID is not set on the activation specification {0} of the resource adapter wrapper.
WMSG3010E: The activate endpoint method was called with an activation specification of type {1} when a type of {0} is expected.
WMSG3011E: During deactivation, the endpoint created the following exception: {0}
WMSG3012E: The endpoint that the resource adapter wrapper {1} wraps for endpoint {0} is already activated.
WMSG3013E: The endpoint that the resource adapter wrapper {1} wraps for endpoint {0} is not activated.
WMSG3080E: The system called an unexpected method. The createEndpoint method was called on a message endpoint factory in the Control Region Adjunct on z/OS.
WMSG3100E: An error occurred during before delivery processing, see linked exception for more information: {0}
WMSG3101E: An error occurred during after-delivery processing. See the linked exception for more information: {0}
WMSG3102E: An error occurred because the method {0} is not expected to be called for application {1}.
WMSG3103E: An error occurred because the method {0} is not expected to be called for application {1}.
WMSG3104E: An error occurred because the method {0} is not expected to be called for application {1}.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ejs.jms.messaging.dita
File name: com.ibm.ejs.jms.messaging.html