EJB with CMT sending JMS message

[Nicki Carstensen]

Hi all,

I have a problem with container managed transactions in a stateless session bean sending a jms message.
It seems i can't include my JMS session in the transaction.

Here's the code:

@Resource(mappedName = "ConnectionFactory")
private QueueConnectionFactory connectionFactory;

@Resource(mappedName = "queue/OutboundOrders")
private Queue orderQueue;

@TransactionAttribute(TransactionAttributeType.REQUIRED)
public void enqueueOrder(OrderLineEntity orderLine, Queue orderQueue){
	//Do stuff

	QueueConnection connection = connectionFactory.createQueueConnection();
	QueueSession session = connection.createQueueSession(true, 0);
	ObjectMessage message = session.createObjectMessage();
	message.setObject(orderLine);
	QueueSender sender = session.createSender(orderQueue);
	sender.send(message);
	session.close();
	connection.close();

	//Do other stuff
}

Problem is that no message ends up on the queue when the enqueueOrder method completes, and i would expect the container to commit the transaction. Method completes ok without throwing any exceptions.

However if I change to:

connection.createQueueSession(false, 0);

the message is placed on the queue when the send(message) call completes. But that means the jms session is not part of the EJB transaction.

My app-server is JBoss5.1, and there are no consumers on the queue.

I'm probably missing something blindingly obvious, but i just can't spot it. Any help appreciated.

[Michal Nalewajko]

Hi,

you should commit the session when it is transacional.

sender.send(message);  
session.commit();
session.close(); 

[Nicki Carstensen]

Hi Michael,

Thanks for your tip, you are correct, if i call session.commit(); the message ends up on the queue.

But that confuses me .
I thought that when using

	@Resource(mappedName = "ConnectionFactory")
	private QueueConnectionFactory connectionFactory;

in a JEE container, the application server would create a resource adapter that wraps the real jms connection, enabling container managed transactions.

Please enlighten me if I'm wrong.

[Nicki Carstensen]

Found the solution!

JBoss provides resource adapter for JMS at java:/JmsXA, not at java:/ConnectionFactory in JNDI.

Here is the changed code:

	@Resource(mappedName = "java:/JmsXA")
	private QueueConnectionFactory connectionFactory;

Rest is still the same:

@Resource(mappedName = "queue/OutboundOrders")
private Queue orderQueue;

@TransactionAttribute(TransactionAttributeType.REQUIRED)
public void enqueueOrder(OrderLineEntity orderLine, Queue orderQueue){
	//Do stuff

	QueueConnection connection = connectionFactory.createQueueConnection();
	QueueSession session = connection.createQueueSession(true, 0);
	ObjectMessage message = session.createObjectMessage();
	message.setObject(orderLine);
	QueueSender sender = session.createSender(orderQueue);
	sender.send(message);
	session.close();
	connection.close();

	//Do other stuff
}

Messages are now placed on the queue when method completes and container commits transaction.