[QPID-4934] [Java Client] XASessionImpl creates three AMQP sessions, only one is XA... why?

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.24
• Component/s: JMS AMQP 0-x
• Assignee: Unassigned
• Reporter: Robert Godfrey
• Created: 18/Jun/13 15:35
• Updated: 14/Mar/17 20:07
• Resolved: 18/Jul/14 19:45

Description

XASessionImpl creates three AMQP Sessions...

1) it calls the constructor of the superclass AMQSession_0_10, which does this:

    _qpidConnection = qpidConnection;
    if (name == null)
    {
        _qpidSession = _qpidConnection.createSession(1);
    }
    else
    {
        _qpidSession = _qpidConnection.createSession(name,1);
    }

... this session is not XA.

2. Immediately after calling the super's constructor it calls createSession() which does this:

    _qpidDtxSession = getQpidConnection().createSession(0,true);
    _qpidDtxSession.setSessionListener(this);
    _qpidDtxSession.dtxSelect();

this session is XA

3. Finally if you call getSession(), getQueueSession() or getTopicSession(), it creates a third (non-XA) session

    public Session getSession() throws JMSException
    {
        if (_jmsSession == null)
        {
            _jmsSession = getAMQConnection().createSession(true, getAcknowledgeMode());
        }
        return _jmsSession;
    }

Why do we need three separate sessions, with two of them being non-XA?