Can you post a small example of what it was you were trying to do earlier that didnt work?
I haven't used Camel before so if you have a small contained example I can use it would help me look into it further when I get some time. Robbie On 24 September 2012 12:56, Mark Webb <[email protected]> wrote: > I am using : > > Camel 2.10.0 > RabbitMQ 2.8.6 > Qpid 0.18 > OS X 10.7.5 > Maven 3.0.3 > Java 1.7.0_04-ea > > I have gotten an example working with the following connection > factory. Is think its less than optimal since I have to declare the > exchange in the connection factory and cannot send messages to > different endpoints from Camel. > > <bean id="jmsConnectionFactory" > class="org.apache.qpid.client.AMQConnectionFactory" > > <constructor-arg > index="0" type="java.lang.String" > value="amqp://guest:guest@ > /myvhost?brokerlist='tcp://localhost:5672'&defaultTopicExchange=MyExchange" > /> > </bean> > > > > On Mon, Sep 24, 2012 at 7:50 AM, Robbie Gemmell > <[email protected]> wrote: > > I'm not sure QPID-4250 is really the answer here. The exception message > > implies that a non-passive exchange declare was sent for amq.direct, but > I > > believe changes were made for previously in order to prevent that and > stop > > issues specifically like this. QPID-4250 simply fixes choosing to disable > > all the implicit exchange declares, which will certainly help here in its > > own way, but isnt necessarily the answer. > > > > Can I ask what versions of the qpid client and rabbitmq broker are > actually > > in use here? > > > > Robbie > > > > On 24 September 2012 09:26, Gordon Sim <[email protected]> wrote: > > > >> On 09/24/2012 02:30 AM, Mark Webb wrote: > >> > >>> I am working on getting Apache Camel 2.10.0 working with RabbitMQ. > >>> Has anyone gotten this to work, and could you please post your Camel > >>> context route. I am running into problems getting a message to pass > >>> from Camel -> RabbitMQ -> Camel. Here's the error I am currently > >>> running in to: > >>> > >>> Thread-6] AMQConnection INFO Closing AMQConnection > >>> due to :org.apache.qpid.**AMQChannelClosedException: Error: > >>> PRECONDITION_FAILED - cannot redeclare exchange 'amq.direct' in vhost > >>> '/test' with different type, durable, internal or autodelete value > >>> [error code 406: In use] > >>> > >>> I have a vhost defined ("/test") in RabbitMQ and from what I can tell > >>> this error message states that I am trying to change the attributes of > >>> an existing exchange but I'm not, I don't even see where I can do this > >>> or how I would do this. > >>> > >> > >> Unfortunately that is a defect that has come several times in the > past[1]. > >> The good news is that it has at last been fixed on trunk (though not > yet in > >> any released version). See https://issues.apache.org/** > >> jira/browse/QPID-4250 <https://issues.apache.org/jira/browse/QPID-4250>for > details of the change. > >> > >> > >> [1] Most recently in http://mail-archives.apache.** > >> org/mod_mbox/qpid-users/**201208.mbox/%3C1345564311401-** > >> [email protected]%3E< > http://mail-archives.apache.org/mod_mbox/qpid-users/201208.mbox/%[email protected]%3E>where > some of the responses[2][3], may be of interest. > >> > >> [2] http://mail-archives.apache. > **org/mod_mbox/qpid-users/**201208.mbox/%* > >> *3CCAFitrpRwyT0N1pcKLDNiQyrHoj_**2XiXzbhpwO1cRgZjOmyG3Dg@mail.** > >> gmail.com%3E< > http://mail-archives.apache.org/mod_mbox/qpid-users/201208.mbox/%3ccafitrprwyt0n1pckldniqyrhoj_2xixzbhpwo1crgzjomyg...@mail.gmail.com%3E > > > >> > >> [3] http://mail-archives.apache. > **org/mod_mbox/qpid-users/**201208.mbox/%* > >> *3CCAFitrpRtdDn5s5nNb+T-_**OCYxC39WeN-h9C5OMLDjr7eNf4=bg@** > >> mail.gmail.com%3E< > http://mail-archives.apache.org/mod_mbox/qpid-users/201208.mbox/%3CCAFitrpRtdDn5s5nNb+T-_OCYxC39WeN-h9C5OMLDjr7eNf4=b...@mail.gmail.com%3E > > > >> > >> > >> > >> > >> > >> > >> > >> > ------------------------------**------------------------------**--------- > >> To unsubscribe, e-mail: [email protected].**org< > [email protected]> > >> For additional commands, e-mail: [email protected] > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
