B Oracle JMS and Oracle AQ XML Servlet Error Messages
A list of error messages is provided to aid you in troubleshooting problems.
B.1 Oracle JMS Error Messages
- JMS-101 Invalid delivery mode (string)
-
Cause: The delivery mode is not supported
- JMS-102 Feature not supported (string)
-
Cause: This feature is not supported in the current release
- JMS-104 Message Payload must be specified
-
Cause: The message payload was null
- JMS-105 Agent must be specified
-
Cause: AQjmsAgent object was null
- JMS-106 Cannot have more than one open Session on a JMSConnection
-
Cause: There is already one open JMS session on the connection. Cannot have more than one open session on a connection
- JMS-107 Operation not allowed on (string)
-
Cause: The specified operation is not allowed on this object
- JMS-108 Messages of type (string) not allowed with Destinations containing payload of type (string)
-
Cause: There was a mismatch between the message type being used and the payload type specified for the destination
- JMS-109 Class not found: (string)
-
Cause: The specified class was not found
- JMS-110 Property (string) not writeable
-
Cause: An attempt was made to update a read-only message header field or property
- JMS-111 Connection must be specified
-
Cause: The connection object was null
- JMS-112 Connection is invalid
-
Cause: The JDBC connection is invalid
- JMS-113 Connection is in stopped state
-
Cause: An attempt was made to receive messages on a connection that is in stopped state
- JMS-114 Connection is closed
-
Cause: An attempt was made to use a Connection that has been closed
- JMS-115 Consumer is closed
-
Cause: An attempt was mode to use a Consumer that has been closed
- JMS-116 Subscriber name must be specified
-
Cause: Subscriber name was null
- JMS-117 Conversion failed - invalid property type
-
Cause: An error occurred while converting the property to the requested type
- JMS-119 Invalid Property value
-
Cause: The property value specified is invalid
- JMS-120 Dequeue failed
-
Cause: An error occurred while receiving the message
- JMS-121 DestinationProperty must be specified
-
Cause: A null AQjmsDestinationProperty was specified while creating a queue/topic
- JMS-122 Internal error (string)
-
Cause: Internal error occurred
- JMS-123 Interval must be at least (integer) seconds
-
Cause: An invalid interval was specified
- JMS-124 Invalid Dequeue mode
-
Cause: Invalid dequeue mode was specified
- JMS-125 Invalid Queue specified
-
Cause: An invalid Queue object was specified
- JMS-126 Invalid Topic specified
-
Cause: An invalid Topic object was specified
- JMS-127 Invalid Destination
-
Cause: An invalid destination object was specified
- JMS-128 Invalid Navigation mode
-
Cause: An invalid navigation mode was specified
- JMS-129 Invalid Payload type
-
Cause: There was a mismatch between the message type being used and the payload type specified for the destination
- JMS-130 JMS queue cannot be multi-consumer enabled
-
Cause: An attempt was made to get a AQ multi-consumer queue as a JMS queue
- JMS-131 Session is closed
-
Cause: An attempt was made to use a session that has been closed
- JMS-132 Maximum number of properties (integer) exceeded
-
Cause: Maximum number of user defined properties for the message has been exceeded
- JMS-133 Message must be specified
-
Cause: Message specified was null
- JMS-134 Name must be specified
-
Cause: Queue or Queue table Name specified was null
- JMS-135 Driver (string) not supported
-
Cause: The specified driver is not supported
- JMS-136 Payload factory can only be specified for destinations with ADT payloads
-
Cause: A CustomDatumFactory was specified for consumers on destinations not containing ADT payloads
- JMS-137 Payload factory must be specified for destinations with ADT payloads
-
Cause: CustomDatumFactory was not specified for destinations containing ADT payloads
- JMS-138 Producer is closed
-
Cause: An attempt was made to use a producer that has been closed
- JMS-139 Property name must be specified
-
Cause: Property name was null
- JMS-140 Invalid System property
-
Cause: Invalid system property name specified.
- JMS-142 JMS topic must be created in multi-consumer enabled queue tables
-
Cause: An attempt was made to create a JMS topic in a single-consumer queue table
- JMS-143 Queue must be specified
-
Cause: Null queue was specified
- JMS-144 JMS queue cannot be created in multiconsumer enabled queue tables
-
Cause: An attempt was made to create a JMS queue in a multi-consumer queue table
- JMS-145 Invalid recipient list
-
Cause: The recipient list specified was empty
- JMS-146 Registration failed
-
Cause: An error occurred while registering the type in the type map
- JMS-147 Invalid ReplyTo destination type
-
Cause: The ReplyTo destination object type is invalid
- JMS-148 Property name size exceeded
-
Cause: The property name is greater than the maximum size
- JMS-149 Subscriber must be specified
-
Cause: Subscriber specified was null
- JMS-150 Property not supported
-
Cause: An attempt was made to use a property that is not supported
- JMS-151 Topics cannot be of type EXCEPTION
-
Cause: Topics cannot be of type AQjmsConstants.EXCEPTION
- JMS-153 Invalid System property type
-
Cause: The type of the value specified does not match the type defined for the system property being set
- JMS-154 Invalid value for sequence deviation
-
Cause: The sequence deviation is invalid
- JMS-155 AQ Exception (string)
-
Cause: An error occurred in the AQ java layer
- JMS-156 Invalid Class (string)
-
Cause: Class specified is invalid
- JMS-157 IO Exception (string)
-
Cause: IO exception
- JMS-158 SQL Exception (string)
-
Cause: SQL Exception
- JMS-159 Invalid selector (string)
-
Cause: The selector specified is either invalid or too long
- JMS-160 EOF Exception (string)
-
Cause: EOF exception occurred while reading the byte stream
- JMS-161 MessageFormat Exception: (string)
-
Cause: An error occurred while converting the stream data to specified type
- JMS-162 Message not Readable
-
Cause: Message is in write-only mode
- JMS-163 Message not Writeable
-
Cause: Message is in read-only mode
- JMS-164 No such element
-
Cause: Element with specified name was not found in the map message
- JMS-165 Maximum size of property value exceeded
-
Cause: The property value exceeded the maximum length allowed
- JMS-166 Topic must be specified
-
Cause: Topic specified was null
- JMS-167 Payload factory or Sql_data_class must be specified
-
Cause: Payload factory or Sql_data_class not specified for queues containing object payloads
- JMS-168 Cannot specify both payload factory and sql_data_class
-
Cause: Both CustomDatumFactory and SQLData class were specified during dequeue
- JMS-169 Sql_data_class cannot be null
-
Cause: SQLData class specified is null
- JMS-171 Message is not defined to contain (string)
-
Cause: Invalid payload type in message
- JMS-172 More than one queue table matches query (string)
-
Cause: More than one queue table matches the query
- JMS-173 Queue Table (string) not found
-
Cause: The specified queue table was not found
- JMS-174 Class must be specified for queues with object payloads\n. Use dequeue(deq_option,payload_fact) or dequeue(deq_option, sql_data_cl)
-
Cause: This dequeue method cannot be used to dequeue from queues with OBJECT payloads
- JMS-175 DequeueOption must be specified
-
Cause: DequeueOption specified is null
- JMS-176 EnqueueOption must be specified
-
Cause: EnqueueOption specified is null
- JMS-177 Invalid payload type: Use dequeue(deq_option) for raw payload queues
-
Cause: This method cannot be used to dequeue from queues with RAW payload
- JMS-178 Invalid Queue name - (string)
-
Cause: The queue name specified is null or invalid
- JMS-179 Invalid Queue Table name - (string)
-
Cause: The queue table name specified is null or invalid
- JMS-180 Invalid Queue Type
-
Cause: Queue type is invalid
- JMS-181 Invalid value for wait_time
-
Cause: Invalid value for wait type
- JMS-182 More than one queue matches query
-
Cause: More than one queue matches query
- JMS-183 No AQ driver registered
-
Cause: No AQDriver registered
- JMS-184 Queue object is invalid
-
Cause: The queue object is invalid
- JMS-185 QueueProperty must be specified
-
Cause: AQQueueProperty specified is null
- JMS-186 QueueTableProperty must be specified
-
Cause: QueueTableProperty specified is null
- JMS-187 Queue Table must be specified
-
Cause: Queue Table specified is null
- JMS-188 QueueTable object is invalid
-
Cause: The queue table object is invalid
- JMS-189 Byte array too small
-
Cause: The byte array given is too small to hold the data requested
- JMS-190 Queue (string) not found
-
Cause: The specified queue was not found
- JMS-191 sql_data_cl must be a class that implements SQLData interface
-
Cause: The class specified does not support the java.sql.SQLData interface
- JMS-192 Invalid Visibility value
-
Cause: Visibility value specified is invalid
- JMS-193 JMS queues cannot contain payload of type RAW
-
Cause: An attempt was made to create a JMS queue with RAW payload
- JMS-194 Session object is invalid
-
Cause: Session object is invalid
- JMS-195 Invalid object type: object must implement CustomDatum or SQLData interface
-
Cause: Invalid object type specified
- JMS-196 Cannot have more than one open QueueBrowser for the same destination on a JMS Session
-
Cause: There is already an open QueueBrowser for this queue on this session
- JMS-197 Agent address must be specified for remote subscriber
-
Cause: Address field is null for remote subscriber
- JMS-198 Invalid operation: Privileged message listener set for the Session
-
Cause: The client tried to use a message consumer to receive messages when the session message listener was set.
- JMS-199 Registration for notification failed
-
Cause: Listener Registration failed
- JMS-200 Destination must be specified
-
Cause: Destination is null
- JMS-201 All Recipients in recipient_list must be specified
-
Cause: One or more elements in the recipient list are null
- JMS-202 Unregister for asynchronous receipt of messages failed
-
Cause: An error occurred while removing the registration of the consumer with the database for asynchronous receipt
- JMS-203 Payload Factory must be specified
-
Cause: Null Payload Factory was specified
- JMS-204 An error occurred in the AQ JNI layer
-
Cause: JNI Error
- JMS-205 Naming Exception
-
Cause: Naming exception
- JMS-207 JMS Exception (string)
-
Cause: An error occurred in the JMS layer
- JMS-208 XML SQL Exception
-
Cause: An error occurred in the XML SQL layer
- JMS-209 XML SAX Exception
-
Cause: An error occurred in the XML SAX layer
- JMS-210 XML Parse Exception
-
Cause: An error occurred in the XML Parser layer
- JMS-220 Connection no longer available
-
Cause: Connection to the database no longer available.
- JMS-221 Free physical database connection unavailable in connection pool
-
Cause: A free physical database connection was not available in the OCI connection pool in order to perform the specified operation.
- JMS-222: Invalid Payload factory type
-
Cause: Payload factory should be of CustomDatumFactory or ORADataFactory type.
- JMS-223: Payload factory must be null for destinations with Sys.AnyData payload - use typemap instead
-
Cause: A CustomDatumFactory/ORADataFactory was specifed for consumers on destinations containing SYS.ANYDATA payloads
- JMS-224: Typemap is invalid - must be populated with SQLType/OraDataFactory mappings to receive messages from Sys.AnyData destinations
-
Cause: The typemap of the session is null or empty. For destinations of tpye Sys.AnyData, the typemap must contain OraDataFactory objects for all possible types that may be stored in the queue/topic
- JMS-225: Invalid JDBC driver - OCI driver must be used for this operation
-
Cause: Operations on Sys.AnyData queues/topics are not supported using this JDBC driver
- JMS-226: Header-only Message does not have a body
-
Cause: Header-only message does not have a body; the body cannot be cleared, changed, or queried.
- JMS-227: Illegal attempt to commit on a non transacted JMS Session
-
Cause: Illegal attempt to invoke the commit method on a non transacted JMS Session
- JMS-228: Illegal attempt to rollback on a non transacted JMS Session
-
Cause: Illegal attempt to invoke the rollback method on a non transacted JMS Session
- JMS-229: (string) must be specified
-
Cause: The specified parameter was null
- JMS-230: Illegal operation on durable subscription with active TopicSubscriber
-
Cause: Try to unsubscribe, change or create durable subscription while it has an active TopicSubscriber.
- JMS-231: Consumers on temporary destination must belong to the same
-
Cause: The specified parameter was null
- JMS-232: An invalid user/password was specified for the JMS connection
-
Cause: Invalid user/password specified for connection
- JMS-233: The required subscriber information is not available
-
Cause: Try to retrieve subscriber information from a subscriber which was obtained with getDurableSubscriber method and had no corresponding information in the in-memory map.
- JMS-234: This operation is not allowed in the current messaging domain
-
Cause: Perform an operation that is not allowed in the current messaging domain
- JMS-235: Can not link the durable subscriber name with a topic in unsubscribe method.
-
Cause: OJMS is unable to link the supplied durable subscriber name with a topic. This causes unsubscribe method to fail.
- JMS-236: OJMS encountered invalid OCI handles.
-
Cause: OJMS encountered invalid OCI handles when using JDBC OCI driver .
- JMS-237: Can not start thread for message listener.
-
Cause: OJMS is unable to start a new thread for message listener.
- JMS-238: Illegal attempt to recover on a transacted JMS Session
-
Cause: Illegal attempt to invoke the recover method on a transacted JMS Session
- JMS-239: Illegal attempt to call (string) method on a XASession.
-
Cause: Illegal attempt to invoke the commit or rollback method on a XASession
- JMS-240: Illegal attempt to call setClientID after other actions.
-
Cause: Illegal attempt to call Connection.setClientID method after other actions has been taken on this Connection
- JMS-241: Illegal attempt to delete temporary destination when there are consumers using it.
-
Cause: Illegal attempt to delete temporary destination while there are existing consumers still using it.
- JMS-242: Illegal attempt to enqueue message with both immediate visibility and three phase enqueue process.
-
Cause: Illegal attempt to enqueue message with both immediate visibility and three phase enqueue process.
- JMS-243: Topic (string) not found}
-
Cause: The specified topic was not found
B.2 Oracle AQ XML Servlet Error Messages
- JMS-400 Destination name must be specified
-
Cause: A null Destination name was specified
- JMS-402 Class not found: {0}
-
Cause: The specified class was not found
- JMS-403 IO Exception {0}
-
Cause: IO exception
- JMS-404 XML Parse Exception
-
Cause: An error occurred in the XML Parser layer
- JMS-405 XML SAX Exception
-
Cause: An error occurred in the XML SAX layer
- JMS-406 JMS Exception {0}
-
Cause: An error occurred in the JMS layer
- JMS-407 Operation not allowed on {0}
-
Cause: The specified operation is not allowed on this object
- JMS-408 Conversion failed - invalid property type
-
Cause: An error occurred while converting the property to the requested type
- JMS-409 No such element
-
Cause: Element with specified name was not found in the map message
- JMS-410 XML SQL Exception
-
Cause: An error occurred in the JDBC SQL layer
- JMS-411 Payload body cannot be null
-
Cause: An invalid body string or document was specified
- JMS-412 Byte conversion failed
-
Cause: An invalid username/password was specified
- JMS-413 Autocommit not allowed for operation
-
Cause: The autocommit flag cannot be set for this operation
- JMS-414 Destination owner must be specified
-
Cause: A null Destination owner was specified
- JMS-415 Invalid Visibility value
-
Cause: Visibility value specified is invalid
- JMS-416 Invalid Dequeue mode
-
Cause: Invalid dequeue mode was specified
- JMS-417 Invalid Navigation mode
-
Cause: An invalid navigation mode was specified
- JMS-418 Invalid value for wait_time
-
Cause: Invalid value for wait type
- JMS-419 Invalid ConnectionPoolDataSource
-
Cause: A null or invalid ConnectionPoolDataSource was specified
- JMS-420 Invalid value for cache_size
-
Cause: An invalid cache_size was specified
- JMS-421 Invalid value for cache_scheme
-
Cause: An invalid cache scheme was specified
- JMS-422 Invalid tag - {0}
-
Cause: An invalid tag was encountered in the XML document
- JMS-423 Invalid value
-
Cause: An invalid value was specified
- JMS-424 Invalid message header
-
Cause: The message header specified is null or invalid
- JMS-425 Property name must be specified
-
Cause: Property name was null
- JMS-426 Property does not exist
-
Cause: Invalid property name specified. The property does not exist
- JMS-427 Subscriber name must be specified
-
Cause: Subscriber name was null
- JMS-428 Valid message must be specified
-
Cause: Message was null
- JMS-429 Register Option must be specified
-
Cause: Register option is null
- JMS-430 Database Link must be specified
-
Cause: DB Link is null
- JMS-431 Sequence Number must be specified
-
Cause: Register option is null
- JMS-432 Status must be specified
-
Cause: Status option is null
- JMS-433 User not authenticated
-
Cause: User is not authenticated
- JMS-434 Invalid data source
-
Cause: Data source is null or invalid
- JMS-435 Invalid schema location
-
Cause: Schema location is null or invalid
- JMS-436 AQ Exception
-
Cause: An error occurred in the AQ java layer
- JMS-437 Invalid Destination
-
Cause: An invalid destination object was specified
- JMS-438 AQ agent {0} not mapped to a valid database user
-
Cause: The AQ agent specified does not map to a database user which has privileges to perform the requested operation
- JMS-439 Invalid schema document
-
Cause: The schema document specified is not valid
- JMS-440 Invalid operations - agent {0} maps to more than one database user
-
Cause: The AQ agent mapped to more than one database user in the same session
- JMS-441: {0} cannot be null
-
Cause: The specified parameter was null
- JMS-442: Name and Address for Agent cannot be null
-
Cause: Both the name and address parameters were specified as null
- JMS-443: IMMEDIATE visibility mode not supported for this queue/topic
-
Cause: IMMEDIATE visibility mode not supported for JMS type queue/topic
- JMS-444: This feature is not supported yet
-
Cause: The requested feature is not yet supported
- JMS-445: Destination alias must be specified
-
Cause: A null Destination alias was specified
- JMS-446: Agent alias must be specified
-
Cause: A null Agent alias was specified
- JMS-447: error in accessing LDAP server
-
Cause: error in accessing the LDAP server
- JMS-448: Invalid Content-Type
-
Cause: Invalid Content-Type