Regarding the issue,
Any reason for defining both and using them?
14:17:13.101 [xaQueueListener-4] INFO c.a.jms.AtomikosJmsNonXaSessionProxy - atomikos non-xa session proxy
for vendor instance com.tibco.tibjms.TibjmsxSessionImp@1549ceb: WARNING - detected JTA transaction context
while using non-transactional session.
instead just use com.tibco.tibjms.TibjmsXAQueueConnectionFactory
<bean id="jmsConnection" class="com.tibco.tibjms.TibjmsQueueConnectionFactory"
<bean id="xaJmsConnection" class="com.tibco.tibjms.TibjmsXAConnectionFactory"
What poller are you referring to? You have a message-driven-channel-adapter which doesn't require a poller sub element. The transaction are demarcated by the transaction-manager attribute or the one confugured with the container in your case.
I can't start transaction without poller. Is It correct behaviour or my configuration mistake?
Below is the line from the documentation regarding message-driven-channel-adapter
Are things working as you are expecting them to, or you still are facing problems?
The poller sub-element is not applicable for a message-driven Channel Adapter, as it will be actively invoked.