You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2008/01/27 16:19:25 UTC

[jira] Closed: (AMQCPP-155) Problem changing from "AUTO_ACKNOWLEDGE" to "SESSION_TRANSACTED"

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

Timothy Bish closed AMQCPP-155.
-------------------------------

    Resolution: Cannot Reproduce

I cannot reproduce the issue seen in any of my environments.

> Problem changing from "AUTO_ACKNOWLEDGE" to "SESSION_TRANSACTED"
> ----------------------------------------------------------------
>
>                 Key: AMQCPP-155
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-155
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 2.1.1
>         Environment: CMS 2.1.1
> ActiveMQ 4.1.1
> SUSE 10.2
>            Reporter: John Oldman
>            Assignee: Timothy Bish
>            Priority: Blocker
>             Fix For: 2.2
>
>         Attachments: forumBuild.tar.gz
>
>
> Based on the sample code, have set up a simple client/server queue,  
> using createSession with AUTO_ACKNOWLEDGE.
> Messages appear to work as expected.
> However, I want to eventually end up with a failover setup, with two servers, and therefore need to leave the message in the queue until it has been sucessfully processed by the working server.  
> I have tried using createSession with SESSION_TRANSACTED to keep the message in the queue, then calling commit() when the server has completed processing the message, but keep getting core dumps.
>  Is this approach to using SESSION_TRANSACTED / commit() the correct way to be running CMS?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.