Transacted QueueSession in WLS8.1sp3

Question

I'm migrating a WLS6.1sp6 application to WLS8.1sp3.
          I have a JMSConnectionFactory which does not have XA Connection Factory Enabled but whenever I obtain a reference to it using its JNDI name I always get returned a JMSXAConnectionFactory.
          The knock on effect of this is that createQueueConnection().createQueueSession(true, ...) never returns me a transacted QueueSession.
          I've tried every combination of UserTransactionsEnabled="true/false" XAConnectionFactoryEnabled="true/false" without success.
          Any ideas appreciated.
          Tim

Answer 1

Tom,
          A question on this. If I do not specify any connection factory in the weblogic-ejb-jar.xml, how does the container/MDB know, which connection factory to use for getting connection to the desitnation?
          Rohit
          > > I don't understand what the connection between the
          > MDB > and the connection factory is.
          >
          > As per the standard JMS API, all client access to JMS
          > resources requires a JMS connection to a server
          > within the cluster. The client routes JMS requests
          > through this connection. A JMS connection factory
          > is the JMS API's method for creating connections.
          > Once an MDB obtains a connection, it creates a JMS
          > S session using the connection, and then creates a
          > consumer from the session that to receive messages
          > from the MDB's source destination.
          >
          > You can think of a JMS connection factory as being
          > very similar in concept to a JDBC data source. JDBC
          > data sources are looked up in JNDI and are used to
          > create JDBC connections. Furthermore you can think
          > of a "user-transaction-aware" JMS session as similar
          > to an XA capable JDBC connection, and a "transacted"
          > " session as similar to a non-XA JDBC connection that
          > is used for local transactions (transactions scoped
          > to the connection only).
          >
          >
          > > Why does the MDB weblogic-ejb-jar have
          > <connection-
          > > factory-jndi-name>?
          >
          > To (1) allow for different connection factories which
          > may have different configured behaviors or may be
          > targeted to specific WL servers, and (2) to allow the
          > MDB to connect to remote non-WebLogic JMS providers
          > which will not have the same connection factory JNDI
          > name as the default WL JMS connection factory.
          >
          > > Surely any message on queue Q will be processed
          > > regardless of the connection factory it was sent
          > under?
          >
          > Among other things, the JMS connection factory has an
          > explicit role in determining the XA or transacted
          > behavior of JMS clients, it is where such behavior is
          > configured. So, you can generally receive messages
          > using any connection factory, but can't necessarily
          > get the desired XA or transacted capability using any
          > connection factory...
          >
          > Tom