publish messages and ignore current transaction?

[drcharris]

Is there any way to configure JBossMQ such that the publication of messages will *ignore* any currently active transaction?

The scenario is that we make a call to an EJB method that takes a few minutes to run (we have a long tx timeout), but would like to publish progress messages during the computation for consumption by a client GUI. Problem is that at the moment, the JMS messages don't actually get published until the tx commits (it's all set up with XA connections) and then they all come at once.

I've tried using java:/ConnectionFactory instead of java:/JmsXA to get my connections but that doesn't seem to make any difference. Of course it's quite hard to test in any automated way.

I can't run without a transaction since the side-effects of the method call updates CMPs etc and I want transactional control there - I just want to publish JMS messages in a no-tx way.

Could I set up another ConnectionFactory with no-tx?

[genman]

How do you obtain your QueueSession?
This will create a queue session that is not transacted. (It shouldn't matter if you use java:/JmsXA for this.)

QueueConnection.createQueueSession(false,
QueueSession.AUTO_ACKNOWLEDGE);

(replace Queue with Topic for publishing.)

[drcharris]

Yes that's how we do it (but for Topics).

In fact inside our ejb method we make multiple calls to a convenience method that gets the connection, creates a session, publisher etc, then publishes the message and closes eveything down.

The session is definitely non-transacted in the JMS sense - but that's not the problem. It's the pre-existing JTA transaction that is holding up the messages in the JMS server so they don't get sent until the JTA transaction commits.

I'm at home now so don't have the code - will post tomorrow morning.

[adrian.brock]

If you use java:/JmsXA it will be part of the transaction.
If you use java:/ConnectionFactory it ill not.

Regards,
Adrian

[drcharris]

Yes that's what I thought.

Turns out that we had a threading issue on the client, which is a Delphi-JIntegra program and couldn't handle the callbacks properly so bunched them all up.

Thanks for the help.