HOW TO: Enqueue a JMS_TEXT_MESSAGE from java to Oracle database Queue

In this example, I've quickly highlighted the JMS (Java Message Service) components with a simple POJO (Plain Old Java Object) for an asynchronous oracle database queue as well as constructing a JMS_TEXT_MESSAGE to the queue.
February 1, 2017

If you haven't already, jump to the blog HOW TO: Create a Oracle AQ Topic JMS message for java delivery, which will be able to assist you in setting up the database, if you haven't already.

Java Message Service (JMS) is the messaging standard to provide the exchanging of messages. Essentially, JMS are a set interfaces that provides a JMS client the ability to facilitate for the enterprise messaging. This also includes the extension to support the operations and features for Advanced Queuing (AQ)

The JMS Text message is sent to an AQ queue. There are other types of JMS messages ('bytes_messages', 'map_message', 'stream_message' etc) though this blog focuses on the text message, which is called SYS.AQ$_JMS_TEXT_MESSAGE.

The code below goes through a similar example though here's a basic JMS TEXT MESSAGE.


Breaking down the SYS.AQ$_JMS_TEXT_MESSAGE

Essentially, the SYS.AQ$_JMS_TEXT_MESSAGE as 4 components, which are highlighted below. the type of JMS_TEXT_MESSAGE components are as follows:

  • HEADER - Header properties in the SYS.AQ$_JMS_HEADER datatype. (Explained in more detail below)
  • TEXT_LEN - It's the size of the message, which it is set automatically. The example above is 29
  • TEXT_VC - The message payload in VARCHAR2 format, if the payload is equal to or less than 4000 bytes. Because the example above is TEXT_LEN is less than 4000 (hence 29), this is populated and not the TEXT_LOB. If it's greater than 4000, this remains null and the TEXT_LOB is populated.
  • TEXT_LOB - The message payload in CLOB (hence the 'LOB' name) format. This is populated if the TEXT_VS is greater than 4000, otherwise it's null


The HEADER value, which is known as the SYS.AQ$_JMS_HEADER datatype, contains the following attributes.

  • REPLYTO - A Destination supplied by a client when a message is sent
  • TYPE - The type of the message
  • USERID - The identity of the user sending the message
  • APPID - The identity of the application sending the message
  • GROUPID - The identity of the message group of which this message is a part; set by the client
  • GROUPSEQ - The sequence number of the message within the group
  • PROPERTIES - Additional message properties in the SYS.AQ$_JMS_USERPROPARRAY datatype
So you have the header information, the size of the message, then either a VC or a LOB (basically a varchar or a BLOB). To populate the TEXT_LOB, you need to ensure the message exceeds 4000 characters. The example below shows an example on how an xml file is populated within the buffer reader and eventually as a message

Example Below:

package com.aptec.iam.idl.client.produceMessage;

import java.sql.SQLException;
import java.util.Properties;

import javax.jms.JMSException;
import javax.jms.MessageProducer;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.Session;
import javax.jms.TextMessage;
import javax.jms.TopicConnection;
import javax.naming.InitialContext;

import oracle.jms.AQjmsFactory;
import oracle.jms.AQjmsSession;

public class OracleAQClient {

	static final String xmlFile = "/Users/danielredfern/Documents/workspace/AQProducerAndConsumer/src/com/aptec/iam/idl/client/xmlExamples/identification.xml";
public static QueueConnection getConnection() {

	Properties p = new Properties();
	p.setProperty("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
	p.setProperty("java.naming.provider.url", "t3://");
	p.setProperty("", "weblogic");
	p.setProperty("", "Password1");
	InitialContext ctx = null;
		ctx = new InitialContext(p);
	}catch(Exception e){
    String hostname = "";
    String oracle_sid = "orcl";
    int portno = 1521;
    String userName = "ORACLEAQJMSUSER";
    String password = "ORACLEAQJMSUSER";
    String driver = "thin";
    QueueConnectionFactory QFac = null;
    QueueConnection QCon = null;
    try {
        // get connection factory , not going through JNDI here
        QFac = AQjmsFactory.getQueueConnectionFactory(hostname, oracle_sid, portno, driver);
        // create connection
        QCon = QFac.createQueueConnection(userName, password);
    } catch (Exception e) {
    return QCo

The identification.xml file contains characters that exceeds 4000 characters, so the VC becomes a BLOB. This is demonstrated when I query queue table, by using the following command:

select msgid, enq_time, enq_uid, q.user_data from queuetable1 q where q_name = 'AQ_MESSAGE_QUEUE_TABLE'

About the author

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as
Follow Daniel on twitter @nervouswiggles


Other Posts

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen


September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups


September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid


September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.

ERROR Caused by 400 Bad Request - invalid_g


September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by 400 Bad Request - invalid_grant



August 29, 2017
Created by: Daniel Redfern
Received the JWT error

Unexpected character ('¾' (code 190)): expected a valid value


June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
E_WARNING Error in file posts.php at line 464: fopen( failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found E_WARNING Error in file posts.php at line 464: fclose() expects parameter 1 to be resource, boolean given

OpenDJ Error - Connect Error Result Code: 91 (Connect Error)


June 5, 2017
Created by: Daniel Redfern
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"

Tomcat NioEndpoint$SocketProcessor.doRun java.lang.NullPointerException error


June 5, 2017
Created by: Daniel Redfern
When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds

IDM ERROR - JDBC repository configured but datasource default was not found


May 23, 2017
Created by: Daniel Redfern
IDM ERROR - JDBC repository configured but datasource default was not found

OpenIDM Issue - javax.crypto.BadPaddingException: Given final block not properly padded


May 23, 2017
Created by: Daniel Redfern
org.forgerock.json.JsonException: org.forgerock.json.crypto.JsonCryptoException: javax.crypto.BadPaddingException: Given final block not properly padded