com.ibm.mq.jms.services
Class MQJMS_Messages
java.lang.Object
|
+--com.ibm.mq.jms.services.MQJMS_Messages
- public final class MQJMS_Messages
- extends java.lang.Object
Defines the most common exceptions that can be generated by
WebSphere MQ JMS. It does not include all messages that can be written to
a trace file. If you receive an exception message not in this list (except
in a trace file), or if the cause seems to be an error in WebSphere MQ JMS,
contact your IBM service representative.
A JMSException might have an embedded exception that contains a WebSphere
MQ reason code. For an explanation of each WebSphere MQ reason code, see
the WebSphere Messages and Websphere MQ z/OS Messages and Codes books.
Reading variables in a message: Some messages display text or numbers
that vary according to the circumstances giving rise to the message; these
are known as message variables. Message variables are indicated by the use
of numbers in braces; for example, {0}, {1}, and so on.
Field Summary |
static java.lang.String |
MQJMS_ADMIN_BIND_FAIL
Unable to bind object.
|
static java.lang.String |
MQJMS_ADMIN_BND_NONADMIN
Binding non-administerable or not found.
|
static java.lang.String |
MQJMS_ADMIN_CLASH_CLIENT
Clash of the client properties.
|
static java.lang.String |
MQJMS_ADMIN_CLASH_EXITINIT
ExitInit string supplied without Exit string.
|
static java.lang.String |
MQJMS_ADMIN_CNT_OPEN_CFG
Cannot open configuration file.
|
static java.lang.String |
MQJMS_ADMIN_CONF_MISSING
Missing configuration properties.
|
static java.lang.String |
MQJMS_ADMIN_CONVERT_CIPHER
Matching CipherSpec {0} to CipherSuite {1} not possible.
|
static java.lang.String |
MQJMS_ADMIN_CTX_NOT_EMPTY
Context is not empty.
|
static java.lang.String |
MQJMS_ADMIN_CTX_NOTFND
Context not found.
|
static java.lang.String |
MQJMS_ADMIN_CTX_NOTFNDU
Context not found or cannot be deleted.
|
static java.lang.String |
MQJMS_ADMIN_ERROR
Error.
|
static java.lang.String |
MQJMS_ADMIN_ICF_NOT_FOUND
Class specified by INITIAL_CONTEXT_FACTORY not found in CLASSPATH.
|
static java.lang.String |
MQJMS_ADMIN_INV_PROP
Parameter {1} for method {0} was not valid.
|
static java.lang.String |
MQJMS_ADMIN_INV_PROP_CTX
The property was not valid in this context.
|
static java.lang.String |
MQJMS_ADMIN_INV_PROP_VAL
Value {1} for property {0} was not valid.
|
static java.lang.String |
MQJMS_ADMIN_INVALID_AUTH_TYPE
The authentication type supplied was not valid - used none.
|
static java.lang.String |
MQJMS_ADMIN_INVALID_NAME
A name was supplied that was not valid.
|
static java.lang.String |
MQJMS_ADMIN_JNDI_INITFAIL
JNDI initialization failed.
|
static java.lang.String |
MQJMS_ADMIN_LEXERR
Lexical error.
|
static java.lang.String |
MQJMS_ADMIN_MV_SEMIFAIL
Unable to complete MOVE; a COPY has been done instead.
|
static java.lang.String |
MQJMS_ADMIN_NEW_CTX_FAIL
Unable to create context.
|
static java.lang.String |
MQJMS_ADMIN_NON_MQJMS
Object is not a WebSphere MQ JMS administered object.
|
static java.lang.String |
MQJMS_ADMIN_OBJ_INACTIVE
Object is inactive, so cannot perform directory operations.
|
static java.lang.String |
MQJMS_ADMIN_OBJTYPE_MISMATCH
Expected and actual object types do not match.
|
static java.lang.String |
MQJMS_ADMIN_PROP_UNK
Unknown parameter: {0}.
|
static java.lang.String |
MQJMS_ADMIN_PROPVAL_NULL
Parameter {0} is null.
|
static java.lang.String |
MQJMS_ADMIN_SYN_ERR
Syntax error.
|
static java.lang.String |
MQJMS_ADMIN_VAL_OBJ_FAIL
Unable to create a valid object.
|
static java.lang.String |
MQJMS_ADMIN_WS_INST
Unable to create a WebSphere MQ specific class.
|
static java.lang.String |
MQJMS_CLIENTID_FIXED
Client ID cannot be set after connection has been used.
|
static java.lang.String |
MQJMS_CLIENTID_NO_RESET
Resetting the Client ID is not allowed.
|
static java.lang.String |
MQJMS_DIR_IMB_BADSOCKNAME
The socket family name: {0} is not valid.
|
static java.lang.String |
MQJMS_DIR_IMB_NOCLASS
An exception occurred while attempting to load socket factory class {0}, exception: <{1}>.
|
static java.lang.String |
MQJMS_DIR_JMS_BADID
The specified JMSMessageID, {0}, is not valid.
|
static java.lang.String |
MQJMS_DIR_JMS_BADNUM
Exception {1} occurred when initializing parameter {0}.
|
static java.lang.String |
MQJMS_DIR_JMS_BDTOPIMPL
The {0} implementation of Topic is not supported.
|
static java.lang.String |
MQJMS_DIR_JMS_CLOSED
Operation not permitted on an entity that is closed.
|
static java.lang.String |
MQJMS_DIR_JMS_FMTINT
An attempt was made to read from a Stream message before a previous read has completed.
|
static java.lang.String |
MQJMS_DIR_JMS_INVPRI
A JMSPriority level of {0} is outside the range specified in JMS.
|
static java.lang.String |
MQJMS_DIR_JMS_KILLMON
The client-side connection monitor is terminating.
|
static java.lang.String |
MQJMS_DIR_JMS_LSTACT
Attempted to synchronously receive on a MessageConsumer for which a listener is active.
|
static java.lang.String |
MQJMS_DIR_JMS_NEXCLIS
No ExceptionListener was set.
|
static java.lang.String |
MQJMS_DIR_JMS_NOMORE
No more client parameter changes allowed.
|
static java.lang.String |
MQJMS_DIR_JMS_NOTHDPOOL
An exception occurred while attempting to load thread pooling support; {0}.
|
static java.lang.String |
MQJMS_DIR_JMS_PBIOERR
An IOException occurred while publishing; {0}.
|
static java.lang.String |
MQJMS_DIR_JMS_PBNOWLD
Topic {0} contains a wildcard, which is invalid for publishing.
|
static java.lang.String |
MQJMS_DIR_JMS_RUNKEXC
An exception occurred during synchronous receive; {0}.
|
static java.lang.String |
MQJMS_DIR_JMS_TCFLERR
An exception occurred while creating the TopicConnection; {0}.
|
static java.lang.String |
MQJMS_DIR_JMS_TCSTSTP
An IOException occurred when starting or stopping delivery on the connection; {0}.
|
static java.lang.String |
MQJMS_DIR_JMS_THDEXC
An exception occurred while initializing a thread pool instance; {0}.
|
static java.lang.String |
MQJMS_DIR_JMS_TMPVIO
Wrong use of temporary topic with the current connection.
|
static java.lang.String |
MQJMS_DIR_JMS_TSBADMTC
While creating a TopicSubscriber attempting to add the subscription to the matching
engine resulted in exception: {0}.
|
static java.lang.String |
MQJMS_DIR_JMS_TSIOERR
An IOException occurred while subscribing; {0}.
|
static java.lang.String |
MQJMS_DIR_MIN_ACK_NOT_SUPPORTED
Client Acknowledge is not supported for transport type DIRECT.
|
static java.lang.String |
MQJMS_DIR_MIN_AUTHREJ
Minimal client connection rejected because of authentication failure.
|
static java.lang.String |
MQJMS_DIR_MIN_BADBRKMSG
The broker sent a message during authentication which was not valid.
|
static java.lang.String |
MQJMS_DIR_MIN_BADFIELD
The value of field {0} is not valid.
|
static java.lang.String |
MQJMS_DIR_MIN_BADMSG
Connector.send was called with a message value that is not valid.
|
static java.lang.String |
MQJMS_DIR_MIN_BADTOP
A specified topic was malformed, topic; {0}.
|
static java.lang.String |
MQJMS_DIR_MIN_BRKERR
The broker indicated an error on the minimal client connection.
|
static java.lang.String |
MQJMS_DIR_MIN_EOF
End of file (EOF) was encountered while receiving data in the minimal client.
|
static java.lang.String |
MQJMS_DIR_MIN_EXP_NOT_SUPPORTED
A Topic Expiry greater than zero not supported for transport type DIRECT.
|
static java.lang.String |
MQJMS_DIR_MIN_INTERR
An unexpected internal error occurred in the minimal client.
|
static java.lang.String |
MQJMS_DIR_MIN_NOQOP
No QOP available in the minimal client.
|
static java.lang.String |
MQJMS_DIR_MIN_NOSUB
Unauthorized subscription to topic {0}.
|
static java.lang.String |
MQJMS_DIR_MIN_NOTBYTES
A Byte message operation was requested on something that is not a Byte message.
|
static java.lang.String |
MQJMS_DIR_MIN_NOTMAP
A Map message operation was requested on something that is not a Map message.
|
static java.lang.String |
MQJMS_DIR_MIN_NOTSTREAM
A Stream message operation was requested on something that is not a Stream message.
|
static java.lang.String |
MQJMS_DIR_MIN_NOTTEXT
A Text message operation was requested on something that is not a Text message.
|
static java.lang.String |
MQJMS_DIR_MIN_NOXASUP
Transport type DIRECT within a transaction is not supported.
|
static java.lang.String |
MQJMS_DIR_MIN_PER_NOT_SUPPORTED
Persistent messages not supported for transport type DIRECT.
|
static java.lang.String |
MQJMS_DIR_MIN_SECLDERR
An exception occurred while loading the minimal client security implementation.
|
static java.lang.String |
MQJMS_DIR_MIN_TTL_NOT_SUPPORTED
Time to Live greater than zero not supported for transport type DIRECT.
|
static java.lang.String |
MQJMS_DIR_MIN_UNVPRO
The broker requested an unavailable protocol during authentication.
|
static java.lang.String |
MQJMS_DIR_MIN_UNXEXC
An unexpected exception in minimal client; {0}.
|
static java.lang.String |
MQJMS_DIR_MTCH_BDESC
The escape sequence was used to terminate the pattern; {0}.
|
static java.lang.String |
MQJMS_DIR_MTCH_BDESCL
The escape sequence {0} passed to the pattern tool is longer than one character.
|
static java.lang.String |
MQJMS_DIR_MTCH_BDMSG
An exception occured while attempting to access a field of a message; {0}.
|
static java.lang.String |
MQJMS_DIR_MTCH_BDSEP
The Topic segment separator {0} appears in an incorrect position.
|
static java.lang.String |
MQJMS_DIR_MTCH_BDWLD
An incorrect use of the Topic wildcard character {0} was detected.
|
static java.lang.String |
MQJMS_DIR_MTCH_ECNMIN
An EvalCache get or put operation specified an invalid ID.
|
static java.lang.String |
MQJMS_DIR_MTCH_NULCH
An attempt was made to remove an object with a Topic {0} from the matching engine, but it
did not have a cache entry: {1}.
|
static java.lang.String |
MQJMS_DIR_MTCH_NULRM
An attempt was made to remove an object with Topic {0} from an empty matching engine: {1}.
|
static java.lang.String |
MQJMS_DIR_MTCH_PSTPER
An exception occurred while parsing a subscription selector; {0}.
|
static java.lang.String |
MQJMS_DIR_MTCH_TOMNY
Too many content attributes were specified.
|
static java.lang.String |
MQJMS_DIR_MTCH_UNKEXC
An unexpected exception occured in the matching engine: {0}.
|
static java.lang.String |
MQJMS_DIR_MTCH_UNXTYP
A message field was expected to contain a value of type {0} but contained one of type {1}.
|
static java.lang.String |
MQJMS_DIR_PGM_LIB_NOT_FOUND
Unable to load the native library required for PGM/IP.
|
static java.lang.String |
MQJMS_E_11_INVALID_CROSS_DOMAIN
Attribute for a domain specific object was not valid.
|
static java.lang.String |
MQJMS_E_11_INVALID_DOMAIN_SPECIFIC
Operation for a domain specific object was not valid.
|
static java.lang.String |
MQJMS_E_11_SERVICES_NOT_SETUP
The required queues or publish/subscribe services are not set up: {0}.
|
static java.lang.String |
MQJMS_E_BAD_CCSID
The character set {0} is not supported.
|
static java.lang.String |
MQJMS_E_BAD_DEST_STR
Failed to reconstitute destination from {0}.
|
static java.lang.String |
MQJMS_E_BAD_ELEMENT_NAME
Message element name: {0} is not valid.
|
static java.lang.String |
MQJMS_E_BAD_EXIT_CLASS
Failed to create instance of exit class {0}.
|
static java.lang.String |
MQJMS_E_BAD_PROPERTY_NAME
Invalid message property name: {0}.
|
static java.lang.String |
MQJMS_E_BAD_RFH2
The MQRFH2 header has an incorrect format.
|
static java.lang.String |
MQJMS_E_BAD_TIMEOUT
Timeout not valid for WebSphere MQ.
|
static java.lang.String |
MQJMS_E_BAD_TYPE
The property or element in the message has an incompatible datatype {0}.
|
static java.lang.String |
MQJMS_E_BATCH_SIZE
Incorrect message batch size (must be greater than zero).
|
static java.lang.String |
MQJMS_E_BROKER_MESSAGE_CONTENT
The broker control message content: {0} is not valid.
|
static java.lang.String |
MQJMS_E_BROWSE_MSG_FAILED
Failed to browse message.
|
static java.lang.String |
MQJMS_E_BYTE_TO_STRING
The JMS client attempted to convert a byte array to a String.
|
static java.lang.String |
MQJMS_E_CC_MIXED_DOMAIN
Mixed-domain consumers acting on the same input is forbidden.
|
static java.lang.String |
MQJMS_E_CLEANUP_NONE_REQUESTED
Cleanup level of NONE requested.
|
static java.lang.String |
MQJMS_E_CLEANUP_REP_BAD_LEVEL
Level for repeating Cleanup is not valid.
|
static java.lang.String |
MQJMS_E_CLOSE_FAILED
Close failed because of {0}.
|
static java.lang.String |
MQJMS_E_CONN_DEST_MISMATCH
Connection and Destination mismatch.
|
static java.lang.String |
MQJMS_E_DELIVERY_MODE_INVALID
The delivery mode was not valid.
|
static java.lang.String |
MQJMS_E_DESERIALISE_FAILED
Unable to deserialize an object.
|
static java.lang.String |
MQJMS_E_DISCARD_FAILED
Error while discarding message.
|
static java.lang.String |
MQJMS_E_DLH_READ_FAILED
Error reading dead letter header.
|
static java.lang.String |
MQJMS_E_DLH_WRITE_FAILED
Error writing dead letter header.
|
static java.lang.String |
MQJMS_E_DLQ_FAILED
Unable to write a message to dead letter queue.
|
static java.lang.String |
MQJMS_E_EXCP_LSTNR_FAILED
ExceptionListener threw exception: {0}.
|
static java.lang.String |
MQJMS_E_IDENT_PRO_INVALID_OP
The operation is not valid for the identified producer.
|
static java.lang.String |
MQJMS_E_INTERNAL_ERROR
An internal error has occurred.
|
static java.lang.String |
MQJMS_E_INVALID_ESCAPE
An incorrect XML escape sequence detected {0}.
|
static java.lang.String |
MQJMS_E_INVALID_HEX_STRING
String is not a valid hexadecimal number - {0}.
|
static java.lang.String |
MQJMS_E_INVALID_MAP_MESSAGE
The map message has an incorrect format.
|
static java.lang.String |
MQJMS_E_INVALID_MESSAGE
Cannot transmit JMS messages which are not WebSphere MQ messages.
|
static java.lang.String |
MQJMS_E_INVALID_SESSION
Session object not valid.
|
static java.lang.String |
MQJMS_E_INVALID_STREAM_MESSAGE
The stream message has an incorrect format.
|
static java.lang.String |
MQJMS_E_INVALID_SURROGATE
An incorrect UTF-16 surrogate character detected {0}.
|
static java.lang.String |
MQJMS_E_JNDI_GENERAL_ERROR
JNDI failed due to {0}.
|
static java.lang.String |
MQJMS_E_LOG_ERROR
Failed to log error.
|
static java.lang.String |
MQJMS_E_MSG_LSTNR_FAILED
MessageListener threw: {0}.
|
static java.lang.String |
MQJMS_E_MULTICAST_HEARTBEAT_TIMEOUT
Multicast connection disconnected due to timeout.
|
static java.lang.String |
MQJMS_E_MULTICAST_LOST_MESSAGES
Lost {0} messages in reliable multicast mode.
|
static java.lang.String |
MQJMS_E_MULTICAST_NOT_AVAILABLE
Multicast connection cannot be established.
|
static java.lang.String |
MQJMS_E_MULTICAST_PORT_INVALID
Cannot connect with a specific local port for multicast.
|
static java.lang.String |
MQJMS_E_NO_BORQ
No Backout-Requeue queue defined.
|
static java.lang.String |
MQJMS_E_NO_MSG_LISTENER
No message listener.
|
static java.lang.String |
MQJMS_E_NO_SESSION
Message has no session associated with it.
|
static java.lang.String |
MQJMS_E_NO_STR_CONSTRUCTOR
There is no constructor with a String argument.
|
static java.lang.String |
MQJMS_E_NO_UTF8
Fatal error - UTF8 not supported.
|
static java.lang.String |
MQJMS_E_NO_XARESOURCE
Failed to obtain XAResource.
|
static java.lang.String |
MQJMS_E_NON_LOCAL_RXQ
Non-local WebSphere MQ queue not valid for receiving or browsing.
|
static java.lang.String |
MQJMS_E_NOT_ALLOWED_WITH_XA
Operation for an XA transacted session was not valid.
|
static java.lang.String |
MQJMS_E_NOT_IMPLEMENTED
Not implemented.
|
static java.lang.String |
MQJMS_E_NULL_CONNECTION
No valid connection available.
|
static java.lang.String |
MQJMS_E_NULL_MESSAGE
Unable to process a null message.
|
static java.lang.String |
MQJMS_E_NULL_POOL
Null ServerSessionPool has been provided.
|
static java.lang.String |
MQJMS_E_QMGR_NAME_INQUIRE_FAILED
The queue manager name could not be queried.
|
static java.lang.String |
MQJMS_E_QUEUE_NOT_LOCAL_OR_ALIAS
Specified WebSphere MQ Queue is neither a QLOCAL nor a QALIAS queue.
|
static java.lang.String |
MQJMS_E_READING_MSG
Exception occurred reading message body: {0}.
|
static java.lang.String |
MQJMS_E_RECOVER_BO_FAILED
Failed to recover: unacknowledged messages might not get redelivered.
|
static java.lang.String |
MQJMS_E_REDIRECT_FAILED
Failed to redirect message.
|
static java.lang.String |
MQJMS_E_REQUEUE_FAILED
Message requeue failed.
|
static java.lang.String |
MQJMS_E_RESOURCE_BUNDLE_NOT_FOUND
Failed to locate the resource bundle.
|
static java.lang.String |
MQJMS_E_RFH_CONTENTS_ERROR
RFH content was unrecognised or not valid.
|
static java.lang.String |
MQJMS_E_RFH_READ_FAILED
Error reading RFH.
|
static java.lang.String |
MQJMS_E_RFH_WRITE_FAILED
Error writing RFH.
|
static java.lang.String |
MQJMS_E_ROLLBACK_FAILED
Failed to roll back.
|
static java.lang.String |
MQJMS_E_S390_DOUBLE_TOO_BIG
Number outside of range for double precision
z/OS Float {0}.
|
static java.lang.String |
MQJMS_E_SECURITY_CREDS_INVALID
Security credentials cannot be specified when using WebSphere MQ bindings.
|
static java.lang.String |
MQJMS_E_SERIALISE_FAILED
Unable to serialize an object.
|
static java.lang.String |
MQJMS_E_SESSION_ASYNC
Operation cannot be performed while the session is using asynchronous delivery.
|
static java.lang.String |
MQJMS_E_SESSION_CLOSED
Session closed.
|
static java.lang.String |
MQJMS_E_SESSION_IS_TRANSACTED
The operation is not valid for a transacted session.
|
static java.lang.String |
MQJMS_E_SESSION_NOT_TRANSACTED
The operation is not valid for a non-transacted session.
|
static java.lang.String |
MQJMS_E_START_FAILED
Start failed because of {0}.
|
static java.lang.String |
MQJMS_E_SYSTEM_PROPERTY_NOT_FOUND
Failed to find the system property {0}.
|
static java.lang.String |
MQJMS_E_TMPQ_CLOSED
Temporary queue already closed or deleted.
|
static java.lang.String |
MQJMS_E_TMPQ_DEL_FAILED
Failed to delete temporary queue.
|
static java.lang.String |
MQJMS_E_TMPQ_DEL_STATIC
Cannot delete a static queue.
|
static java.lang.String |
MQJMS_E_TMPQ_FAILED
Failed to create a temporary queue from {0}.
|
static java.lang.String |
MQJMS_E_TMPQ_INUSE
Temporary queue in use.
|
static java.lang.String |
MQJMS_E_TMPT_DELETED
TemporaryTopic already deleted.
|
static java.lang.String |
MQJMS_E_TMPT_IN_USE
TemporaryTopic in use.
|
static java.lang.String |
MQJMS_E_TMPT_OUTOFSCOPE
TemporaryTopic out of scope.
|
static java.lang.String |
MQJMS_E_TRACE_FILE_NOT_FOUND
The trace file does not exist.
|
static java.lang.String |
MQJMS_E_TRACE_STREAM_ERROR
Failed to connect to Trace stream.
|
static java.lang.String |
MQJMS_E_UNIDENT_PRO_INVALID_OP
Operation not valid for unidentified producer.
|
static java.lang.String |
MQJMS_E_UNKNOWN_TARGET_CLIENT
Unknown value of target client: {0}.
|
static java.lang.String |
MQJMS_E_UNKNOWN_TRANSPORT
Unknown value of transportType: {0}.
|
static java.lang.String |
MQJMS_E_UNREC_BROKER_MESSAGE
Unrecognized message from publish / subscribe broker.
|
static java.lang.String |
MQJMS_E_UNSUPPORTED_TYPE
Unsupported property or element datatype {0}.
|
static java.lang.String |
MQJMS_ERR_QSENDER_CLOSED
QueueSender is closed.
|
static java.lang.String |
MQJMS_EXC_ENLIST_FAILED
Enlist failed.
|
static java.lang.String |
MQJMS_EXCEPTION_AUTHENTICATION_FAILED
The security authentication supplied for MQQueueManager was not valid.
|
static java.lang.String |
MQJMS_EXCEPTION_BAD_STATE_TRANSITION
Unhandled state transition from {0} to {1}.
|
static java.lang.String |
MQJMS_EXCEPTION_BAD_VALUE
The value for {0}:{1} is not valid.
|
static java.lang.String |
MQJMS_EXCEPTION_CONNECTION_CLOSED
Connection closed.
|
static java.lang.String |
MQJMS_EXCEPTION_GET_MSG_FAILED
Failed to get message from an MQQueue object.
|
static java.lang.String |
MQJMS_EXCEPTION_ILLEGAL_STATE
Method {0} has been invoked at an illegal or inappropriate time, or the
provider is not in an appropriate state for the requested operation.
|
static java.lang.String |
MQJMS_EXCEPTION_INVALID_CLIENTID
JMS client attempted to set a client ID on a connection
Explanation:
An application attempted to set the client ID property of a valid connection to
null, or attempted to set the clientId property of an invalid connection.
|
static java.lang.String |
MQJMS_EXCEPTION_INVALID_DESTINATION
Destination not understood or no longer valid.
|
static java.lang.String |
MQJMS_EXCEPTION_INVALID_SELECTOR
JMS Client has given JMS provider a message selector with incorrect syntax.
|
static java.lang.String |
MQJMS_EXCEPTION_MESSAGE_EOF
Unexpected end of stream has been reached when a StreamMessage or BytesMessage
is being read.
|
static java.lang.String |
MQJMS_EXCEPTION_MESSAGE_FORMAT
JMS Client attempts to use a data type not supported by a message or attempts
to read data in the wrong type.
|
static java.lang.String |
MQJMS_EXCEPTION_MQ_NULL_Q
MQQueue reference is null.
|
static java.lang.String |
MQJMS_EXCEPTION_MQ_NULL_QMGR
MQQueueManager reference is null.
|
static java.lang.String |
MQJMS_EXCEPTION_MQ_Q_CLOSE_FAILED
Failed to close WebSphere MQ queue.
|
static java.lang.String |
MQJMS_EXCEPTION_MQ_Q_INQUIRE_FAILED
Failed to inquire an MQQueue object depth.
|
static java.lang.String |
MQJMS_EXCEPTION_MQ_Q_OPEN_FAILED
Failed to open an MQQueue object.
|
static java.lang.String |
MQJMS_EXCEPTION_MQ_QM_COMMIT_FAILED
MQQueueManager.commit() failed.
|
static java.lang.String |
MQJMS_EXCEPTION_MQ_UNKNOWN_DEFTYPE
Unknown value for an MQQueue object definitionType: {0}.
|
static java.lang.String |
MQJMS_EXCEPTION_MSG_CREATE_ERROR
Failed to create JMS message.
|
static java.lang.String |
MQJMS_EXCEPTION_NULL_ELEMENT_NAME
Element name is null.
|
static java.lang.String |
MQJMS_EXCEPTION_NULL_PROPERTY_NAME
Property name is null.
|
static java.lang.String |
MQJMS_EXCEPTION_PUT_MSG_FAILED
Failed to send message to an MQQueue object.
|
static java.lang.String |
MQJMS_EXCEPTION_QMDISC_FAILED
Failed to disconnect queue manager.
|
static java.lang.String |
MQJMS_EXCEPTION_QMGR_FAILED
Failed to create an MQQueueManager for {0}.
|
static java.lang.String |
MQJMS_EXCEPTION_RESOURCE_ALLOCATION
JMS Provider is unable to allocate the resources required for a method.
|
static java.lang.String |
MQJMS_EXCEPTION_SOME_PROBLEM
WebSphere MQ problem: {0}.
|
static java.lang.String |
MQJMS_EXCEPTION_TRANSACTION_IN_PROGRESS
Operation cannot be performed while a transaction is in progress.
|
static java.lang.String |
MQJMS_EXCEPTION_TRANSACTION_ROLLED_BACK
Call to Session.commit resulted in a rollback of the current transaction.
|
static java.lang.String |
MQJMS_EXCEPTION_UNEXPECTED_ERROR
An internal error has occurred. |
static java.lang.String |
MQJMS_EXCEPTION_UNKNOWN_ACK_MODE
Unknown acknowledgement mode {0}.
|
static java.lang.String |
MQJMS_EXCEPTION_XACLOSE_FAILED
XACLOSE failed.
|
static java.lang.String |
MQJMS_LOCAL_XA_CLASH
Local transactions not allowed with XA sessions.
|
static java.lang.String |
MQJMS_MESSAGECONSUMER_CLOSED
Message Consumer is closed.
|
static java.lang.String |
MQJMS_MESSAGEPRODUCER_CLOSED
Message Producer is closed.
|
static java.lang.String |
MQJMS_MSEL_AND_BVER_INCOMPATIBLE
Broker message selection is only valid when using WebSphere MQ Integrator broker.
|
static java.lang.String |
MQJMS_PS_COMMAND_MSG_BUILD
Failed to build command {0}.
|
static java.lang.String |
MQJMS_PS_COMMAND_MSG_FAILED
Failed to publish command to WebSphere MQ queue.
|
static java.lang.String |
MQJMS_PS_GENERAL_ERROR
Publish/Subscribe failed due to {0}.
|
static java.lang.String |
MQJMS_PS_INCORRECT_SUBSTORE
Incorrect subscription store type.
|
static java.lang.String |
MQJMS_PS_INVALID_SUBQ_PREFIX
Subscriber queue prefix was not valid: {0}.
|
static java.lang.String |
MQJMS_PS_NULL_CLIENTID
The use of an uninitialized client ID is not possible.
|
static java.lang.String |
MQJMS_PS_NULL_NAME
The use of a null name is not possible.
|
static java.lang.String |
MQJMS_PS_PUBLISH_MSG_BUILD
Failed to build publish message.
|
static java.lang.String |
MQJMS_PS_PUBLISH_MSG_FAILED
Failed to publish message to WebSphere MQ queue.
|
static java.lang.String |
MQJMS_PS_STORE_ADMIN_ENTRY
Failed to store admininstration entry.
|
static java.lang.String |
MQJMS_PS_SUB_ACTIVE
Subscription has an active TopicSubscriber.
|
static java.lang.String |
MQJMS_PS_SUB_Q_DELETE_FAILED
Failed to delete subscriber queue {0}.
|
static java.lang.String |
MQJMS_PS_SUB_Q_OPEN_FAILED
Failed to open subscriber queue {0}.
|
static java.lang.String |
MQJMS_PS_SUBQ_REQUEUE
Durable re-subscribe must use same subscriber queue; specified: {0}, original: {1}.
|
static java.lang.String |
MQJMS_PS_SUBSTORE_NOT_SUPPORTED
Subscription store type not supported by queue manager.
|
static java.lang.String |
MQJMS_PS_TOPIC_NULL
Topic reference is null.
|
static java.lang.String |
MQJMS_PS_UNKNOWN_DS
Unknown durable subscription {0}.
|
static java.lang.String |
MQJMS_PS_WRONG_SUBSCRIPTION_TYPE
Incorrect subscription type for this subscription store.
|
static java.lang.String |
MQJMS_PUBLISHER_CLOSED
TopicPublisher is closed.
|
static java.lang.String |
MQJMS_QRECEIVER_CLOSED
QueueReceiver is closed.
|
static java.lang.String |
MQJMS_SUBSCRIBER_CLOSED
TopicSubscriber is closed.
|
static java.lang.String |
MQJMS_UTIL_PS_NO_BRK_Q
Unable to access the broker control queue on the queue manager.
|
static java.lang.String |
MQJMS_UTIL_PS_NO_BROKER
No broker response.
|
static java.lang.String |
MQJMS_UTIL_PS_NO_MSG
The broker appears to be running, but the message did not arrive.
|
static java.lang.String |
MQJMS_UTIL_PS_NO_QM
Unable to connect to queue manager.
|
Methods inherited from class java.lang.Object |
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
MQJMS_EXCEPTION_ILLEGAL_STATE
public static final java.lang.String MQJMS_EXCEPTION_ILLEGAL_STATE
- Method {0} has been invoked at an illegal or inappropriate time, or the
provider is not in an appropriate state for the requested operation.
Explanation:
The normal reason for this exception is that the SSL certificate stores
have not been defined. {0} identifies the method that has caused the
problem.
User Response:
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_INVALID_CLIENTID
public static final java.lang.String MQJMS_EXCEPTION_INVALID_CLIENTID
- JMS client attempted to set a client ID on a connection
Explanation:
An application attempted to set the client ID property of a valid connection to
null, or attempted to set the clientId property of an invalid connection.
User Response:
The clientId property on a connection can only be set once, only to a non-null
value, and only before the connection is used. Ensure that the connection is
valid and that the clientId value is not null.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_INVALID_DESTINATION
public static final java.lang.String MQJMS_EXCEPTION_INVALID_DESTINATION
- Destination not understood or no longer valid.
Explanation:
The queue or topic might have become unavailable, the application might be
using an incorrect connection for the queue or topic, or the supplied
destination is not of the correct type for this method.
User Response:
Check that WebSphere MQ is still running and the queue manager is available.
Check that the right connection is being used for your queue or topic.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_INVALID_SELECTOR
public static final java.lang.String MQJMS_EXCEPTION_INVALID_SELECTOR
- JMS Client has given JMS provider a message selector with incorrect syntax.
Explanation:
The message selector string is empty or contains a value which is incorrect or has the wrong syntax.
User Response:
Check the linked WebSphere MQ exception reason and completion codes for more information.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MESSAGE_EOF
public static final java.lang.String MQJMS_EXCEPTION_MESSAGE_EOF
- Unexpected end of stream has been reached when a StreamMessage or BytesMessage
is being read.
Explanation:
The byte stream being read is shorter than the buffer supplied.
This can also be caused by receiving a corrupt StreamMessage or BytesMessage.
User Response:
Check the length of buffer supplied. Check system event logs for more information.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MESSAGE_FORMAT
public static final java.lang.String MQJMS_EXCEPTION_MESSAGE_FORMAT
- JMS Client attempts to use a data type not supported by a message or attempts
to read data in the wrong type.
Explanation:
Wrong data types used to read message property types.
User Response:
Check that the message received and the properties to be read are of the type
expected.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_RESOURCE_ALLOCATION
public static final java.lang.String MQJMS_EXCEPTION_RESOURCE_ALLOCATION
- JMS Provider is unable to allocate the resources required for a method.
Explanation:
Machine resources might be overloaded, the linked exception might
give further information.
User Response:
Check system resources and load.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_TRANSACTION_IN_PROGRESS
public static final java.lang.String MQJMS_EXCEPTION_TRANSACTION_IN_PROGRESS
- Operation cannot be performed while a transaction is in progress.
User Response:
Wait for the current transaction to complete.
See the linked WebSphere MQ exception for further information.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_TRANSACTION_ROLLED_BACK
public static final java.lang.String MQJMS_EXCEPTION_TRANSACTION_ROLLED_BACK
- Call to Session.commit resulted in a rollback of the current transaction.
Explanation:
The transaction failed and was rolled back to a safe state.
See the linked exception for more information.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MSG_CREATE_ERROR
public static final java.lang.String MQJMS_EXCEPTION_MSG_CREATE_ERROR
- Failed to create JMS message.
Explanation:
The wrong message type or properties were specified when creating a base message.
User Response:
Check the linked WebSphere MQ exception Reason and Completion code for
more information.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_UNKNOWN_ACK_MODE
public static final java.lang.String MQJMS_EXCEPTION_UNKNOWN_ACK_MODE
- Unknown acknowledgement mode {0}.
Explanation:
Incorrect or no parameter {0} set for acknowledgement mode on the session.
User Response:
See MQSession
for the possible values
for the acknowledgement mode.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_CONNECTION_CLOSED
public static final java.lang.String MQJMS_EXCEPTION_CONNECTION_CLOSED
- Connection closed.
Explanation:
An operation such as start() or stop() has been called on a connection
that is already closed.
User Response:
Ensure that the connection is open before performing any operation.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_BAD_STATE_TRANSITION
public static final java.lang.String MQJMS_EXCEPTION_BAD_STATE_TRANSITION
- Unhandled state transition from {0} to {1}.
Explanation:
The state transition is not valid, see log for more information.
User Response:
Check the linked WebSphere MQ exception reason and completion code.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_BAD_VALUE
public static final java.lang.String MQJMS_EXCEPTION_BAD_VALUE
- The value for {0}:{1} is not valid.
Explanation:
The value {1} for property {0} is not correct.
User Response:
Check the linked WebSphere MQ exception reason and completion code.
- See Also:
- Constant Field Values
MQJMS_E_BAD_EXIT_CLASS
public static final java.lang.String MQJMS_E_BAD_EXIT_CLASS
- Failed to create instance of exit class {0}.
User Response:
Check that the supplied String matches the fully-qualified name of the
exit class, and that the exit implements the correct interface.
- See Also:
- Constant Field Values
MQJMS_E_UNKNOWN_TRANSPORT
public static final java.lang.String MQJMS_E_UNKNOWN_TRANSPORT
- Unknown value of transportType: {0}.
Explanation:
The value given for transportType could not be used. {0} shows the incorrect
value.
- See Also:
- Constant Field Values
MQJMS_E_NO_STR_CONSTRUCTOR
public static final java.lang.String MQJMS_E_NO_STR_CONSTRUCTOR
- There is no constructor with a String argument.
Explanation:
User exits must provide a constructor that takes a single String. No such
constructor was found in the specified exit.
User Response:
Ensure that the user exit provides a suitable constructor.
- See Also:
- Constant Field Values
MQJMS_E_NOT_IMPLEMENTED
public static final java.lang.String MQJMS_E_NOT_IMPLEMENTED
- Not implemented.
Explanation:
The function requested is not implemented.
This can be thrown by message acknowledgement, if the session
or acknowledgement parameters are not valid or are incorrect.
- See Also:
- Constant Field Values
MQJMS_E_SECURITY_CREDS_INVALID
public static final java.lang.String MQJMS_E_SECURITY_CREDS_INVALID
- Security credentials cannot be specified when using WebSphere MQ bindings.
Explanation:
The RRS queue does not support a client connection, and bindings connections
do not support the specification of security credentials.
User Response:
Ensure that you do not try to specify security credentials when using a
bindings connection.
- See Also:
- Constant Field Values
MQJMS_E_NO_MSG_LISTENER
public static final java.lang.String MQJMS_E_NO_MSG_LISTENER
- No message listener.
Explanation:
The message listener has stopped or was never started.
User Response:
Restart the message listener and retry.
- See Also:
- Constant Field Values
MQJMS_E_SESSION_ASYNC
public static final java.lang.String MQJMS_E_SESSION_ASYNC
- Operation cannot be performed while the session is using asynchronous delivery.
Explanation:
You cannot perform the requested operation while the session is actively
using asynchronous delivery mode.
User Response:
- See Also:
- Constant Field Values
MQJMS_E_IDENT_PRO_INVALID_OP
public static final java.lang.String MQJMS_E_IDENT_PRO_INVALID_OP
- The operation is not valid for the identified producer.
Explanation:
The QueueSender.send method has been used on an identified
QueueSender, which contradicts the JMS specification.
User Response:
For further information see the
MQQueueSender
class.
- See Also:
- Constant Field Values
MQJMS_E_UNKNOWN_TARGET_CLIENT
public static final java.lang.String MQJMS_E_UNKNOWN_TARGET_CLIENT
- Unknown value of target client: {0}.
Explanation:
The value for the targetClient property set by the application for this
destination is not recognized by WebSphere MQ JMS.
User Response:
- See Also:
- Constant Field Values
MQJMS_E_INTERNAL_ERROR
public static final java.lang.String MQJMS_E_INTERNAL_ERROR
- An internal error has occurred.
Contact your system administrator. Detail: {0}.
User Response:
Check the linked WebSphere MQ exception reason and completion code for
more information.
- See Also:
- Constant Field Values
MQJMS_E_NON_LOCAL_RXQ
public static final java.lang.String MQJMS_E_NON_LOCAL_RXQ
- Non-local WebSphere MQ queue not valid for receiving or browsing.
Explanation:
An attempt was made to perform an inappropriate operation on a non-local queue.
User Response:
Check the queue properties.
- See Also:
- Constant Field Values
MQJMS_E_NULL_CONNECTION
public static final java.lang.String MQJMS_E_NULL_CONNECTION
- No valid connection available.
Explanation:
The queue is busy, there are network problems, or a connection has
not been defined for the object.
User Response:
Create a valid connection for this operation.
- See Also:
- Constant Field Values
MQJMS_E_SESSION_NOT_TRANSACTED
public static final java.lang.String MQJMS_E_SESSION_NOT_TRANSACTED
- The operation is not valid for a non-transacted session.
Explanation:
Commit is not allowed on a session that is not transacted.
User Response:
Check the linked IllegalStateException for more information.
- See Also:
MQSession
,
Constant Field Values
MQJMS_E_SESSION_IS_TRANSACTED
public static final java.lang.String MQJMS_E_SESSION_IS_TRANSACTED
- The operation is not valid for a transacted session.
Explanation:
The acknowledgement mode is not valid for a transacted session.
Acknowledge and Recover are not valid operations in transacted sessions.
User Response:
- See Also:
MQSession
,
Constant Field Values
MQJMS_E_RECOVER_BO_FAILED
public static final java.lang.String MQJMS_E_RECOVER_BO_FAILED
- Failed to recover: unacknowledged messages might not get redelivered.
Explanation:
The system was unable to recover from a failure.
User Response:
Check the linked exception to determine why the call to recover failed.
- See Also:
- Constant Field Values
MQJMS_E_REDIRECT_FAILED
public static final java.lang.String MQJMS_E_REDIRECT_FAILED
- Failed to redirect message.
Explanation:
When performing asynchronous delivery, WebSphere MQ JMS attempted to
redirect the message to the backout queue. No backout queue was defined.
User Response:
Ensure that the backout queue is defined.
Also, investigate why WebSphere MQ JMS was attempting to redirect the message.
It might do so in response to a failing MessageListener implementation.
- See Also:
- Constant Field Values
MQJMS_E_ROLLBACK_FAILED
public static final java.lang.String MQJMS_E_ROLLBACK_FAILED
- Failed to roll back.
Explanation:
The system was unable to roll back to a safe state.
User Response:
Check the linked WebSphere MQ Exception reason and completion codes for further
information.
- See Also:
- Constant Field Values
MQJMS_E_SESSION_CLOSED
public static final java.lang.String MQJMS_E_SESSION_CLOSED
- Session closed.
Explanation:
The session was closed. It either timed out, or it was closed explicitly, or it was
closed because the connection or the queue
manager was closed.
User Response:
Restart the session, and check all required resources are available.
- See Also:
- Constant Field Values
MQJMS_E_BROWSE_MSG_FAILED
public static final java.lang.String MQJMS_E_BROWSE_MSG_FAILED
- Failed to browse message.
Explanation:
No message was available for browsing, possibly because there was no message on the Queue.
User Response:
Check the linked WebSphere MQ Exception reason and completion codes.
Check that a message is available for browsing.
- See Also:
- Constant Field Values
MQJMS_E_EXCP_LSTNR_FAILED
public static final java.lang.String MQJMS_E_EXCP_LSTNR_FAILED
- ExceptionListener threw exception: {0}.
User Response:
Check linked exceptions for further information.
- See Also:
- Constant Field Values
MQJMS_E_BAD_DEST_STR
public static final java.lang.String MQJMS_E_BAD_DEST_STR
- Failed to reconstitute destination from {0}.
Explanation:
A message has been received which contains destination information in
the RFH2 header which is not valid.
User Response:
Ensure that any messages being sent by non-JMS applications have correctly
formatted destination information. In the case of RFH2 headers, pay special
attention to the Rto (reply to) and Dst (destination) elements
of the XML portion of the header. Valid destination strings must start
either queue or topic.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_NULL_ELEMENT_NAME
public static final java.lang.String MQJMS_EXCEPTION_NULL_ELEMENT_NAME
- Element name is null.
Explanation:
A null name string was passed to one of the get value by name methods
of MapMessage.
User Response:
Ensure that all name strings being used to retrieve values are not null.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_NULL_PROPERTY_NAME
public static final java.lang.String MQJMS_EXCEPTION_NULL_PROPERTY_NAME
- Property name is null.
Explanation:
The itemExists method of MapMessage was invoked with a null item name,
or a null name string was used as an argument to a method which retrieves
property values by name from a JMS message.
User Response:
Ensure that the name strings indicated do not have null values.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_UNEXPECTED_ERROR
public static final java.lang.String MQJMS_EXCEPTION_UNEXPECTED_ERROR
- An internal error has occurred. Contact your system administrator.
Explanation:
Internal Error.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_E_CLOSE_FAILED
public static final java.lang.String MQJMS_E_CLOSE_FAILED
- Close failed because of {0}.
Explanation:
Internal Error. {0} indicates the reason for the error.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_E_START_FAILED
public static final java.lang.String MQJMS_E_START_FAILED
- Start failed because of {0}.
Explanation:
{0} indicates why the session failed to start.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_E_MSG_LSTNR_FAILED
public static final java.lang.String MQJMS_E_MSG_LSTNR_FAILED
- MessageListener threw: {0}.
Explanation:
When performing asynchronous delivery, the onMessage method of the
application's MessageListener failed with a Throwable.
WebSphere MQ JMS tries to redeliver or requeue the message.
User Response:
Do not throw Throwables from the onMessage method of a MessageListener.
- See Also:
- Constant Field Values
MQJMS_E_INVALID_MESSAGE
public static final java.lang.String MQJMS_E_INVALID_MESSAGE
- Cannot transmit JMS messages which are not WebSphere MQ messages.
Explanation:
Wrong message type used. This might be an internal problem.
User Response:
Check the message type.
Contact your IBM representative if there appears to be an internal error.
- See Also:
- Constant Field Values
MQJMS_E_RESOURCE_BUNDLE_NOT_FOUND
public static final java.lang.String MQJMS_E_RESOURCE_BUNDLE_NOT_FOUND
- Failed to locate the resource bundle.
Explanation:
The resource bundle is either not present or not in the application's classpath.
User Response:
Check that the classpath includes the location of property files.
- See Also:
- Constant Field Values
MQJMS_E_LOG_ERROR
public static final java.lang.String MQJMS_E_LOG_ERROR
- Failed to log error.
Explanation:
Log settings might be incorrect. See the linked LogException.
User Response:
Check that the log settings are correct.
- See Also:
- Constant Field Values
MQJMS_E_TRACE_FILE_NOT_FOUND
public static final java.lang.String MQJMS_E_TRACE_FILE_NOT_FOUND
- The trace file does not exist.
Explanation:
Trace settings might be incorrect.
User Response:
Check trace settings and trace file existence.
- See Also:
- Constant Field Values
MQJMS_E_TRACE_STREAM_ERROR
public static final java.lang.String MQJMS_E_TRACE_STREAM_ERROR
- Failed to connect to Trace stream.
Explanation:
Trace settings may be incorrect.
User Response:
- See Also:
- Constant Field Values
MQJMS_E_SYSTEM_PROPERTY_NOT_FOUND
public static final java.lang.String MQJMS_E_SYSTEM_PROPERTY_NOT_FOUND
- Failed to find the system property {0}.
Explanation:
The system property specified in {0} does not exist or was not found in
the application's classpath.
User Response:
Check the classpath settings and the product installation.
- See Also:
- Constant Field Values
MQJMS_E_DELIVERY_MODE_INVALID
public static final java.lang.String MQJMS_E_DELIVERY_MODE_INVALID
- The delivery mode was not valid.
Explanation:
Either the value for the delivery mode of a message producer was incorrectly specified,
or the mode value was specified incorrectly when publishing a message.
User Response:
Check to ensure that the value specified is a valid enumeration for delivery mode.
- See Also:
- Constant Field Values
MQJMS_E_JNDI_GENERAL_ERROR
public static final java.lang.String MQJMS_E_JNDI_GENERAL_ERROR
- JNDI failed due to {0}.
Explanation:
{0} gives further information.
User Response:
Check settings for LDAP, JNDI, and in the JMSAdmin.config file.
- See Also:
- Constant Field Values
MQJMS_E_INVALID_HEX_STRING
public static final java.lang.String MQJMS_E_INVALID_HEX_STRING
- String is not a valid hexadecimal number - {0}.
Explanation:
Either an attempt was made to specify a group ID or correlation ID which starts
with the prefix ID but is not followed by a well-formed hexadecimal value,
or an attempt was made to receive a message which contains an RFH2 property
of type bin.hex that does not have a well-formed hexadecimal value.
User Response:
Ensure that a valid hexadecimal value always follows the
ID prefix when
setting group ID or correlation ID values.
Ensure that any RFH2 headers generated by non-JMS applications are well-formed.
- See Also:
- Constant Field Values
MQJMS_E_S390_DOUBLE_TOO_BIG
public static final java.lang.String MQJMS_E_S390_DOUBLE_TOO_BIG
- Number outside of range for double precision
z/OS Float {0}.
Explanation:
This is a z/OS
specific error.
- See Also:
- Constant Field Values
MQJMS_E_BAD_CCSID
public static final java.lang.String MQJMS_E_BAD_CCSID
- The character set {0} is not supported.
Explanation:
An attempt was made to send or receive a map message, stream message or text message whose
body is encoded using a character set not supported by the JVM.
In the case of text messages, this exception might be thrown when the body of the message is
first queried, rather than at receive time.
User Response:
Only encode a message using a character set known to be available to the receiving
application.
- See Also:
- Constant Field Values
MQJMS_E_INVALID_MAP_MESSAGE
public static final java.lang.String MQJMS_E_INVALID_MAP_MESSAGE
- The map message has an incorrect format.
Explanation:
A map message was received, but its RFH2 header information is badly formatted.
User Response:
Ensure any non-JMS applications are building well-formed RFH2 header information
for inclusion in map messages.
- See Also:
- Constant Field Values
MQJMS_E_INVALID_STREAM_MESSAGE
public static final java.lang.String MQJMS_E_INVALID_STREAM_MESSAGE
- The stream message has an incorrect format.
Explanation:
A stream message was received, but its RFH2 header information is badly formatted.
User Response:
Ensure that any non-JMS applications are building well-formed RFH2 header
information for inclusion in stream messages.
- See Also:
- Constant Field Values
MQJMS_E_BYTE_TO_STRING
public static final java.lang.String MQJMS_E_BYTE_TO_STRING
- The JMS client attempted to convert a byte array to a String.
Explanation:
Attempted to receive a byte array from a stream message using the
readString method.
User Response:
Either use the appropriate method to receive the data, or format the
data placed into the stream message correctly.
- See Also:
- Constant Field Values
MQJMS_E_BAD_RFH2
public static final java.lang.String MQJMS_E_BAD_RFH2
- The MQRFH2 header has an incorrect format.
Explanation:
Received a message with a badly formed RFH2 header.
User Response:
Ensure that any non-JMS applications building messages with RFH2 headers create
well-formed RFH2 headers.
- See Also:
- Constant Field Values
MQJMS_E_INVALID_SURROGATE
public static final java.lang.String MQJMS_E_INVALID_SURROGATE
- An incorrect UTF-16 surrogate character detected {0}.
Explanation:
A UTF-16 surrogate character was encountered which is not valid as part of a
topic name or RFH2 property.
User Response:
Ensure that, when specifying UTF-16, topic names or RFH2 properties
are well-formed.
- See Also:
- Constant Field Values
MQJMS_E_INVALID_ESCAPE
public static final java.lang.String MQJMS_E_INVALID_ESCAPE
- An incorrect XML escape sequence detected {0}.
Explanation:
An XML escape sequence was encountered which is not valid in the RFH2 header
of a received message.
User Response:
Ensure that only valid XML escape sequences are placed into any RFH2
headers built by non-JMS applications.
- See Also:
- Constant Field Values
MQJMS_E_BAD_TYPE
public static final java.lang.String MQJMS_E_BAD_TYPE
- The property or element in the message has an incompatible datatype {0}.
Explanation:
Attempted to retrieve a property from a JMS message using a accessor
method which specifies an incompatible type. For example, attempting to
retrieve an integer property using the getBooleanProperty method.
User Response:
Use an accessor method defined by the JMS specification as being able to
retrieve property values of the required type.
- See Also:
- Constant Field Values
MQJMS_E_UNSUPPORTED_TYPE
public static final java.lang.String MQJMS_E_UNSUPPORTED_TYPE
- Unsupported property or element datatype {0}.
Explanation:
This error is caused by one of the following:
- Attempting to set a property of a JMS message using an object which is not one of the
supported types.
- Attempting to set or receive a message whose RFH2 contains an element representing a
property which does not have a valid type associated with it.
User Response:
Ensure that when setting message properties, you use a valid JMS object type.
If this exception occurs when receiving a message containing an RFH2 header sent by a
non-JMS application, ensure that the RFH2 header is well-formed.
- See Also:
- Constant Field Values
MQJMS_E_NO_SESSION
public static final java.lang.String MQJMS_E_NO_SESSION
- Message has no session associated with it.
Explanation:
An attempt was made to acknowledge a message on a session which is not
in an open state.
User Response:
Ensure that the session associated with the message has been correctly opened.
Check that the session has not been closed.
- See Also:
- Constant Field Values
MQJMS_E_BAD_PROPERTY_NAME
public static final java.lang.String MQJMS_E_BAD_PROPERTY_NAME
- Invalid message property name: {0}.
Explanation:
Attempted to set a property that either does not have a valid property name, or cannot be set.
User Response:
Ensure that the property name used is a valid property name in accordance with the JMS
specification.
If the property name refers to a JMS or provider-specific extension property, ensure that
this property can be set.
- See Also:
- Constant Field Values
MQJMS_E_NO_UTF8
public static final java.lang.String MQJMS_E_NO_UTF8
- Fatal error - UTF8 not supported.
Explanation:
The Java runtime environment you are using does not support the UTF-8 character encoding.
JMS requires support for this encoding to perform some operations.
User Response:
Consult the documentation and or provider of your Java runtime environment to determine
how to obtain support for the UTF-8 character encoding.
- See Also:
- Constant Field Values
MQJMS_E_SERIALISE_FAILED
public static final java.lang.String MQJMS_E_SERIALISE_FAILED
- Unable to serialize an object.
Explanation:
An attempt has been made to serialize an ObjectMessage which contains a non-serializable
object.
User Response:
Ensure that ObjectMessages only contain serializable objects.
If the object placed inside an ObjectMessage references other objects, these must also
be serializable.
- See Also:
- Constant Field Values
MQJMS_E_DESERIALISE_FAILED
public static final java.lang.String MQJMS_E_DESERIALISE_FAILED
- Unable to deserialize an object.
Explanation:
Deserialization of an ObjectMessage failed.
User Response:
Ensure that the ObjectMessage being received contains valid data.
Ensure that the class files representing object data contained within the ObjectMessage
are present on the machine deserializing the ObjectMessage.
If the object contained within the ObjectMessage references other objects, ensure that
these class files are also present.
- See Also:
- Constant Field Values
MQJMS_E_BAD_ELEMENT_NAME
public static final java.lang.String MQJMS_E_BAD_ELEMENT_NAME
- Message element name: {0} is not valid.
Explanation:
Attempted to set a message property using either a property name which is not valid, or the name of
a property which cannot have its value set.
User Response:
Ensure that the property name specified conforms to the JMS specification.
If the property name supplied is that of a JMS property, or a vendor specific extension,
ensure that this property name can be set.
- See Also:
- Constant Field Values
MQJMS_E_BAD_TIMEOUT
public static final java.lang.String MQJMS_E_BAD_TIMEOUT
- Timeout not valid for WebSphere MQ.
Explanation:
An attempt was made to invoke the receive method on either a QueueReceiver or TopicSubscriber
method, specifying a long timeout value which is not valid.
User Response:
Ensure the timeout value specified is not negative and not greater than the value of
Integer.MAX_VALUE.
- See Also:
- Constant Field Values
MQJMS_E_NO_XARESOURCE
public static final java.lang.String MQJMS_E_NO_XARESOURCE
- Failed to obtain XAResource.
Explanation:
JMS failed to create an XA Queue resource due to an error.
User Response:
See the linked XAException for more information.
- See Also:
- Constant Field Values
MQJMS_E_NOT_ALLOWED_WITH_XA
public static final java.lang.String MQJMS_E_NOT_ALLOWED_WITH_XA
- Operation for an XA transacted session was not valid.
Explanation:
The acknowledgement mode for a transacted session was not valid.
Acknowledge and Recover are not valid operations in transacted sessions.
User Response:
- See Also:
MQXASession
,
Constant Field Values
MQJMS_E_QMGR_NAME_INQUIRE_FAILED
public static final java.lang.String MQJMS_E_QMGR_NAME_INQUIRE_FAILED
- The queue manager name could not be queried.
Explanation:
In createConnectionConsumer() or createDurableConnectionConsumer(), JMS could not determine
the name of the queue manager.
User Response:
Check your queue manager error logs for problems which may cause this.
If there are no other error conditions, contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_E_QUEUE_NOT_LOCAL_OR_ALIAS
public static final java.lang.String MQJMS_E_QUEUE_NOT_LOCAL_OR_ALIAS
- Specified WebSphere MQ Queue is neither a QLOCAL nor a QALIAS queue.
Explanation:
createConnectionConsumer() was called, but a queue of the wrong type was specified.
Only QALIAS and QLOCAL queues can be used with the ConnectionConsumer feature.
User Response:
Specify a queue of the correct type.
- See Also:
- Constant Field Values
MQJMS_E_NULL_MESSAGE
public static final java.lang.String MQJMS_E_NULL_MESSAGE
- Unable to process a null message.
Explanation:
Internal error in WebSphere MQ JMS.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_E_DLH_WRITE_FAILED
public static final java.lang.String MQJMS_E_DLH_WRITE_FAILED
- Error writing dead letter header.
Explanation:
JMS attempted to requeue a message to the dead letter queue, but could
not construct a dead letter header.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_E_DLH_READ_FAILED
public static final java.lang.String MQJMS_E_DLH_READ_FAILED
- Error reading dead letter header.
Explanation:
JMS attempted to interpret a message with a dead letter header, but encountered a problem.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_E_CONN_DEST_MISMATCH
public static final java.lang.String MQJMS_E_CONN_DEST_MISMATCH
- Connection and Destination mismatch.
Explanation:
An operation was requested, but the Destination class is incompatible with
the Connection class. Topics cannot be used with QueueConnections and Queues
cannot be used with TopicConnections.
User Response:
Supply a suitable Destination. If this error represents an internal error condition
in JMS contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_E_INVALID_SESSION
public static final java.lang.String MQJMS_E_INVALID_SESSION
- Session object not valid.
Explanation:
The JMS ConnectionConsumer feature attempted to deliver a batch of messages
to a Session. However, the Session contained in the ServerSession object
returned by the ServerSessionPool was not a WebSphere MQ JMS Session.
User Response:
This is an error in the ServerSessionPool.
If you have supplied a ServerSessionPool, check its behavior. In a J2EE
application server, this might represent an error in the application server;
in which case, refer to your application server's documentation.
- See Also:
- Constant Field Values
MQJMS_E_DLQ_FAILED
public static final java.lang.String MQJMS_E_DLQ_FAILED
- Unable to write a message to dead letter queue.
Explanation:
JMS attempted to requeue a message to the dead letter queue, but failed.
User Response:
Use the linked exception to determine the cause of this error.
If there is no linked exception, check that the queue manager has a defined a dead letter queue.
Once JMS has sent a message to the dead letter queue, the reason code stored in the
message's DLH can be used to determine why the message was sent there.
- See Also:
- Constant Field Values
MQJMS_E_NO_BORQ
public static final java.lang.String MQJMS_E_NO_BORQ
- No Backout-Requeue queue defined.
Explanation:
JMS encountered a message which has been backed out more than the queue's
Backout Threshold, but the queue does not have a Backout-Requeue
queue defined.
User Response:
Define a Backout-Requeue queue for the queue, or set the Backout Threshold
to zero to disable poison message handling.
Investigate the repeated backouts.
- See Also:
- Constant Field Values
MQJMS_E_REQUEUE_FAILED
public static final java.lang.String MQJMS_E_REQUEUE_FAILED
- Message requeue failed.
Explanation:
JMS found an error when requeuing a message which has been backed out
more than the queue's Backout Threshold.
User Response:
Use the linked exception to determine the cause of this error.
Investigate the repeated backouts.
- See Also:
- Constant Field Values
MQJMS_E_DISCARD_FAILED
public static final java.lang.String MQJMS_E_DISCARD_FAILED
- Error while discarding message.
Explanation:
JMS encountered an error while discarding a message, or while generating an exception report
for a message to be discarded.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_E_BATCH_SIZE
public static final java.lang.String MQJMS_E_BATCH_SIZE
- Incorrect message batch size (must be greater than zero).
Explanation:
An incorrect batch size parameter was passed to createConnectionConsumer() or
createDurableConnectionConsumer().
User Response:
Set a batch size greater than zero.
In a J2EE application server, this may represent an error in the application server.
Refer to your application server's documentation.
- See Also:
- Constant Field Values
MQJMS_E_NULL_POOL
public static final java.lang.String MQJMS_E_NULL_POOL
- Null ServerSessionPool has been provided.
Explanation:
The ServerSessionPool specified on createConnectionConsumer() or
createDurableConnectionConsumer() was null.
User Response:
Set an appropriate ServerSessionPool.
In a J2EE application server, this may represent an error in the application server.
Refer to your application server's documentation.
- See Also:
- Constant Field Values
MQJMS_E_RFH_WRITE_FAILED
public static final java.lang.String MQJMS_E_RFH_WRITE_FAILED
- Error writing RFH.
Explanation:
JMS attempted to construct an RFH message header, but encountered an error.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_E_RFH_READ_FAILED
public static final java.lang.String MQJMS_E_RFH_READ_FAILED
- Error reading RFH.
Explanation:
JMS encountered an error while parsing an RFH message header.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_E_RFH_CONTENTS_ERROR
public static final java.lang.String MQJMS_E_RFH_CONTENTS_ERROR
- RFH content was unrecognised or not valid.
Explanation:
JMS expected to find an RFH message header, but found it to be missing,
malformed or lacking required data.
User Response:
Investigate the source of the message.
If this represents an internal error condition in JMS,
contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_E_CC_MIXED_DOMAIN
public static final java.lang.String MQJMS_E_CC_MIXED_DOMAIN
- Mixed-domain consumers acting on the same input is forbidden.
Explanation:
A point-to-point ConnectionConsumer is using the subscriber queue of
a publish/subscribe ConnectionConsumer.
User Response:
Do not attempt to access subscriber queues using the point-to-point
ConnectionConsumer facilities of JMS. Check your TopicConnectionFactory
and Topic objects to make sure they are not using a QLOCAL
intended for use by point-to-point applications as a subscriber queue.
- See Also:
- Constant Field Values
MQJMS_E_READING_MSG
public static final java.lang.String MQJMS_E_READING_MSG
- Exception occurred reading message body: {0}.
Explanation:
JMS encountered an exception while reading data from a message.
The message being read is likely to be a response message from the
publish/subscribe broker.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_E_UNIDENT_PRO_INVALID_OP
public static final java.lang.String MQJMS_E_UNIDENT_PRO_INVALID_OP
- Operation not valid for unidentified producer.
Explanation:
An attempt was made to send a message from an unidentified
MessageProducer without specifying a Destination to send the message to.
User Response:
Ensure that either an indentified producer is used (that is, a Destination was
supplied when the producer was created), or specify a Destination when the
send method is invoked.
- See Also:
- Constant Field Values
MQJMS_E_MULTICAST_NOT_AVAILABLE
public static final java.lang.String MQJMS_E_MULTICAST_NOT_AVAILABLE
- Multicast connection cannot be established.
Explanation:
Multicast is enabled, but a multicast exception could not be established and
the application specified that fallback to unicast is disallowed.
User Response:
Check the connection parameters and check that the broker is still running.
- See Also:
- Constant Field Values
MQJMS_E_MULTICAST_LOST_MESSAGES
public static final java.lang.String MQJMS_E_MULTICAST_LOST_MESSAGES
- Lost {0} messages in reliable multicast mode.
Explanation:
A MulticastPacketLossException is thrown if a multicast receiver
detects lost messages, and the messages cannot be retransmitted
* because they have been purged from the brokers's buffer.
User Response:
Increase the Broker Minimal History Size and/or Broker History
Cleaning Time to give the client more time to request retransmission
of lost messages. See the Broker documentation for details of how to
do this.
- See Also:
- Constant Field Values
MQJMS_E_MULTICAST_HEARTBEAT_TIMEOUT
public static final java.lang.String MQJMS_E_MULTICAST_HEARTBEAT_TIMEOUT
- Multicast connection disconnected due to timeout.
Explanation:
No heartbeat packet was received when expected. There has probably been a
transmitter failure or a network failure.
User Response:
Check for network problems and check the broker is still running. If the network
load is high, consider increasing the heartbeat interval.
- See Also:
- Constant Field Values
MQJMS_E_MULTICAST_PORT_INVALID
public static final java.lang.String MQJMS_E_MULTICAST_PORT_INVALID
- Cannot connect with a specific local port for multicast.
Explanation:
A port number was specified. This is not valid for multicast.
User Response:
Check the String supplied to com.ibm.mq.jms.MQConnectionFactory.setLocalAddress(String)
is valid for multicast.
- See Also:
- Constant Field Values
MQJMS_DIR_PGM_LIB_NOT_FOUND
public static final java.lang.String MQJMS_DIR_PGM_LIB_NOT_FOUND
- Unable to load the native library required for PGM/IP.
Explanation:
The broker is set to use the multicast protocol PGM/IP, but the native library
required to support this protocol is not available on this platform or could
not be loaded.
User Response:
If the client is running on a platform that supports PGM, check that the native
library is present in its expected location. If PGM is unsupported, specify a
different multicast protocol on the broker.
- See Also:
- Constant Field Values
MQJMS_E_11_SERVICES_NOT_SETUP
public static final java.lang.String MQJMS_E_11_SERVICES_NOT_SETUP
- The required queues or publish/subscribe services are not set up: {0}.
Explanation:
The required WebSphere MQ setup for the messaging domain is not complete.
User Response:
For the point-to-point messaging, make sure that you have started the queue manager and,
if your JMS application is connecting as a client application, make sure that you have
started a listener for the correct port.
For publish/subscribe messaging, make sure that you have done the post installation setup.
- See Also:
- Constant Field Values
MQJMS_E_11_INVALID_DOMAIN_SPECIFIC
public static final java.lang.String MQJMS_E_11_INVALID_DOMAIN_SPECIFIC
- Operation for a domain specific object was not valid.
Explanation:
A JMS application attempted to perform an operation on domain specific object, but the
operation is valid only for the other messaging domain.
User Response:
Make sure that the JMS objects used by your application are relevant for the required
messaging domain.
If your application uses both messaging domains, consider using domain independent objects
throughout the application.
- See Also:
- Constant Field Values
MQJMS_E_11_INVALID_CROSS_DOMAIN
public static final java.lang.String MQJMS_E_11_INVALID_CROSS_DOMAIN
- Attribute for a domain specific object was not valid.
Explanation:
A JMS application attempted to set an attribute of a domain specific object, but the
attribute is valid only for the other messaging domain.
User Response:
Make sure that the JMS object types used by your application are relevant for the required
messaging domain.
If your application uses both messaging domains, consider using domain independent objects
throughout the application.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MQ_Q_CLOSE_FAILED
public static final java.lang.String MQJMS_EXCEPTION_MQ_Q_CLOSE_FAILED
- Failed to close WebSphere MQ queue.
Explanation:
JMS attempted to close a WebSphere MQ queue, but encountered an error.
The queue might already be closed, or another thread may be performing an
MQGET while close() is called.
User Response:
Use the linked exception to determine the cause of this error.
You may be able to perform the close() later.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MQ_NULL_Q
public static final java.lang.String MQJMS_EXCEPTION_MQ_NULL_Q
- MQQueue reference is null.
Explanation:
JMS attempted to perform some operation on a null MQQueue object.
User Response:
Check your system setup, and that all required queue names have been specified.
If this represents an internal error condition in JMS,
contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_GET_MSG_FAILED
public static final java.lang.String MQJMS_EXCEPTION_GET_MSG_FAILED
- Failed to get message from an MQQueue object.
Explanation:
JMS attempted to perform an MQGET; however WebSphere MQ reported an error.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_QMDISC_FAILED
public static final java.lang.String MQJMS_EXCEPTION_QMDISC_FAILED
- Failed to disconnect queue manager.
Explanation:
JMS encountered an error while attempting to disconnect.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MQ_NULL_QMGR
public static final java.lang.String MQJMS_EXCEPTION_MQ_NULL_QMGR
- MQQueueManager reference is null.
Explanation:
JMS attempted to perform an operation on a null MQQueueManager object.
User Response:
Check that the relevant object has not been closed.
If this represents an internal error condition in JMS,
contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_QMGR_FAILED
public static final java.lang.String MQJMS_EXCEPTION_QMGR_FAILED
- Failed to create an MQQueueManager for {0}.
Explanation:
JMS could not connect to a queue manager.
{0} gives the name of the queue manager.
User Response:
Use the linked exception to determine the cause of this error. Check the queue
manager is running and. If using client attach, check that the listener is running
and the channel, port and hostname are set correctly. If no queue manager name
has been specified, check that the default queue manager has been defined.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_SOME_PROBLEM
public static final java.lang.String MQJMS_EXCEPTION_SOME_PROBLEM
- WebSphere MQ problem: {0}.
Explanation: JMS encountered a problem with WebSphere MQ.
{0} describes the problem.
User Response:
Use the included text and linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_PUT_MSG_FAILED
public static final java.lang.String MQJMS_EXCEPTION_PUT_MSG_FAILED
- Failed to send message to an MQQueue object.
Explanation:
JMS attempted to perform an MQPUT, but WebSphere MQ reported an error.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MQ_Q_OPEN_FAILED
public static final java.lang.String MQJMS_EXCEPTION_MQ_Q_OPEN_FAILED
- Failed to open an MQQueue object.
Explanation:
JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error.
User Response:
Use the linked exception to determine the cause of this error.
Check that the specified queue and queue manager are defined correctly.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MQ_QM_COMMIT_FAILED
public static final java.lang.String MQJMS_EXCEPTION_MQ_QM_COMMIT_FAILED
- MQQueueManager.commit() failed.
Explanation:
JMS attempted to perform an MQCMIT, but WebSphere MQ reported an error.
User Response:
Use the linked exception to determine the cause of this error.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MQ_UNKNOWN_DEFTYPE
public static final java.lang.String MQJMS_EXCEPTION_MQ_UNKNOWN_DEFTYPE
- Unknown value for an MQQueue object definitionType: {0}.
Explanation:
Unable to delete the temporary queue because the definitionType is not valid.
User Response:
Check the setting of the definitionType.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_MQ_Q_INQUIRE_FAILED
public static final java.lang.String MQJMS_EXCEPTION_MQ_Q_INQUIRE_FAILED
- Failed to inquire an MQQueue object depth.
Explanation:
WebSphere MQ JMS is unable to determine how many messages are on the queue.
User Response: Check that the queue and queue manager are available.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_XACLOSE_FAILED
public static final java.lang.String MQJMS_EXCEPTION_XACLOSE_FAILED
- XACLOSE failed.
Explanation:
See linked XAException for more details.
- See Also:
- Constant Field Values
MQJMS_EXCEPTION_AUTHENTICATION_FAILED
public static final java.lang.String MQJMS_EXCEPTION_AUTHENTICATION_FAILED
- The security authentication supplied for MQQueueManager was not valid.
Explanation:
Bad username, or password, or both.
In bindings mode, a supplied user ID does not match the logged in user ID.
User Response:
Check that the user IDs used by WebSphere MQ are all assigned to the relevant groups and given
appropriate user permissions.
- See Also:
- Constant Field Values
MQJMS_E_TMPQ_FAILED
public static final java.lang.String MQJMS_E_TMPQ_FAILED
- Failed to create a temporary queue from {0}.
Explanation:
Creation of temporary queue failed.
User Response:
See linked exception for more information.
Check that the TemporaryModel parameter against the QueueConnectionFactory is set to a
valid model queue.
- See Also:
- Constant Field Values
MQJMS_E_TMPQ_CLOSED
public static final java.lang.String MQJMS_E_TMPQ_CLOSED
- Temporary queue already closed or deleted.
Explanation:
Temporary queue no longer exists or is equal to null.
User Response:
Check to see that the queue has been created, and that the session is still available.
- See Also:
- Constant Field Values
MQJMS_E_TMPQ_INUSE
public static final java.lang.String MQJMS_E_TMPQ_INUSE
- Temporary queue in use.
Explanation:
Another program is using the queue.
User Response:
Wait for the temporary queue to become free or create another.
- See Also:
- Constant Field Values
MQJMS_E_TMPQ_DEL_STATIC
public static final java.lang.String MQJMS_E_TMPQ_DEL_STATIC
- Cannot delete a static queue.
Explanation:
Attempted to delete a queue of type static, where a temporary queue was expected.
User Response:
Check the expected queue type for deletion.
- See Also:
- Constant Field Values
MQJMS_E_TMPQ_DEL_FAILED
public static final java.lang.String MQJMS_E_TMPQ_DEL_FAILED
- Failed to delete temporary queue.
Explanation:
The temporary queue may be persistent or busy.
User Response:
See the linked exception for more details.
Wait if the queue is busy, or delete the queue manually if it is persistent.
- See Also:
- Constant Field Values
MQJMS_PS_GENERAL_ERROR
public static final java.lang.String MQJMS_PS_GENERAL_ERROR
- Publish/Subscribe failed due to {0}.
Explanation:
General error: {0} shows the reason.
User Response:
Check the linked exception reason and completion codes for more information.
It is possible that the broker and queue manager versions are incompatible.
- See Also:
- Constant Field Values
MQJMS_PS_TOPIC_NULL
public static final java.lang.String MQJMS_PS_TOPIC_NULL
- Topic reference is null.
Explanation:
Topic supplied to a publisher is null.
User Response:
Use non-null values.
- See Also:
- Constant Field Values
MQJMS_PS_COMMAND_MSG_BUILD
public static final java.lang.String MQJMS_PS_COMMAND_MSG_BUILD
- Failed to build command {0}.
Explanation: Broker message command parameters incorrect.
User Response: Check linked exception for cause.
- See Also:
- Constant Field Values
MQJMS_PS_COMMAND_MSG_FAILED
public static final java.lang.String MQJMS_PS_COMMAND_MSG_FAILED
- Failed to publish command to WebSphere MQ queue.
Explanation:
Invalid command, queue unavailable or broker errors.
User Response:
Check linked exception reason and completion codes for more information.
- See Also:
- Constant Field Values
MQJMS_PS_PUBLISH_MSG_BUILD
public static final java.lang.String MQJMS_PS_PUBLISH_MSG_BUILD
- Failed to build publish message.
Explanation:
Unable to build the base message for the broker.
User Response:
See the linked exception for further details.
Check settings and parameters are all correct.
- See Also:
- Constant Field Values
MQJMS_PS_PUBLISH_MSG_FAILED
public static final java.lang.String MQJMS_PS_PUBLISH_MSG_FAILED
- Failed to publish message to WebSphere MQ queue.
Explanation:
See linked exception for more information.
User Response:
Check settings and parameters are all correct.
- See Also:
- Constant Field Values
MQJMS_PS_STORE_ADMIN_ENTRY
public static final java.lang.String MQJMS_PS_STORE_ADMIN_ENTRY
- Failed to store admininstration entry.
Explanation: An add to the admin or status queue failed due
to duplication or some other error. See linked exception for more
information.
User Response: Check for duplicates and retry.
- See Also:
- Constant Field Values
MQJMS_PS_SUB_Q_OPEN_FAILED
public static final java.lang.String MQJMS_PS_SUB_Q_OPEN_FAILED
- Failed to open subscriber queue {0}.
User Response:
See linked exception for more information.
- See Also:
- Constant Field Values
MQJMS_PS_SUB_Q_DELETE_FAILED
public static final java.lang.String MQJMS_PS_SUB_Q_DELETE_FAILED
- Failed to delete subscriber queue {0}.
Explanation: {0} gives the queue name. See linked exception for more information.
User Response:
See Writing WebSphere MQ JMS publish/subscribe applications section
of WebSphere MQ Using Java for more information.
- See Also:
- Constant Field Values
MQJMS_PS_UNKNOWN_DS
public static final java.lang.String MQJMS_PS_UNKNOWN_DS
- Unknown durable subscription {0}.
Explanation:
Could not locate the given subscription.
For example, during an unsubscribe request.
User Response:
- See Also:
- Constant Field Values
MQJMS_E_TMPT_DELETED
public static final java.lang.String MQJMS_E_TMPT_DELETED
- TemporaryTopic already deleted.
Explanation:
TemporaryTopic no longer exists or is equal to null.
User Response:
Check that the queue has been created, and that the session is still
available.
- See Also:
- Constant Field Values
MQJMS_E_TMPT_OUTOFSCOPE
public static final java.lang.String MQJMS_E_TMPT_OUTOFSCOPE
- TemporaryTopic out of scope.
Explanation:
The current connection ID does not match the connection that
created the temporary topic.
User Response:
Check that the topic has been created under this connection.
- See Also:
- Constant Field Values
MQJMS_PS_INVALID_SUBQ_PREFIX
public static final java.lang.String MQJMS_PS_INVALID_SUBQ_PREFIX
- Subscriber queue prefix was not valid: {0}.
Explanation:
The name specified is not valid.
It must begin with SYSTEM.JMS.D for durable subscriptions or SYSTEM.JMS.ND for non-durable
subscriptions.
User Response:
- See Also:
- Constant Field Values
MQJMS_PS_SUBQ_REQUEUE
public static final java.lang.String MQJMS_PS_SUBQ_REQUEUE
- Durable re-subscribe must use same subscriber queue; specified: {0}, original: {1}.
Explanation:
{0} and {1} show the differing queue names.
Unable to get a subscription due to wrong queue manager or queue.
User Response:
Check settings.
- See Also:
- Constant Field Values
MQJMS_PS_SUB_ACTIVE
public static final java.lang.String MQJMS_PS_SUB_ACTIVE
- Subscription has an active TopicSubscriber.
Explanation:
Can be caused by a problem opening a queue or if a subscription already exists on the JVM.
If running in WebSphere Application Server there can be other causes.
See linked exception, if set, for more information.
User Response:
Check settings.
- See Also:
- Constant Field Values
MQJMS_PS_NULL_CLIENTID
public static final java.lang.String MQJMS_PS_NULL_CLIENTID
- The use of an uninitialized client ID is not possible.
Explanation:
The client ID in the connection has not been set.
User Response:
Set the clientId before attempting to perform any operation.
- See Also:
- Constant Field Values
MQJMS_E_TMPT_IN_USE
public static final java.lang.String MQJMS_E_TMPT_IN_USE
- TemporaryTopic in use.
Explanation:
Something else is currently using the topic.
User Response:
Wait until the topic is free or create another topic.
Ensure subscribers deregister when finished.
- See Also:
- Constant Field Values
MQJMS_ERR_QSENDER_CLOSED
public static final java.lang.String MQJMS_ERR_QSENDER_CLOSED
- QueueSender is closed.
User Response:
Open or reopen the queue sender if required.
- See Also:
- Constant Field Values
MQJMS_LOCAL_XA_CLASH
public static final java.lang.String MQJMS_LOCAL_XA_CLASH
- Local transactions not allowed with XA sessions.
Explanation:
A call pertaining to a local transaction was made on a session involved with XA-coordinated
transactions
User Response:
This typically represents an error in an application server.
Consult your application server's documentation and any error logs.
- See Also:
- Constant Field Values
MQJMS_PUBLISHER_CLOSED
public static final java.lang.String MQJMS_PUBLISHER_CLOSED
- TopicPublisher is closed.
User Response:
Open or reopen the topic publisher if required.
- See Also:
- Constant Field Values
MQJMS_EXC_ENLIST_FAILED
public static final java.lang.String MQJMS_EXC_ENLIST_FAILED
- Enlist failed.
Explanation:
JTSXA.enlist threw an exception that was caught by JMS.
User Response:
Check the linked exception, reason and completion codes for more information.
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_CLIENTID_FIXED
public static final java.lang.String MQJMS_CLIENTID_FIXED
- Client ID cannot be set after connection has been used.
Explanation:
The Client ID of a connection can be set only once, and only before the connection is used.
User Response:
Set the clientId before using the connection.
- See Also:
- Constant Field Values
MQJMS_CLIENTID_NO_RESET
public static final java.lang.String MQJMS_CLIENTID_NO_RESET
- Resetting the Client ID is not allowed.
Explanation:
The Client ID of a connection can be set only once, and only before the connection is used.
User Response:
Set the Client ID before using the connection.
- See Also:
- Constant Field Values
MQJMS_QRECEIVER_CLOSED
public static final java.lang.String MQJMS_QRECEIVER_CLOSED
- QueueReceiver is closed.
User Response:
Open or reopen the receiver.
- See Also:
- Constant Field Values
MQJMS_SUBSCRIBER_CLOSED
public static final java.lang.String MQJMS_SUBSCRIBER_CLOSED
- TopicSubscriber is closed.
User Response:
Open or reopen the TopicSubscriber.
- See Also:
- Constant Field Values
MQJMS_MSEL_AND_BVER_INCOMPATIBLE
public static final java.lang.String MQJMS_MSEL_AND_BVER_INCOMPATIBLE
- Broker message selection is only valid when using WebSphere MQ Integrator broker.
Explanation:
Broker version and message selection are not consistent.
User Response:
Ensure the broker version has been set in the ConnectionFactory.
Use the method setBrokerVersion(JMSC.MQJMS_BROKER_V2) on the ConnectionFactory for
WebSphere MQ Integrator or WebSphere MQ Event Broker.
- See Also:
- Constant Field Values
MQJMS_MESSAGEPRODUCER_CLOSED
public static final java.lang.String MQJMS_MESSAGEPRODUCER_CLOSED
- Message Producer is closed.
Explanation:
Either or both of the session and connection are closed.
User Response:
Check to ensure that the session and connection are both available.
- See Also:
- Constant Field Values
MQJMS_MESSAGECONSUMER_CLOSED
public static final java.lang.String MQJMS_MESSAGECONSUMER_CLOSED
- Message Consumer is closed.
Explanation:
Either or both of the session and connection are closed.
User Response:
Check to ensure that the session and connection are both available.
- See Also:
- Constant Field Values
MQJMS_PS_NULL_NAME
public static final java.lang.String MQJMS_PS_NULL_NAME
- The use of a null name is not possible.
Explanation:
Durable connection consumers must be named.
User Response:
Check for null values.
- See Also:
- Constant Field Values
MQJMS_E_BROKER_MESSAGE_CONTENT
public static final java.lang.String MQJMS_E_BROKER_MESSAGE_CONTENT
- The broker control message content: {0} is not valid.
Explanation:
{0} explains further.
User Response:
Check the broker documentation for message content information.
- See Also:
- Constant Field Values
MQJMS_E_UNREC_BROKER_MESSAGE
public static final java.lang.String MQJMS_E_UNREC_BROKER_MESSAGE
- Unrecognized message from publish / subscribe broker.
Explanation:
The message received from the broker was not of a recognized or supported format.
User Response:
Check that the broker you are using is supported and refer to broker documentation for settings.
- See Also:
- Constant Field Values
MQJMS_E_CLEANUP_REP_BAD_LEVEL
public static final java.lang.String MQJMS_E_CLEANUP_REP_BAD_LEVEL
- Level for repeating Cleanup is not valid.
User Response:
Set cleanupLevel property to an appropriate value.
- See Also:
- Constant Field Values
MQJMS_E_CLEANUP_NONE_REQUESTED
public static final java.lang.String MQJMS_E_CLEANUP_NONE_REQUESTED
- Cleanup level of NONE requested.
Explanation:
Cleanup requested while cleanupLevel set to NONE.
User Response:
Set cleanupLevel property to an appropriate value.
- See Also:
- Constant Field Values
MQJMS_PS_SUBSTORE_NOT_SUPPORTED
public static final java.lang.String MQJMS_PS_SUBSTORE_NOT_SUPPORTED
- Subscription store type not supported by queue manager.
Explanation:
Not an MQSPIQueue manager or deferred message not supported.
User Response:
Possible incompatibility between queue manager version and broker.
Specify a different type of subscription store or upgrade the queue manager.
- See Also:
- Constant Field Values
MQJMS_PS_INCORRECT_SUBSTORE
public static final java.lang.String MQJMS_PS_INCORRECT_SUBSTORE
- Incorrect subscription store type.
Explanation:
Subscription store changed within TopicConnection.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_PS_WRONG_SUBSCRIPTION_TYPE
public static final java.lang.String MQJMS_PS_WRONG_SUBSCRIPTION_TYPE
- Incorrect subscription type for this subscription store.
Explanation:
TopicSubscriber was created with a different SUBSTORE setting than current TopicConnection.
User Response:
Ensure TopicSubscribers are only used during the lifetime of their parent TopicConnection.
- See Also:
- Constant Field Values
MQJMS_ADMIN_ERROR
public static final java.lang.String MQJMS_ADMIN_ERROR
- Error.
Explanation:
An internal error has occurred.
User Response:
Contact your system administrator.
- See Also:
- Constant Field Values
MQJMS_ADMIN_CTX_NOT_EMPTY
public static final java.lang.String MQJMS_ADMIN_CTX_NOT_EMPTY
- Context is not empty.
Explanation:
Error deleting Context due to context not being empty.
User Response:
Remove context contents before trying delete.
- See Also:
- Constant Field Values
MQJMS_ADMIN_BND_NONADMIN
public static final java.lang.String MQJMS_ADMIN_BND_NONADMIN
- Binding non-administerable or not found.
Explanation:
From JMSAdmin, an object was specified on the command line that either does not exist,
or is not an object that JMSAdmin can administer.
User Response:
Specify a valid obect on the JMSAdmin command line.
- See Also:
- Constant Field Values
MQJMS_ADMIN_CTX_NOTFND
public static final java.lang.String MQJMS_ADMIN_CTX_NOTFND
- Context not found.
Explanation:
Could not find a context to match the name given.
User Response:
Ensure the correct context name is specified.
- See Also:
- Constant Field Values
MQJMS_ADMIN_OBJ_INACTIVE
public static final java.lang.String MQJMS_ADMIN_OBJ_INACTIVE
- Object is inactive, so cannot perform directory operations.
Explanation:
The JNDI service is inactive.
User Response:
- See Also:
- Constant Field Values
MQJMS_ADMIN_CONF_MISSING
public static final java.lang.String MQJMS_ADMIN_CONF_MISSING
- Missing configuration properties.
Explanation:
The Provider URL or InitialContextFactory are undefined
User Response:
Ensure that these parameters are defined.
/
/*See Using the WebSphere MQ
JMS administration tool in WebSphere MQ Using Java for
JMSAdmin and JNDI information.
- See Also:
- Constant Field Values
MQJMS_ADMIN_NON_MQJMS
public static final java.lang.String MQJMS_ADMIN_NON_MQJMS
- Object is not a WebSphere MQ JMS administered object.
User Response:
- See Also:
- Constant Field Values
MQJMS_ADMIN_JNDI_INITFAIL
public static final java.lang.String MQJMS_ADMIN_JNDI_INITFAIL
- JNDI initialization failed.
User Response:
Check your JNDI settings and service for additional information on the cause of this problem
run with the -v argument.
- See Also:
- Constant Field Values
MQJMS_ADMIN_NEW_CTX_FAIL
public static final java.lang.String MQJMS_ADMIN_NEW_CTX_FAIL
- Unable to create context.
Explanation:
Administration service failed.
User Response:
Check LDAP and JNDI settings.
- See Also:
- Constant Field Values
MQJMS_ADMIN_VAL_OBJ_FAIL
public static final java.lang.String MQJMS_ADMIN_VAL_OBJ_FAIL
- Unable to create a valid object.
Explanation:
Consistency check failed.
User Response:
Check the parameters supplied or contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_ADMIN_BIND_FAIL
public static final java.lang.String MQJMS_ADMIN_BIND_FAIL
- Unable to bind object.
Explanation:
Administration service bind or copy or move operation failed.
User Response:
Check that you have correctly set up your JNDI provider.
- See Also:
- Constant Field Values
MQJMS_ADMIN_INVALID_NAME
public static final java.lang.String MQJMS_ADMIN_INVALID_NAME
- A name was supplied that was not valid.
Explanation:
JMSAdmin error. The name supplied when trying to delete a context was invalid.
User Response:
- See Also:
- Constant Field Values
MQJMS_ADMIN_SYN_ERR
public static final java.lang.String MQJMS_ADMIN_SYN_ERR
- Syntax error.
Explanation:
The command syntax was not valid.
User Response:
- See Also:
- Constant Field Values
MQJMS_ADMIN_CNT_OPEN_CFG
public static final java.lang.String MQJMS_ADMIN_CNT_OPEN_CFG
- Cannot open configuration file.
Explanation:
Configuration file might not exist.
User Response:
Check that the MQ_JAVA_INSTALL_PATH environment variable exists and that it specifies the
installation directory of the base Java classes.
- See Also:
- Constant Field Values
MQJMS_ADMIN_MV_SEMIFAIL
public static final java.lang.String MQJMS_ADMIN_MV_SEMIFAIL
- Unable to complete MOVE; a COPY has been done instead.
Explanation:
The object was copied, but the original object could not be deleted.
User Response:
Delete the original object manually.
- See Also:
- Constant Field Values
MQJMS_ADMIN_LEXERR
public static final java.lang.String MQJMS_ADMIN_LEXERR
- Lexical error.
User Response:
- See Also:
- Constant Field Values
MQJMS_ADMIN_PROPVAL_NULL
public static final java.lang.String MQJMS_ADMIN_PROPVAL_NULL
- Parameter {0} is null.
Explanation:
A null value was supplied when a non-null Object was expected.
User Response:
Check that the supplied parameter for {0} has been correctly instantiated
and retry.
- See Also:
- Constant Field Values
MQJMS_ADMIN_INV_PROP
public static final java.lang.String MQJMS_ADMIN_INV_PROP
- Parameter {1} for method {0} was not valid.
Explanation:
The parameter {1} supplied to method {0} was incorrectly specified.
User Response:
Correct the parameter supplied to {0} and retry.
- See Also:
- Constant Field Values
MQJMS_ADMIN_INV_PROP_CTX
public static final java.lang.String MQJMS_ADMIN_INV_PROP_CTX
- The property was not valid in this context.
Explanation:
JMSAdmin object value is not valid in the current context.
User Response:
- See Also:
- Constant Field Values
MQJMS_ADMIN_INV_PROP_VAL
public static final java.lang.String MQJMS_ADMIN_INV_PROP_VAL
- Value {1} for property {0} was not valid.
Explanation:
The value supplied for parameter {0} is not valid.
User Response:
Correct the value supplied and retry.
- See Also:
- Constant Field Values
MQJMS_ADMIN_PROP_UNK
public static final java.lang.String MQJMS_ADMIN_PROP_UNK
- Unknown parameter: {0}.
Explanation:
The parameter {0} is unknown.
User Response:
Check the parameter to be set and retry.
- See Also:
- Constant Field Values
MQJMS_ADMIN_CTX_NOTFNDU
public static final java.lang.String MQJMS_ADMIN_CTX_NOTFNDU
- Context not found or cannot be deleted.
Explanation:
The specified child context could not be deleted.
User Response:
Ensure the correct context name was specified.
- See Also:
- Constant Field Values
MQJMS_ADMIN_OBJTYPE_MISMATCH
public static final java.lang.String MQJMS_ADMIN_OBJTYPE_MISMATCH
- Expected and actual object types do not match.
Explanation:
Requested and retrieved objects are of different types.
User Response:
Check that you have specified the correct object type.
- See Also:
- Constant Field Values
MQJMS_ADMIN_CLASH_CLIENT
public static final java.lang.String MQJMS_ADMIN_CLASH_CLIENT
- Clash of the client properties.
Explanation:
Client properties specified for a bindings connection are not compatible.
User Response:
Ensure the ConnectionFactory properties are correct.
- See Also:
- Constant Field Values
MQJMS_ADMIN_CLASH_EXITINIT
public static final java.lang.String MQJMS_ADMIN_CLASH_EXITINIT
- ExitInit string supplied without Exit string.
Explanation:
ExitInit string supplied but Exit is not set.
User Response:
Set appropriate exit, or unset ExitInit string.
- See Also:
- Constant Field Values
MQJMS_ADMIN_WS_INST
public static final java.lang.String MQJMS_ADMIN_WS_INST
- Unable to create a WebSphere MQ specific class.
The WebSphere MQ classes might not have been installed or added to the CLASSPATH.
User Response:
Check your WebSphere Application Server installation and CLASSPATH variable.
- See Also:
- Constant Field Values
MQJMS_ADMIN_INVALID_AUTH_TYPE
public static final java.lang.String MQJMS_ADMIN_INVALID_AUTH_TYPE
- The authentication type supplied was not valid - used none.
Explanation:
The AdminService JNDI initialization parameters contained an authorization scheme which was not valid, so
none is used as the value instead.
User Response:
- See Also:
- Constant Field Values
MQJMS_ADMIN_CONVERT_CIPHER
public static final java.lang.String MQJMS_ADMIN_CONVERT_CIPHER
- Matching CipherSpec {0} to CipherSuite {1} not possible.
Explanation:
The supplied CipherSpec could not be matched to a known CipherSuite
User Response:
Check the supplied CipherSpec is supported and retry.
- See Also:
- Constant Field Values
MQJMS_ADMIN_ICF_NOT_FOUND
public static final java.lang.String MQJMS_ADMIN_ICF_NOT_FOUND
- Class specified by INITIAL_CONTEXT_FACTORY not found in CLASSPATH.
User Response:
Check the classname or add the class to the CLASSPATH.
- See Also:
- Constant Field Values
MQJMS_UTIL_PS_NO_BROKER
public static final java.lang.String MQJMS_UTIL_PS_NO_BROKER
- No broker response.
Explanation:
Possible causes are:
- Broker is not running.
- You are using BrokerVersion=V2 in your TopicConnectionFactory with the WebSphere MQ
Publish/Subscribe broker, which does not support this.
- The Broker has rejected the publication or subscription and placed it on the
SYSTEM.DEAD.LETTER.QUEUE
User Response:
Ensure that your broker is running.
Check the system event log for broker error messages.
Check that the broker supports the BrokerVersion you are using.
Check the SYSTEM.DEAD.LETTER.QUEUE for rejected messages.
- See Also:
- Constant Field Values
MQJMS_UTIL_PS_NO_MSG
public static final java.lang.String MQJMS_UTIL_PS_NO_MSG
- The broker appears to be running, but the message did not arrive.
Explanation:
Generated by the installation verification test when the subscriber fails to receive the
published message.
User Response:
Check that you have set up the broker correctly.
Check system event logs for broker error messages.
Check the SYSTEM.DEAD.LETTER.QUEUE for messages rejected by the broker.
- See Also:
- Constant Field Values
MQJMS_UTIL_PS_NO_QM
public static final java.lang.String MQJMS_UTIL_PS_NO_QM
- Unable to connect to queue manager.
Explanation:
Generated by the installation verification test.
User Response:
Check that the queue manager is running and that its name is specified correctly in the
IVTTest parameters.
- See Also:
- Constant Field Values
MQJMS_UTIL_PS_NO_BRK_Q
public static final java.lang.String MQJMS_UTIL_PS_NO_BRK_Q
- Unable to access the broker control queue on the queue manager.
User Response:
Check that the control queue exists.
The default name is SYSTEM.BROKER.CONTROL.QUEUE.
- See Also:
- Constant Field Values
MQJMS_DIR_IMB_BADSOCKNAME
public static final java.lang.String MQJMS_DIR_IMB_BADSOCKNAME
- The socket family name: {0} is not valid.
Explanation:
A socket family name given to an instance of IMBSocketFactory was not valid.
{0} shows the bad name.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_IMB_NOCLASS
public static final java.lang.String MQJMS_DIR_IMB_NOCLASS
- An exception occurred while attempting to load socket factory class {0}, exception: <{1}>.
Explanation:
Either a ClassNotFoundException, an InstantiationException or an IllegalAccessException
occurred while trying to load a particular IMBSocketFactory.
{0} gives the name of the exception class.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_SECLDERR
public static final java.lang.String MQJMS_DIR_MIN_SECLDERR
- An exception occurred while loading the minimal client security implementation.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_UNXEXC
public static final java.lang.String MQJMS_DIR_MIN_UNXEXC
- An unexpected exception in minimal client; {0}.
Explanation:
An unusual or unexpected exception occurred at the minimal client.
{0} gives more details.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_BADTOP
public static final java.lang.String MQJMS_DIR_MIN_BADTOP
- A specified topic was malformed, topic; {0}.
Explanation:
{0} gives the name of the malformed topic.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_EOF
public static final java.lang.String MQJMS_DIR_MIN_EOF
- End of file (EOF) was encountered while receiving data in the minimal client.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_BRKERR
public static final java.lang.String MQJMS_DIR_MIN_BRKERR
- The broker indicated an error on the minimal client connection.
User Response:
Refer to JMS or broker documentation.
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_BADMSG
public static final java.lang.String MQJMS_DIR_MIN_BADMSG
- Connector.send was called with a message value that is not valid.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_BADFIELD
public static final java.lang.String MQJMS_DIR_MIN_BADFIELD
- The value of field {0} is not valid.
Explanation:
{0} shows the value used.
User Response:
See Table 38 on page 457 for a list of properties and their possible values.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_INTERR
public static final java.lang.String MQJMS_DIR_MIN_INTERR
- An unexpected internal error occurred in the minimal client.
Explanation:
Internal problem.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_NOTBYTES
public static final java.lang.String MQJMS_DIR_MIN_NOTBYTES
- A Byte message operation was requested on something that is not a Byte message.
Explanation:
The wrong message type was found.
User Response:
Check message type before performing type specific operations.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_NOTTEXT
public static final java.lang.String MQJMS_DIR_MIN_NOTTEXT
- A Text message operation was requested on something that is not a Text message.
Explanation:
The wrong message type was found.
User Response:
Check message type before performing type specific operations.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_NOTSTREAM
public static final java.lang.String MQJMS_DIR_MIN_NOTSTREAM
- A Stream message operation was requested on something that is not a Stream message.
Explanation:
The wrong message type was found.
User Response:
Check message type before performing type specific operations.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_NOTMAP
public static final java.lang.String MQJMS_DIR_MIN_NOTMAP
- A Map message operation was requested on something that is not a Map message.
Explanation:
The wrong message type was found.
User Response:
Check message type before performing type specific operations.
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_BADBRKMSG
public static final java.lang.String MQJMS_DIR_MIN_BADBRKMSG
- The broker sent a message during authentication which was not valid.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_UNVPRO
public static final java.lang.String MQJMS_DIR_MIN_UNVPRO
- The broker requested an unavailable protocol during authentication.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_AUTHREJ
public static final java.lang.String MQJMS_DIR_MIN_AUTHREJ
- Minimal client connection rejected because of authentication failure.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_NOQOP
public static final java.lang.String MQJMS_DIR_MIN_NOQOP
- No QOP available in the minimal client.
Explanation:
Indicates that QOP is not implemented in the current version of the minimal client.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_NOTHDPOOL
public static final java.lang.String MQJMS_DIR_JMS_NOTHDPOOL
- An exception occurred while attempting to load thread pooling support; {0}.
Explanation:
An exception occured while attempting to load thread pooling support in the JMS client.
{0} gives details of the exception.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_FMTINT
public static final java.lang.String MQJMS_DIR_JMS_FMTINT
- An attempt was made to read from a Stream message before a previous read has completed.
Explanation:
Internal error.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_THDEXC
public static final java.lang.String MQJMS_DIR_JMS_THDEXC
- An exception occurred while initializing a thread pool instance; {0}.
Explanation:
A SocketThreadPoolException exception occured while initializing a thread pool instance in the JMS client.
{0} gives details of the exception.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_NEXCLIS
public static final java.lang.String MQJMS_DIR_JMS_NEXCLIS
- No ExceptionListener was set.
User Response:
Create an ExceptionListener.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_KILLMON
public static final java.lang.String MQJMS_DIR_JMS_KILLMON
- The client-side connection monitor is terminating.
User Response:
Restart the connection.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_LSTACT
public static final java.lang.String MQJMS_DIR_JMS_LSTACT
- Attempted to synchronously receive on a MessageConsumer for which a listener is active.
Explanation:
MessageConsumer.receive() was called but a message listener is already active on the connection.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_TCSTSTP
public static final java.lang.String MQJMS_DIR_JMS_TCSTSTP
- An IOException occurred when starting or stopping delivery on the connection; {0}.
Explanation:
{0} gives details of the exception.
User Response:
Restart the connection.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_RUNKEXC
public static final java.lang.String MQJMS_DIR_JMS_RUNKEXC
- An exception occurred during synchronous receive; {0}.
Explanation:
Internal error. {0} gives details of the exception.
User Response:
Restart connection.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_INVPRI
public static final java.lang.String MQJMS_DIR_JMS_INVPRI
- A JMSPriority level of {0} is outside the range specified in JMS.
Explanation:
{0} gives the value that is in error.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_BADID
public static final java.lang.String MQJMS_DIR_JMS_BADID
- The specified JMSMessageID, {0}, is not valid.
Explanation:
Incorrect syntax was used to specify a message ID in Message.setJMSMessageID.
The correct syntax is ID:[0-9]+.
User Response:
Check parameters.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_NOMORE
public static final java.lang.String MQJMS_DIR_JMS_NOMORE
- No more client parameter changes allowed.
Explanation:
Internal error.
An attempt was made to set a SessionConfig parameter when no more changes are allowed.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_BADNUM
public static final java.lang.String MQJMS_DIR_JMS_BADNUM
- Exception {1} occurred when initializing parameter {0}.
Explanation:
{0} identifies the parameter that failed to initialize and {1}, the caught exception.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_TCFLERR
public static final java.lang.String MQJMS_DIR_JMS_TCFLERR
- An exception occurred while creating the TopicConnection; {0}.
Explanation:
{0} gives details of the exception.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_CLOSED
public static final java.lang.String MQJMS_DIR_JMS_CLOSED
- Operation not permitted on an entity that is closed.
Explanation:
An operation was requested on a closed publisher, session, or connection.
User Response:
Ensure that the publisher, session, or connection is open before trying this operation.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_BDTOPIMPL
public static final java.lang.String MQJMS_DIR_JMS_BDTOPIMPL
- The {0} implementation of Topic is not supported.
Explanation:
The Topic instance passed to a TopicPublisher or TopicSession method has an unsupported
run-time implementation.
{0} gives the class name of the unsupported implementation.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_PBNOWLD
public static final java.lang.String MQJMS_DIR_JMS_PBNOWLD
- Topic {0} contains a wildcard, which is invalid for publishing.
Explanation:
The Topic specified to a TopicPublisher method contained a wildcard.
Wildcards are not allowed in Topics when publishing messages.
The failing Topic is given by {0}.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_PBIOERR
public static final java.lang.String MQJMS_DIR_JMS_PBIOERR
- An IOException occurred while publishing; {0}.
Explanation:
An IOException occured while publishing a message.
{0} gives details of the exception.
User Response:
See Writing WebSphere MQ JMS publish/subscribe applications in
WebSphere MQ Using Java for more information.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_TMPVIO
public static final java.lang.String MQJMS_DIR_JMS_TMPVIO
- Wrong use of temporary topic with the current connection.
Explanation:
Attempted to use a temporary topic not created on the current connection.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_TSIOERR
public static final java.lang.String MQJMS_DIR_JMS_TSIOERR
- An IOException occurred while subscribing; {0}.
Explanation:
An IOException occured while subscribing.
{0} gives details of the exception.
User Response:
See Writing WebSphere MQ JMS publish/subscribe applications in
WebSphere MQ Using Java for more information.
- See Also:
- Constant Field Values
MQJMS_DIR_JMS_TSBADMTC
public static final java.lang.String MQJMS_DIR_JMS_TSBADMTC
- While creating a TopicSubscriber attempting to add the subscription to the matching
engine resulted in exception: {0}.
Explanation:
{0} gives details of the exception.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_UNKEXC
public static final java.lang.String MQJMS_DIR_MTCH_UNKEXC
- An unexpected exception occured in the matching engine: {0}.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_NULRM
public static final java.lang.String MQJMS_DIR_MTCH_NULRM
- An attempt was made to remove an object with Topic {0} from an empty matching engine: {1}.
Explanation:
Internal error. An attempt was made to remove an object from a null tree in the matching engine.
{0} gives the Topic and {1} gives the MatchTarget.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_NULCH
public static final java.lang.String MQJMS_DIR_MTCH_NULCH
- An attempt was made to remove an object with a Topic {0} from the matching engine, but it
did not have a cache entry: {1}.
Explanation:
Internal error. An attempt was made to remove an object from a null tree in the matching engine.
{0} gives the Topic and {1} gives the cache entry.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_BDMSG
public static final java.lang.String MQJMS_DIR_MTCH_BDMSG
- An exception occured while attempting to access a field of a message; {0}.
Explanation:
A corrupt message format was discovered.
Internal error.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_ECNMIN
public static final java.lang.String MQJMS_DIR_MTCH_ECNMIN
- An EvalCache get or put operation specified an invalid ID.
Explanation:
Internal Error. The MinValue of an EvalCache could not be increased, although the
operation expected it to be.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_TOMNY
public static final java.lang.String MQJMS_DIR_MTCH_TOMNY
- Too many content attributes were specified.
Explanation:
Internal Error. Too many non-topic attributes were specified in Factor.createMatcherInternal.
User Response:
Contact your IBM representative.
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_BDWLD
public static final java.lang.String MQJMS_DIR_MTCH_BDWLD
- An incorrect use of the Topic wildcard character {0} was detected.
Explanation:
The failed Topic is given by parameter {0}.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_BDSEP
public static final java.lang.String MQJMS_DIR_MTCH_BDSEP
- The Topic segment separator {0} appears in an incorrect position.
Explanation:
A subscription Topic separator was used incorrectly.
{0} shows the bad separator.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_PSTPER
public static final java.lang.String MQJMS_DIR_MTCH_PSTPER
- An exception occurred while parsing a subscription selector; {0}.
Explanation:
A TypeCheckException occurred while loading or invoking the match parser.
This might indicate a syntax error in your Selector.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_BDESC
public static final java.lang.String MQJMS_DIR_MTCH_BDESC
- The escape sequence was used to terminate the pattern; {0}.
Explanation:
This might indicate a syntax error in your Selector.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_BDESCL
public static final java.lang.String MQJMS_DIR_MTCH_BDESCL
- The escape sequence {0} passed to the pattern tool is longer than one character.
Explanation:
This might indicate a syntax error in your Selector.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MTCH_UNXTYP
public static final java.lang.String MQJMS_DIR_MTCH_UNXTYP
- A message field was expected to contain a value of type {0} but contained one of type {1}.
Explanation:
This may indicate a syntax error in your Selector.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_NOSUB
public static final java.lang.String MQJMS_DIR_MIN_NOSUB
- Unauthorized subscription to topic {0}.
Explanation:
Attempted to create a subscription to a Topic that is not authorized for the client.
{0} shows the Topic.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_NOXASUP
public static final java.lang.String MQJMS_DIR_MIN_NOXASUP
- Transport type DIRECT within a transaction is not supported.
Explanation:
The application attempted to use a transactional method. This is not
supported with a DirectIP transport type.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_PER_NOT_SUPPORTED
public static final java.lang.String MQJMS_DIR_MIN_PER_NOT_SUPPORTED
- Persistent messages not supported for transport type DIRECT.
Explanation:
A DeliveryMode that is not valid was specified when using DirectIP transport.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_TTL_NOT_SUPPORTED
public static final java.lang.String MQJMS_DIR_MIN_TTL_NOT_SUPPORTED
- Time to Live greater than zero not supported for transport type DIRECT.
Explanation:
A time to live that is not valid was specified when using DirectIP transport.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_EXP_NOT_SUPPORTED
public static final java.lang.String MQJMS_DIR_MIN_EXP_NOT_SUPPORTED
- A Topic Expiry greater than zero not supported for transport type DIRECT.
Explanation:
An Expiry time that is not valid was specified when using DirectIP transport.
User Response:
- See Also:
- Constant Field Values
MQJMS_DIR_MIN_ACK_NOT_SUPPORTED
public static final java.lang.String MQJMS_DIR_MIN_ACK_NOT_SUPPORTED
- Client Acknowledge is not supported for transport type DIRECT.
Explanation:
Client Acknowledge mode was requested when creating a session. This is not
supported with a DirectIP transport type.
User Response:
- See Also:
- Constant Field Values