JMS QueueConnectionFactory vs ConnectionFactory

java jms jndi mq
bvdb picture bvdb · May 8, 2015 · Viewed 9.2k times · Source

My question is about the use of the following 2 factories:

  • ConnectionFactory
  • QueueConnectionFactory

At the moment I just use a ConnectionFactory to initialize everything:

Connection conn = factory.createConnection(user, pw);
Session session = conn.createSession()
Destination dest = session.createQueue('xyz')
...

If I understand correctly, the QueueConnectionFactory works pretty much the same way. Is it the exact same thing ?

I am wondering especially because I'm using a JNDI context which contains both objects. So, I'm not sure which one I should prefer to use.

Answer

Evgeniy Dorofeev picture Evgeniy Dorofeev · May 8, 2015

javax.jms package API says:

For historical reasons JMS offers four alternative sets of interfaces for sending and receiving messages:

•JMS 1.0 defined two domain-specific APIs, one for point-to-point messaging (queues) and one for pub/sub (topics). Although these remain part of JMS for reasons of backwards compatibility they should be considered to be completely superseded by the later APIs.

•JMS 1.1 introduced a new unified API which offered a single set of interfaces that could be used for both point-to-point and pub/sub messaging. This is referred to here as the classic API.

•JMS 2.0 introduces a simplified API which offers all the features of the classic API but which requires fewer interfaces and is simpler to use.

Each API offers a different set of interfaces for connecting to a JMS provider and for sending and receiving messages. However they all share a common set of interfaces for representing messages and message destinations and to provide various utility features.

In other words QueueConnectionFactory is simply a legacy interface

Related questions

Why is my JNDI lookup for a QueueConnectionFactory returning null?

I am trying to look up a QueueConnectionFactory and Queue via Geronimo's JNDI. The Queue gets returned fine, but the QueueConnectionFactory lookup always returns null. It doesn't throw a NamingException, which is what I'd expect if the JNDI name was …

Read More
How does the JNDI lookup work in this JMS example?

I am having a hard time to understand the JNDI part of the following JMS example. public static void main(String[] args) { try { // Gets the JNDI context Context jndiContext = new InitialContext(); // Looks up the administered objects ConnectionFactory connectionFactory = (ConnectionFactory) jndiContext.…

Read More
Differences between javax.jms.ConnectionFactory and javax.jms.XAConnectionFactory

I'm entering the world of JTA, due to need of distributed transactions, and I'm uncertain about the differences between javax.jms.ConnectionFactory and javax.jms.XAConnectionFactory or more accurately how can it be that javax.jms.ConnectionFactory performed what I …

Read More