QueueSession commits not automatically synchronized with Bea

[svinther]

Hi

As of what I can understand, the default jms behaviour when used in transacted beans is to automatically commit/rollback the QueueSessions used when the beans transactions is committed/rollbacked

But I can seem to get this behaviour working. In the ejbCreate method of a stateless SessionBean I setup a QueueSession like this

 jndiContext = new InitialContext();
 QueueConnectionFactory queueConnectionFactory = (QueueConnectionFactory) jndiContext.lookup("XAConnectionFactory");
 log.debug("QCF: " + queueConnectionFactory);
 Queue queue = (Queue) jndiContext.lookup(ObserverProcessor.QUEUENAME);
 queueConnection = (QueueConnection) queueConnectionFactory.createQueueConnection();
 queueSession = (QueueSession) queueConnection.createQueueSession(true, Session.AUTO_ACKNOWLEDGE);
 log.debug("Created QueueSession. Transacted=" + queueSession.getTransacted() + " / " + queueSession);
 queueSender = queueSession.createSender(queue);

I send a message from a business method, but when the business method is committed, the message is never being sent...

I tried using the XA interfaces as a test, XAQueueSession etc. but here the message is just send out immediately instead.

I have set up a XA DataSource for Postgresql 8.1, that seems to get deployed ok.

I noticed that in the file jms-ds.xml there is an entry like this

 <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
 <tx-connection-factory>
 <jndi-name>JmsXA</jndi-name>
 <xa-transaction/>
 <adapter-display-name>JMS Adapter</adapter-display-name>
 <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
 <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
 <max-pool-size>20</max-pool-size>
 <security-domain-and-application>JmsXARealm</security-domain-and-application>
 </tx-connection-factory>

And when starting jboss it seems to deploy this. Do I need to configure JMS to use that XA Resource adaptor, or am I doing something else wrong.

Im on JBoss 3.2.7

[adrian.brock]

"svinther" wrote:
or am I doing something else wrong.

Yes.

[svinther]

Well I found out that I needed to lookup java:/JmsXA as the ConnectionFactory. I thought I already did that before and got a ClassCast Exception, but I guess I did something else wrong at that time.

So could you please be a little more specifc about what else im doing wrong.

Also I have read this wiki entry http://wiki.jboss.org/wiki/Wiki.jsp?page=MyJMSReceiverCannotSeeADBUpdateMadeInTheSameTransactionAsASend

and understand that 2 phase commits does not guarantee that when the transaction is done, all datasources has completed their commit operations. The wiki entry states that setting the isolation level of the datasource to TRANSACTION_SERIALIZABLE should prevent the problem. So I tried that, but with no luck, the message still gets to the next MDB before entity bean operations gets committed

[adrian.brock]

"svinther" wrote:

So could you please be a little more specifc about what else im doing wrong.

I could but you could also use search and even enable trace logging so we have
a clue what you are talking about.

Your mistakes in the original post.
* Not using pooled transactional jms resource adapter
* Not using said pooled resource as a pool instead allocating resources per ejb instance.

[adrian.brock]

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp
Will help you get better (any) answers.

[svinther]

* Not using pooled transactional jms resource adapter

Is this not fixed this by using java:/JmsXA as connection factory, as configured in my earlier post ?

* Not using said pooled resource as a pool instead allocating resources per ejb instance.

Im confused about where to allocate/free connections, if not to be done in the ejbCreate/ejbRemove methods.
Unless it is ok to allocate them in the business method, and not free them later. Is this allowed/recommended for pooled connections