On Fri, 2010-04-23 at 00:40 -0800, andrei4002 wrote: > hello > > i'm trying to handle a connection to a broker, using the new 0.6 release (in > 0.5 i have no problems) and i get an unhandled exception using > connection.open to a computer which has it's broker stopped (when it's on is > ok) > > the connection.open method does not seem to throw any exceptions when this > happens
More information would be useful here: Sample code which demonstrates the problem would be really useful - perhaps you could create a Jira to track the bug with reproducer code attached. I'm assuming you're using a 0.6 c++ client, being explicit would help. I suppose the version of broker probably doesn't matter as it's stopped. What do you mean by stopped? Do you mean not running at all: as in the service is stopped; or do you mean ^z as in sent the SIGSTOP signal meaning the process is suspended? Your 2 paragraphs seems to be contradictory - Do you get an exception or not? Thanks Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
