activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: Regarding the transport timeout with CMS
Date Fri, 01 Feb 2013 19:28:43 GMT
On Fri, 2013-02-01 at 00:39 -0800, Gangadhar Rao wrote:
> Hi,
> 
> I started the producer with the below URI
> 
>    std::string brokerURI =
> "failover://(tcp://10.29.9.229:61617?timeout=3000)";

I believe this is the correct URI.

failover://(tcp://10.29.9.229:61617)?transport.timeout=3000


> so while the producer is sending the messages to the broker, I stopped the
> broker....
> 
> So currently it is waiting on the send method.....
> 
> 
> 
> Thread 1 (Thread 0x2ac051de13a0 (LWP 6424)):
> #0  0x0000003cce20b150 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
> /lib64/libpthread.so.0
> #1  0x00002ac051307db8 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  0x00002ac05120dcce 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  0x00002ac0511e5fa1 in
> activemq::transport::correlator::ResponseCorrelator::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
> #4  0x00002ac051121aaf in
> activemq::core::ActiveMQConnection::oneway(decaf::lang::Pointer<activemq::commands::Command,
> decaf::util::concurrent::atomic::AtomicRefCounter>) () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #5  0x00002ac05117223e in
> activemq::core::ActiveMQSession::send(cms::Message*,
> activemq::core::ActiveMQProducer*, activemq::util::Usage*) () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #6  0x00002ac05115f68d in
> activemq::core::ActiveMQProducer::send(cms::Destination const*,
> cms::Message*, int, int, long long) () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #7  0x00002ac05116021b in
> activemq::core::ActiveMQProducer::send(cms::Destination const*,
> cms::Message*) () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #8  0x00002ac05116120e in
> activemq::core::ActiveMQProducer::send(cms::Message*) () from
> /irb/dev2/gdoddi/activemq-cpp-library-3.4.3/src/main/.libs/libactivemq-cpp.so.14
> #9  0x0000000000404699 in SimpleProducer::run() ()
> #10 0x0000000000402dbf in main ()
> 
> *Since I have set the timeout at the transport level, I expected after 3000
> milliseconds a CMS exception would be thrown to the producer.....but I am
> not getting any CMSException....
> *
> 
> Can you please advice, how to get the CMSException being thrown to the
> producer when the broker is down....
> 
> Thanks
> Gangadhar
> 
> 
> 
> 
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Regarding-the-transport-timeout-with-CMS-tp4662612.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/



Mime
View raw message