By the way, I dont have access to more than one machine right now.
Is it practical to set up multiple brokers with clients and servers on the same machine (i.e. localhost), providing the port numbers do not clash? John JohnOldman wrote: > > > I registered on JIRA and submitetd AMQCPP-155 Nate... > > > > nmittler wrote: >> >> Hi John, >> That sounds like the correct use case. Even if it wasn't, it >> shouldn't core dump :) >> >> Would you mind capturing this in a JIRA issue >> (http://issues.apache.org/activemq/browse/AMQCPP >> ) and attaching a sample that causes the problem? >> >> Thanks, >> Nate >> >> On Nov 21, 2007, at 5:52 AM, JohnOldman wrote: >> >>> >>> Hi >>> >>> Using: >>> CMS 2.1.1 >>> ActiveMQ 4.1.1 >>> SUSE 10.2 >>> >>> 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 >>> I know >>> it has been processed by the working server. >>> >>> Now I have tried using createSession with SESSION_TRANSACTED to keep >>> the >>> message in the queue, then calling commit() when the server has >>> finished >>> processing the message, but keep getting core dumps. >>> >>> Is this approach to using SESSION_TRANSACTED / commit() the correct >>> way to >>> be running CMS? >>> >>> Thanks >>> John >>> -- >>> View this message in context: >>> http://www.nabble.com/Problem-changing-from-%22AUTO_ACKNOWLEDGE%22-to-%22SESSION_TRANSACTED%22-tf4849348s2354.html#a13874866 >>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>> >> >> >> > > -- View this message in context: http://www.nabble.com/Problem-changing-from-%22AUTO_ACKNOWLEDGE%22-to-%22SESSION_TRANSACTED%22-tf4849348s2354.html#a13894439 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
