> Problem
>
> 1. The JMSContainerInvoker looksup JNDI to find
> the (Topic/Queue)ConnectionFactory from which it
> creates a (Topic/Queue)Connection.
> 2. The JMSContainerInvoker never checks if the
> ConnectionFactory is XA compliant i.e is instanceof
> XATopicConnectionFactory/XAQueueConnectionFactory
> 3. This means that irrespective of the type of
> ConnectionFactory(XA/non XA) registered in JNDI the
> JMSContainerInvoker always creates a
> (Topic/Queue)Connection and never an XATopicConnection
> or XAQueueConnection. i.e
> createXATopicConnection()/createXAQueueConnection() is
> never called.
This has been fixed.
> 4. When the created (non-XA) connection is passed
> into org.jboss.jms.asf.StdServerSessionPoolFactory
> it is used to create a StdServerSessionPool which
> cribs by giving this elegant message
>
> "WARNING: Using a non-XA TopicConnection. It will not
> be able to participate in a Global UOW"
>
> (StdServerSessionPool.java" line 178)
It will still complain. Perhaps that should be moved to a lower priority
message?
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
