[ 
https://issues.apache.org/jira/browse/QPID-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

BrewTany updated QPID-5585:
---------------------------

    Summary: jms transaction not working on 0.26 clusters  (was: jms 
transaction not working on 0.26)

> jms transaction not working on 0.26 clusters
> --------------------------------------------
>
>                 Key: QPID-5585
>                 URL: https://issues.apache.org/jira/browse/QPID-5585
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.26
>         Environment: Broker:C++, 0.26,
> Client: Java ,JMS 1.0
> qpidd.conf:
> load-module=/usr/local/lib64/qpid/daemon/msgstore.so
> data-dir=/tmp/qpidstore
> ha-cluster=yes
> ha-brokers-url=q1,q2
> log-enable=info+
> log-time=yes
> log-thread=yes
> log-to-file=/tmp/qpid.log
> pid-dir=/tmp/qpidpid
> worker-threads=10
> default-queue-limit=1024000000
> auth=no
>            Reporter: BrewTany
>            Priority: Critical
>              Labels: jms, transaction
>
> JMS Transaction timeout on 0.26, 
> here is my codes:
> Session session = connection.createSession(true, Session.SESSION_TRANSACTED);
> TextMessage message = session.createTextMessage(sb
>                                                                       
> .toString());
> messageProducer.send(message);
> session.commit();// timeout
> //
> it works on 0.24 cluster, but failed on 0.26.
> it works on 0.26 single node, but failed on 0.26 cluster nodes.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to