[rzd]

Hi Markus,

I would sum things up as follows:

1. Setting the transacted parameter to true means you want to manually commit or roll back the session.
2. Forgetting to do so before you close the connection rolls the message back... it would be much clearer, if then a waring was logged.
3. Setting that parameter in a Java EE environment (as Stephen Coy cited the EJB spec) should have no effect. It does, so that's a bug and no TCK seems to check that! I'll address that to the JMS 2.0 EG.
4. Using an XA or non-XA connection factory should influence the distribution of the transaction between JMS and e.g. your database, but not that you sudently have to call commit on the session! I think that's the same bug.

Regards

Rüdiger

[markusdöring]

Hello,

I'm back from vacation, so here are my thoughts:

@Jeremy Whiting (configuration):

good to know, would be nice if this would be the standard configuration of JBoss 7.1.0, so users that used java:/ConnectionFactory don't have to search for the right configuration for ages, "old code" just works the same way then before.

@Rüdiger zu Dohna (sum up):

Yes, I see it the same way.

As far as I understand, all these things (except the Log.warn) are achived out of the box with the configuration jeremy posted.

Didn't had time to test everything with this configuration and with java:/ConnectionFactory but Java:/JmsXA is using same configuration so it should be ok, and I hope to test this later and post testing reults here.

Regards

Markus