Release 2 (9.2)
Part Number A96587-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Application Developer's Guide - Advanced Queuing Release 2 (9.2) Part Number A96587-01 |
|
A list of error messages is provided to aid you in troubleshooting problems.
Cause: The delivery mode is not supported
Action: The valid delivery mode is AQjmsConstants.PERSISTENT
Cause: This feature is not supported in the current release
Action: Self-explanatory
Cause: The message payload was null
Action: Specify a non-null payload for the message
Cause: AQjmsAgent object was null
Action: Specify a valid AQjmsAgent representing the remote subscriber
Cause: There is already one open JMS session on the connection. Cannot have more than one open session on a connection
Action: Close the open session and then open a new one
Cause: The specified operation is not allowed on this object
Action: Self-explanatory
Cause: There was a mismatch between the message type being used and the payload type specified for the destination
Action: Use the message type that maps to the payload specified for the queue table that contains this destination
Cause: The specified class was not found
Action: Make sure your CLASSPATH contains the class
Cause: An attempt was made to update a read-only message header field or property
Action: Self-explanatory
Cause: The connection object was null
Action: Specify a non-null JDBC connection
Cause: The JDBC connection is invalid
Action: Specify a non-null oracle JDBC connection
Cause: An attempt was made to receive messages on a connection that is in stopped state
Action: Start the connection
Cause: An attempt was made to use a Connection that has been closed
Action: Create a new connection
Cause: An attempt was mode to use a Consumer that has been closed
Action: Create a new Message Consumer
Cause: Subscriber name was null
Action: Specify a non-null subscription name
Cause: An error occurred while converting the property to the requested type
Action: Use the method corresponding to the property data type to retrieve it
Cause: The property value specified is invalid
Action: Use the appropriate type of value for the property being set
Cause: An error occurred while receiving the message
Action: See message inside the JMSException and linked SQLException for more information
Cause: A null AQjmsDestinationProperty was specified while creating a queue/topic
Action: Specify a non-null AQjmsDestinationProperty for the destination
Cause: Internal error occurred
Action: Call Support
Cause: An invalid interval was specified
Action: The interval must be greater than 30 seconds
Cause: Invalid dequeue mode was specified
Action: Valid Dequeue modes are AQConstants.DEQUEUE_BROWSE, AQConstants.DEQUEUE_REMOVE, AQConstants.DEQUEUE_LOCKED, AQConstants.DEQUEUE_REMOVE_NODATA
Cause: An invalid Queue object was specified
Action: Specify a valid Queue handle
Cause: An invalid Topic object was specified
Action: Specify a valid Topic handle
Cause: An invalid destination object was specified
Action: Specify a valid destination (Queue/Topic) object
Cause: An invalid navigation mode was specified
Action: The valid navigation modes are AQjmsConstants.NAVIGATION_FIRST_MESSAGE, AQjmsConstants.NAVIGATION_NEXT_MESSAGE, AQjmsConstants.NAVIGATION_NEXT_TRANSACTION
Cause: There was a mismatch between the message type being used and the payload type specified for the destination
Action: Use the message type that maps to the payload specified for the queue table that contains this destination. For ADT messages, use the appropriate CustomDatum factory to create the message consumer
Cause: An attempt was made to get a AQ multi-consumer queue as a JMS queue
Action: JMS queues cannot be multi-consumer enabled
Cause: An attempt was made to use a session that has been closed
Action: Open a new session
Cause: Maximum number of user defined properties for the message has been exceeded
Action: Self-explanatory
Cause: Message specified was null
Action: Specify a non-null message
Cause: Queue or Queue table Name specified was null
Action: Specify a non-null name
Cause: The specified driver is not supported
Action: Valid drivers are oci8 and thin. To use the kprb driver get the kprb connection using getDefaultConnection() and use the static createTopicConnection and createQueueConnection methods
Cause: A CustomDatumFactory was specified for consumers on destinations not containing ADT payloads
Action: This field must be set to null for destinations containing payloads of type SYS.AQ$_JMS_TEXT_MESSAGE, SYS.AQ$_JMS_BYTES_MESSAGE, SYS.AQ$_JMS_MAP_MESSAGE, SYS.AQ$_JMS_OBJECT_MESSAGE, SYS.AQ$_JMS_STREAM_MESSAGE
Cause: CustomDatumFactory was not specified for destinations containing ADT payloads
Action: For destinations containing ADT messages, a CustomDatumFactory for a java class that maps to the SQL ADT type of the destination must be specified
Cause: An attempt was made to use a producer that has been closed
Action: Create a new Message Producer
Cause: Property name was null
Action: Specify a non-null property name
Cause: Invalid system property name specified.
Action: Specify one of the valid JMS system properties
Cause: An attempt was made to create a JMS topic in a single-consumer queue table
Action: JMS topics can only be created in queue tables that are multi-consumer enabled
Cause: Null queue was specified
Action: Specify a non-null queue
Cause: An attempt was made to create a JMS queue in a multi-consumer queue table
Action: JMS queues can only be created in queue tables that are not multi-consumer enabled
Cause: The recipient list specified was empty
Action: Specify a recipient list with at least one recipient
Cause: An error occurred while registering the type in the type map
Action: Self-explanatory
Cause: The ReplyTo destination object type is invalid
Action: The ReplyTo destination must be of type AQjmsAgent
Cause: The property name is greater than the maximum size
Action: Specify a property name that is less than 100 characters
Cause: Subscriber specified was null
Action: Specify a non-null subscriber
Cause: An attempt was made to use a property that is not supported
Action: Self-explanatory
Cause: Topics cannot be of type AQjmsConstants.EXCEPTION
Action: Specify topics to be of type AQjmsConstants.NORMAL
Cause: The type of the value specified does not match the type defined for the system property being set
Action: Use the correct type for the setting the system property
Cause: The sequence deviation is invalid
Action: Valid values are AQEnqueueOption.DEVIATION_BEFORE, AQEnqueueOption.DEVIATION_TOP
Cause: An error occurred in the AQ java layer
Action: See the message inside the JMSException and the linked exception for more information
Cause: Class specified is invalid
Action: Make sure your CLASSPATH has the specified class
Cause: IO exception
Action: See message is JMSException for details
Cause: SQL Exception
Action: See message inside linked SQLException for details
Cause: The selector specified is either invalid or too long
Action: Check the syntax of the selector
Cause: EOF exception occurred while reading the byte stream
Action: Self-explanatory
Cause: An error occurred while converting the stream data to specified type
Action: Check the type of data expected on the stream and use the appropriate read method
Cause: Message is in write-only mode
Action: Call the reset method to make the message readable
Cause: Message is in read-only mode
Action: Use the clearBody method to make the message writeable
Cause: Element with specified name was not found in the map message
Action: Self-explanatory
Cause: The property value exceeded the maximum length allowed
Action: Values for JMS defined properties can be a maximum of length of 100, Values for User defined properties can have a maximum length of 2000
Cause: Topic specified was null
Action: Specify a non-null topic
Cause: Payload factory or Sql_data_class not specified for queues containing object payloads
Action: Specify a CustomDatumFactory or the SQLData class of the java object that maps to the ADT type defined for the queue.
Cause: Both CustomDatumFactory and SQLData class were specified during dequeue
Action: Specify either the CustomDatumFactory or the SQLData class of the java object that maps to the ADT type defined for the queue.
Cause: SQLData class specified is null
Action: Specify the SQLData class that maps to the ADT type defined for the queue
Cause: Invalid payload type in message
Action: Check if the queue is defined to contain RAW or OBJECT payloads and use the appropriate payload type in the message
Cause: More than one queue table matches the query
Action: Specify both owner and queue table name
Cause: The specified queue table was not found
Action: Specify a valid queue table
Cause: This dequeue method cannot be used to dequeue from queues with OBJECT payloads
Action: Use the either dequeue(deq_option, payload_fact) or dequeue(deq_option, sql_data_cl)
Cause: DequeueOption specified is null
Action: Specify a non-null dequeue option
Cause: EnqueueOption specified is null
Action: Specify a non-null enqueue option
Cause: This method cannot be used to dequeue from queues with RAW payload
Action: Use the dequeue(deq_option) method
Cause: The queue name specified is null or invalid
Action: Specify a queue name that is not null. The queue name must not be qualified with the schema name. The schema name must be specified as the value of the owner parameter
Cause: The queue table name specified is null or invalid
Action: Specify a queue table name that is not null. The queue table name must not be qualified with the schema name. The schema name must be specified as the value of the owner parameter
Cause: Queue type is invalid
Action: Valid types are AQConstants.NORMAL or AQConstants.EXCEPTION
Cause: Invalid value for wait type
Action: Wait time can be AQDequeueOption.WAIT_FOREVER, AQDequeueOption.WAIT_NONE or any value greater than 0
Cause: More than one queue matches query
Action: Specify both the owner and name of the queue
Cause: No AQDriver registered
Action: Make sure that the AQ java driver is registered. Use Class.forName("oracle.AQ.AQOracleDriver")
Cause: The queue object is invalid
Action: The underlying JDBC connection may have been closed. Get the queue handle again
Cause: AQQueueProperty specified is null
Action: Specify a non-null AQQueueProperty
Cause: QueueTableProperty specified is null
Action: Specify a non-null AQQueueTableProperty
Cause: Queue Table specified is null
Action: Specify a non-null queue table
Cause: The queue table object is invalid
Action: The underlying JDBC connection may have been closed. Get the queue table handle again
Cause: The byte array given is too small to hold the data requested
Action: Specify a byte array that is large enough to hold the data requested or reduce the length requested
Cause: The specified queue was not found
Action: Specify a valid queue
Cause: The class specified does not support the java.sql.SQLData interface
Action: Self-explanatory
Cause: Visibility value specified is invalid
Action: Valid values areAQConstants.VISIBILITY_ONCOMMIT, AQConstants.VISIBILITY_IMMEDIATE
Cause: An attempt was made to create a JMS queue with RAW payload
Action: JMS queues/topics cannot contain RAW payload
Cause: Session object is invalid
Action: The underlying JDBC connection may have been closed. Create a new session
Cause: Invalid object type specified
Action: Object must implement CustomDatum or SQLData interface
Cause: There is already an open QueueBrowser for this queue on this session
Action: There cannot be more than one queue browser for the same queue in a particular session. Close the existing QueueBrowser and then open a new one
Cause: Address field is null for remote subscriber
Action: The address field must contain the fully qualified name of the remote topic
Cause: The client tried to use a message consumer to receive messages when the session message listener was set.
Action: Use the session's message listener to consume messages. The consumer's methods for receiving messages must not be used.
Cause: Listener Registration failed
Action: See error message in linked Exception for details
Cause: Destination is null
Action: Specify a non-null destination
Cause: One or more elements in the recipient list are null
Action: All AQjmsAgents in the recipient list must be specified
Cause: An error occurred while removing the registration of the consumer with the database for asynchronous receipt
Action: Check error message in linked exception for details
Cause: Null Payload Factory was specified
Action: Specify a non null payload factory
Cause: JNI Error
Action: Check error message in linked exception for details
Cause: Naming exception
Action: Check error message in linked exception for details
Cause: An error occurred in the XA layer
Action: See the message inside the linked XAException for more information
Cause: An error occurred in the JMS layer
Action: See the message inside the linked JMSException for more information
Cause: An error occurred in the XML SQL layer
Action: See the message inside the linked AQxmlException for more information
Cause: An error occurred in the XML SAX layer
Action: See the message inside the linked AQxmlException for more information
Cause: An error occurred in the XML Parser layer
Action: See the message inside the linked AQxmlException for more information
Cause: Connection to the database no longer available.
Action: Comment: This may happen if the database/network/machine is not accessible. This may be a transient failure.
Cause: A free physical database connection was not available in the OCI connection pool in order to perform the specified operation.
Action: Try performing the operation later
Cause: A null Destination name was specified
Action: Specify a non-null destination name
Cause: The specified class was not found
Action: Make sure your CLASSPATH contains the class specified in the error message
Cause: IO exception
Action: See the message inside the linked AQxmlException for more information
Cause: An error occurred in the XML Parser layer
Action: See the message inside the linked AQxmlException for more information
Cause: An error occurred in the XML SAX layer
Action: See the message inside the linked AQxmlException for more information
Cause: An error occurred in the JMS layer
Action: See the message inside the linked JMSException for more information
Cause: The specified operation is not allowed on this object
Action: Check that the user performing the operation has the required privileges
Cause: An error occurred while converting the property to the requested type
Action: Use the method corresponding to the property data type to retrieve it
Cause: Element with specified name was not found in the map message
Action: Specify a valid element name
Cause: An error occurred in the JDBC SQL layer
Action: See the message inside the linked SQLException for more information
Cause: An invalid body string or document was specified
Action: Specify a non-null body string or document for the payload
Cause: An invalid username/password was specified
Action: Specify a non-null username and password
Cause: The autocommit flag cannot be set for this operation
Action: Do not set the autocommit flag
Cause: A null Destination owner was specified
Action: Specify a non-null destination name
Cause: Visibility value specified is invalid
Action: Valid values are AQxmlConstants.VISIBILITY_ONCOMMIT, AQxmlConstants.VISIBILITY_IMMEDIATE
Cause: Invalid dequeue mode was specified
Action: Valid Dequeue modes are AQxmlConstants.DEQUEUE_BROWSE, AQxmlConstants.DEQUEUE_REMOVE, AQxmlConstants.DEQUEUE_LOCKED, AQxmlConstants.DEQUEUE_REMOVE_NODATA
Cause: An invalid navigation mode was specified
Action: The valid navigation modes are:
AQxmlConstants.NAVIGATION_FIRST_MESSAGE
AQxmlConstants.NAVIGATION_NEXT_MESSAGE
AQxmlConstants.NAVIGATION_NEXT_TRANSACTION
Cause: Invalid value for wait type
Action: Wait time can be AQDequeueOption.WAIT_FOREVER, AQDequeueOption.WAIT_NONE, or any value greater than 0
Cause: A null or invalid ConnectionPoolDataSource was specified
Action: Specify a valid OracleConnectionPoolDataSource object with the correct URL and user/password
Cause: An invalid cache_size was specified
Action: Cache size must be greater than 0
Cause: An invalid cache scheme was specified
Action: The valid cache schemes are:
OracleConnectionCacheImpl.DYNAMIC_SCHEME
OracleConnectionCacheImpl.FIXED_WAIT_SCHEME
Cause: An invalid tag was encountered in the XML document
Action: Verify that the XML document conforms to the AQ schema
Cause: An invalid value was specified
Action: Verify that the value specified in the XML document conforms to those specified in the AQ schema
Cause: The message header specified is null or invalid
Action: Specify a valid message header
Cause: Property name was null
Action: Specify a non-null property name
Cause: Invalid property name specified. The property does not exist
Action: The property does not exist
Cause: Subscriber name was null
Action: Specify a non-null subscription name
Cause: Message was null
Action: Specify a non-null message
Cause: Register option is null
Action: Specify a non-null Register Option
Cause: DB Link is null
Action: Specify a non-null Register Option
Cause: Register option is null
Action: Specify a non-null Register Option
Cause: Status option is null
Action: Specify a non-null Register Option
Cause: User is not authenticated
Action: Check that the user was authenticated by the webserver before connecting to the Servlet
Cause: Data source is null or invalid
Action: Specify a valid data source for connecting to the database
Cause: Schema location is null or invalid
Action: Specify a valid URL for the schema
Cause: An error occurred in the AQ java layer
Action: See the message inside the AQxmlException and the linked exception for more information
Cause: An invalid destination object was specified
Action: Specify a valid destination (Queue/Topic) object
Cause: The AQ agent specified does not map to a database user which has privileges to perform the requested operation
Action: Use dbms_aqadm.enable_db_access to map the agent to a database user with the required queue privileges
Cause: The schema document specified is not valid
Action: Specify a valid URL for the schema document
Cause: The AQ agent mapped to more than one database user in the same session
Action: Map the AQ agent to only one database user. Check the aq$internet_users view for database users that map to this agent.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
