Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of tabish121@gmail.com
 designates 209.85.212.51 as permitted sender)
Message-ID: <1360000184.2717.1.camel@OfficePC>
Subject: Re: Regarding the transport timeout with CMS
From: Timothy Bish <tabish121@gmail.com>
To: users@activemq.apache.org
Date: Mon, 04 Feb 2013 12:49:44 -0500
In-Reply-To: <1359971706419-4662706.post@n4.nabble.com>
References: <1359707991055-4662612.post@n4.nabble.com>
	 <1359971706419-4662706.post@n4.nabble.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Mon, 2013-02-04 at 01:55 -0800, Gangadhar Rao wrote:
> I tried with the below option
> 
> std::string brokerURI =
> "failover://(tcp://10.29.9.229:61617)?wireFormat=openwire&transport.timeout=3000";
> 

Sorry was thinking of the wrong client lib, for CMS it should be this.

"failover://(tcp://10.29.9.229:61617)?timeout=3000";

There's no reason to add the wireformat option as openwire is the
default.

> Scenario:
> 
> 1) Made the activemq broker down....
> 2) Started the producer process...
> 
> It was waiting on the connection start function..I expected that the
> connection would fail after 3000 milliseconds, but that is not happening....
> 
> Thread 1 (Thread 0x2b9ebe6133a0 (LWP 5268)):
> #0  0x0000003cce20b150 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
> /lib64/libpthread.so.0
> #1  0x00002b9ebdb39db8 in
> decaf::internal::util::concurrent::ConditionImpl::wait(decaf::util::concurrent::ConditionHandle*,
> long long, long long) () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #2  0x00002b9ebda3fcce in
> activemq::transport::failover::FailoverTransport::oneway(decaf::lang::Pointer<activemq::commands::Command,
> decaf::util::concurrent::atomic::AtomicRefCounter> const&) () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #3  0x00002b9ebda19c9a in
> activemq::transport::correlator::ResponseCorrelator::request(decaf::lang::Pointer<activemq::commands::Command,
> decaf::util::concurrent::atomic::AtomicRefCounter> const&) () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #4  0x00002b9ebd959223 in
> activemq::core::ActiveMQConnection::syncRequest(decaf::lang::Pointer<activemq::commands::Command,
> decaf::util::concurrent::atomic::AtomicRefCounter>, unsigned int) () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #5  0x00002b9ebd95b507 in
> activemq::core::ActiveMQConnection::ensureConnectionInfoSent() () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #6  0x00002b9ebd95baac in activemq::core::ActiveMQConnection::start() ()
> from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #7  0x000000000040441c in SimpleProducer::run() ()
> #8  0x0000000000402dbf in main ()
> 
> 
> Please advice how we get the CMS Exception in the above scenario.....
> 
> 
> 
> 
> 
> 
> 
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Regarding-the-transport-timeout-with-CMS-tp4662612p4662706.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com 
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/