MQJMS Messages

Method ''{0}'' has been invoked at an illegal or inappropriate time or if the provider is not in an appropriate state for the requested operation.

IBM MQ classes for JMS attempted to set invalid connection's client ID.

Destination not understood or no longer valid.

IBM MQ classes for JMS has given JMS Provider a message selector with invalid syntax.

Unexpected end of stream has been reached when a StreamMessage or BytesMessage is being read.

IBM MQ classes for JMS attempts to use a data type not supported by a message or attempts to read data in the wrong type.

IBM MQ classes for JMS attempts to read a write-only message.

IBM MQ classes for JMS attempts to write a read-only message.

IBM MQ classes for JMS is unable to allocate the resources required for a method.

Operation invalid because a transaction is in progress.

Call to Session.commit resulted in a rollback of the current transaction.

Failed to create JMS message.

Unknown acknowledge mode ''{0}''.

Connection closed.

Unhandled state transition from ''{0}'' to ''{1}''.

invalid value for ''{0}'': ''{1}''.

failed to create instance of exit class ''{0}''.

unknown value of transportType: ''{0}''.

no constructor with string argument.

not implemented.

security credentials cannot be specified when using MQ bindings.

no message listener.

operation invalid whilst session is using asynchronous delivery.

operation invalid for identified producer.

unknown value of target client: ''{0}''.

an internal error has occurred. Please contact the system administrator. Detail: ''{0}''.

non-local MQ queue not valid for receiving or browsing.

no valid connection available.

invalid operation for non-transacted session.

invalid operation for transacted session.

recover failed: unacknowledged messages might not get redelivered.

failed to redirect message.

rollback failed.

session closed.

failed to browse message.

ExceptionListener threw exception: ''{0}''.

failed to reconstitute destination from ''{0}''.

element name is null.

property name is null.

buffer supplied by application is too small.

an internal error has occurred. Please contact the system administrator.

close() failed because of ''{0}''.

start() failed because of ''{0}''.

MessageListener threw: ''{0}''.

invalid Delivery Mode.

String is not a valid hexadecimal number - ''{0}''.

Number outside of range for double precision S/390 Float ''{0}''.

The character set ''{0}'' is not supported.

The map message has an incorrect format.

The stream message has an incorrect format.

The IBM MQ classes for JMS attempted to convert a byte array to a String.

The MQRFH2 header has an incorrect format.

JMS Message class.

Unrecognizable JMS Message class.

Invalid UTF-16 surrogate detected ''{0}''.

Invalid XML escape sequence detected ''{0}''.

The property or element in the message has incompatible datatype ''{0}''.

Unsupported property or element datatype ''{0}''.

Message has no session associated with it.

Invalid message property name: ''{0}''.

Fatal error - UTF8 not supported.

Unable to serialize object.

Unable to deserialize object.

Exception occurred reading message body: ''{0}''.

Another ''{0}'' character(s) omitted.

Integer encoding: ''{0}''=Floating point encoding ''{1}''.

Exception occurred writing message body.

Invalid message element name: ''{0}''.

timeout invalid for MQ.

failed to obtain XAResource.

Not allowed with XASession.

Could not inquire upon Queue Manager name.

Specified MQ Queue is neither a QLOCAL nor a QALIAS.

Unable to process null message.

Error writing dead letter header.

Error reading dead letter header.

Connection/destination mismatch.

Invalid Session object.

Unable to write message to dead letter queue.

No Backout-Requeue queue defined.

Message requeue failed.

Failure while discarding message.

Error writing RFH.

Error reading RFH.

Unrecognizable or invalid RFH content.

Mixed-domain consumers acting on the same input is forbidden.

Exception occurred reading message body: ''{0}''.

operation invalid for unidentified producer.

A null parameter was passed to the constructor: ''{0}''.

Invalid quantityHint.

Invalid MessageReference.

Invalid MessageReference version.

Invalid MQQueueAgentThread version.

Multicast connection cannot be established.

Lost ''{0}'' messages in reliable multicast mode.

Multicast connection disconnected due to timeout.

Cannot connect with a specific local port for disthub multicast.

Unable to load the native library required for PGM/IP.

JMS1.1 Operation not supported by this type.

JMS1.1 The required Queues/Publish Subscribe services are not set up.

JMS1.1 Invalid operation for domain specific object.

JMS1.1 Invalid operation for cross domain object.

failed to close MQ queue.

MQ Queue reference is null.

failed to get message from MQ queue.

failed to disconnect queue manager.

MQQueueManager reference is null.

failed to create MQQueueManager for ''{0}''.

MQ problem: ''{0}''.

failed to send message to MQ queue.

failed to open MQ queue ''{0}''.

MQQueueManager.commit() failed.

unknown value for MQ queue definitionType: ''{0}''.

failed to inquire MQ queue depth.

XACLOSE failed.

invalid security authentication supplied for MQQueueManager.

Queue manager rejected XA client connection.

failed to create a temporary queue from ''{0}''.

temporary queue already closed or deleted.

temporary queue in use.

cannot delete a static queue.

failed to delete temporary queue.

Publish/Subscribe failed due to ''{0}''.

Topic reference is null.

Failed to build command ''{0}''.

Failed to publish command to MQ queue.

Failed to build publish message.

Failed to publish message to MQ queue.

Failed to store admin entry.

Failed to open subscriber queue ''{0}''.

Failed to delete subscriber queue ''{0}''.

Unknown durable subscription ''{0}''.

TemporaryTopic already deleted.

TemporaryTopic out of scope.

Invalid subscriber queue prefix: ''{0}''.

Durable re-subscribe must use same subscriber queue; specified:''{0}'' original:''{1}''.

Subscription has an active TopicSubscriber.

Illegal use of uninitialized client ID.

TemporaryTopic in use.

QueueSender is closed.

TopicPublisher is closed.

Can't set clientID after connection has been used.

Resetting the clientID is not allowed.

QueueReceiver is closed.

TopicSubscriber is closed.

Message Producer is closed.

Message Consumer is closed.

Illegal use of null name.

Invalid broker control message content: ''{0}''.

Field ''{0}'' already set.

Unrecognizable message from Pub/Sub Broker.

Invalid Level for repeating Cleanup.

Cleanup level of NONE requested.

Failed to open ''{0}'': maybe a FORCE or NONDUR level cleanup is running?

Failed to open ''{0}'': maybe another JMS application is using Pub/Sub with this queue manager?

Subscription Store type not supported by queue manager.

Incorrect Subscription Store type.

MQJMS_Messages.MQJMS_PS_ WRONG_SUBSCRIPTION_TYPE = Incorrect Subscription type for this Subscription Store.

Subscription is already in use and cannot be updated.

Invalid Subscription name.

Property value for ''{0}'' is null.

Invalid property for a ''{0}'': ''{1}''.

Expected and actual object types do not match.

*** No broker response. Please ensure that the broker is running. If we are using the IBM MQ broker check that your brokerVersion is set to V1 ***

Unexpected error ''{1}'' accessing internal queue ''{0}''.

Invalid socket family name: ''{0}''.

An exception occurred while attempting to load socket factory class ''{0}'', exception: <''{1}''>.

Cannot change parameter ''{0}'' since no more BaseConfig parameter changes are allowed.

Cannot set parameter ''{0}'' to value ''{1}''.

error occurred while getting BaseConfig parameter ''{0}''.

An exception occurred while loading the minimal client security implementation.

An unexpected exception in minimal client, ''{0}''.

A specified topic was malformed, ''{0}''.

EOF was encountered while receiving data in the minimal client.

The broker indicated an error on the minimal client connection.

Connector.send was called with an illegal message value.

An illegal value was encountered for a field, ''{0}''.

An unexpected internal error occurred in the minimal client.

A bytes message operation was requested on something that is not a bytes message.

A text message operation was requested on something that is not a text message.

A stream message operation was requested on something that is not a stream message.

A map message operation was requested on something that is not a map message.

The broker sent an invalid message during authentication.

The broker requested an unavailable protocol during authentication.

Minimal client connection rejected because of authentication failure.

No QOP available in the minimal client.

An exception occurred while attempting to load thread pooling support, ''{0}''.

An attempt was made to read from a Stream message before a previous read has completed.

An exception occurred while initializing a thread pool instance, ''{0}''.

No ExceptionListener has been set.

The client-side connection monitor is terminating.

Attempted to synchronously receive on a MessageConsumer for which a listener is active.

An IOException occurred when starting or stopping delivery on the connection, ''{0}''.

An exception occurred during synchronous receive, ''{0}''.

A JMSPriority level of ''{0}'' is outside the range specified in JMS.

The specified JMSMessageID, ''{0}'', is invalid.

No more client parameter changes allowed.

An exception occurred when initializing parameter ''{0}'', exception ''{1}''.

An exception occurred while creating the TopicConnection, ''{0}''.

This operation is not permitted on an entity that is closed.

The ''{0}'' implementation of Topic is not supported.

Topic ''{0}'' contains a wildcard which is invalid for publishing.

An IOException occurred while publishing, ''{0}''.

Attempted to use a temporary topic not created on the current connection.

An IOException occurred while subscribing, ''{0}''.

While creating a TopicSubscriber, attempting to add the subscription to the matching engine resulted in the following exception: ''{0}''.

An unexpected exception was caught in the matching engine: ''{0}''.

An attempt was made to remove an object with topic ''{0}'' from an empty matching engine: ''{1}''.

An attempt was made to remove an object with topic ''{0}'' from the matching engine, but it did not have a cache entry: ''{1}''.

An unknown check type of class ''{0}'' was encountered in a type-specific matcher.

An attempt was made to access an unknown field named ''{0}''.

In attempting to access a field of a message=the following exception occurred: ''{0}''.

An EvalCache get or put operation occurred when the cache was not loaded.

An EvalCache get or put operation specified an invalid ID.

Too many content attributes were specified.

A duplicate MatchTarget was detected in MatchSpace.

An attempt was made to remove MatchTarget ''{0}'' from MatchSpace, but it has no key (topic).

The MatchTarget ''{1}'' with key (topic) ''{0}'' could not be removed from MatchSpace because it could not be found.

An attempt was made to add a MatchTarget to MatchSpace without a key (topic).

An incorrect use of a the topic wildcard character ''{0}'' was detected.

The topic segment separator ''{0}'' appears in an incorrect position.

An error occurred while trying to load or invoke the subscription selector parser.

The following exception occurred while parsing a subscription selector: ''{0}''.

The escape character was used to terminate the following pattern: ''{0}''.

The escape character ''{0}'' passed to the pattern tool is longer than one character.

A message field was expected to contain a value of type ''{0}'' but contained one of type ''{1}''.

Minimal client authentication failed because exception ''{0}''.

QOP required but disabled for this minimal client.

Non-authorized subscription to topic ''{0}''.

Transport type 'DIRECT' within a transaction is not supported.

An object message operation was requested on something that is not an object message.

An exception occurred when creating subscription to <''{0}'',''{1}''>, ''{2}''.

Persistent messages not supported for transport type 'DIRECT'.

Time to Live > 0 not supported for transport type 'DIRECT'.

Topic Expiry > 0 not supported for transport type 'DIRECT'.

Client Acknowledge not supported for transport type 'DIRECT'.