JMS connector to Oracle Queues (Oracle Advanced Queuing)

The changed jmsConnector class.

The oracle aq support. It provides the JmsOracleAQSupport class.

The way to configure the connector :

<connector name="oracleAQConnector"
className="org.mule.providers.jms.JmsConnector">
<properties>
<property name="specification" value="oracleAQ" />
<property name="username" value="user" />
<property name="password" value="pass" />
<property name="oracleAQHost" value="host" />
<property name="oracleAQDB" value="db" />
<property name="oracleAQPort" value="1521" />
<property name="oracleAQDrivername" value="oci8" />
</properties>
</connector>

Why is the JmsOracleAQSupport needed? Also it contains some hardcoded info -

if (session instanceof XAQueueSession

JmsOracleAQSupport is needed because of the not-very-standard way one gets a reference to a queue.
You can see we have to add the DB schema in the getQueue method.
Here it is hardcoded because until now I have no way of providing this info to the JmsOracleAQSupport class.
One solution is make an alias in the oracle db for this queue so that the schema name is not neccessary.

Note that I have cleaned up stuff a bit. I will shortly introduce a OracleAQConnector which extends jmsConnector.
Still struggling with transaction support though.

Why don't you make the schema name a property of the connector and pass it into the custom OracleJmsSupport in the constructor.

Also this class should extend Jms102bSupport and only override the necessary methods.

Same goes for the connector, but you have done that I think. Something like this will work -

public class OracleJmsConnector extends JmsConnector
{
/* CHANGE BY HENK */
public String oracleAQHost = null;

public String oracleAQDB = null;

public int oracleAQPort;

public String oracleAQDrivername = null;

/* END CHANGE BY HENK */

/*

• (non-Javadoc)
• @see org.mule.providers.UMOConnector#create(java.util.HashMap)
  */
  public void doInitialise() throws InitialisationException {
  initFromServiceDescriptor();
  try {
  //If we have a connection factory, there is no need to initialise
  //the JndiContext
  if (getConnectionFactory() == null) { initJndiContext(); } else { //Set these to false so that the jndiContext //will not be used by the JmsSupport classes setJndiDestinations(false); setForceJndiDestinations(false); }
  /* CHANGE BY HENK */
  setJmsSupport(new OracleJmsSupport(getJndiContext(),
  isJndiDestinations(), isForceJndiDestinations()));

/* END CHANGE BY HENK */
setConnection(createConnection());
} catch (Exception e) { throw new InitialisationException( "Failed to create Jms Connector: " + e.getMessage(), e); }
}

protected ConnectionFactory createConnectionFactory()
throws InitialisationException, NamingException {

try { return AQjmsFactory.getQueueConnectionFactory(oracleAQHost, oracleAQDB, oracleAQPort, oracleAQDrivername); } catch (JMSException e) { throw new InitialisationException( "Unable to get Oracle AQ connectionfactory."); }

}

public String getUsername() { return username; }

public void setUsername(String username) { this.username = username; }

public String getPassword() { return password; }

public void setPassword(String password) { this.password = password; }

public String getOracleAQHost() { return oracleAQHost; }

public void setOracleAQHost(String oracleAQHost) { this.oracleAQHost = oracleAQHost; }

public int getOracleAQPort() { return oracleAQPort; }

public void setOracleAQPort(int oracleAQPort) { this.oracleAQPort = oracleAQPort; }

public String getOracleAQDrivername() { return oracleAQDrivername; }

public void setOracleAQDrivername(String oracleAQDrivername) { this.oracleAQDrivername = oracleAQDrivername; }

public String getOracleAQDB() { return oracleAQDB; }

public void setOracleAQDB(String oracleAQDB) { this.oracleAQDB = oracleAQDB; }

}

Here is the connector that works if you don't use transactions.

updated

Hi,

I have updated the jmsOracleAQSupport class and added the OracleAQConnector.
You can remove the old files.
I resolved the issue with the hardcoded schema.
The OracleAQConnector uses an XAConnection to oracle, but for the moment this does not seem to work. I will have to look into it. One thing I noticed was that for XA transactions to work in oracle, you have to get an Xid. This is something that the transaction manager should do. Tyrex doesn't and I haven't used another manager.

Hi,

what's the status of this?

Ross

It should work. We have a problem with our Oracle 9i installation which has some issues with XA transactions. We will need to patch our server, which is out of my hands. My guess is that the code works if one has a solid installation of oracle 9i or greater.

Hi,
I have checked this code in under a new project in the sandbox called vendor-patches.
This code can be found under oracle-aq/src/java/org/mule/vendor/oracle/aq (note I have changed the package name).

Thanks for submitting this. Please keep it updated if you find any bugs.

Cheers,

Ross