[
https://issues.apache.org/jira/browse/AMQCPP-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915452#comment-13915452
]
Arthur Naseef commented on AMQCPP-535:
--------------------------------------
So, transactions are not the most reliable form of producing message, as the
JMS spec requires?
> Activemq session commit, not working as expected.
> -------------------------------------------------
>
> Key: AMQCPP-535
> URL: https://issues.apache.org/jira/browse/AMQCPP-535
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 3.8.2
> Reporter: D V Gangadhar Rao
> Assignee: Timothy Bish
>
> Tested with AMQ CMS CPP 3.8.2 client
> Producer has opened the session in SESSION_TRANSACTED mode.
> It has sent a set of messages to the destination activemq broker.
> The producer did a commit on the session, which resulted in only committing
> only a subset of messages in the destination queue and remaining messages are
> not commited in case of a scenario where there was a queue full exception.
> Expected behavior:
> Actually we were expecting that session commit call should either commit the
> whole batch of messages or rollback the entire batch of messages if the queue
> is FULL on the destination broker queue, but it should not commit few
> messages and rollback the other messages.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
