Hello there,
I would like to run the qpid-config python script against the java qpid-server.
When I do something like
python qpid-config add exchange topic MsgServer --durable --sequence
I get
Failed: AuthenticationFailure: sasl negotiation failed: no mechanism agreed
If I was to run the Cpp
Hi Gordon,
Yes, I think I went slightly further -
python qpid-config -b guest/guest@192.168.1.3:5672 add exchange topic MsgServer
--durable --sequence
gives me this
Failed: NotFound: no such queue: qmf.default.topic
I just want to replicate in the java world the setup I have with qpidd.
On 08/21/2012 03:19 PM, laurent.deco...@sungard.com wrote:
Yes, I think I went slightly further -
python qpid-config -b guest/guest@192.168.1.3:5672 add exchange topic
MsgServer --durable --sequence
gives me this
Failed: NotFound: no such queue: qmf.default.topic
Ah, so thats broken already
Hi Laurent,
Do you need to use the qpid-config tool? Can't you configure the
exchanges/queues either in the virtualhosts.xml file or using the JMX
Management Console?
Regards
Jakub
On Tue, Aug 21, 2012 at 4:19 PM, laurent.deco...@sungard.com wrote:
Hi Gordon,
Yes, I think I went slightly
Hi Jakub,
I am using 0.16
Here is something that works ;) I managed to recreate the equivalent to this
call python qpid-config add queue ApexInbound --durable
call python qpid-config bind amq.direct ApexInbound ApexInbound
with the java broker, by adding simply this to the virtualhost.xml
Failed to mention that I'm using java client 0.16.
Roger
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Hard-coded-destination-parameters-prevent-creation-of-Producer-and-Consumer-tp7581160p7581161.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Failed to mention that I'm using java client 0.16.
Roger
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Java-example-Hello-java-throws-NPE-tp7581155p7581162.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
New to qpid. Looking to implement transparent interface to amqp/jms servers.
Currently running Rabbitmq (amqp 0.9.1) and old version of OpenMQ (IMQ) on
Centos 5.2.
Tried to run the packaged examples prior to jumping into integrating with
current code. When I try to run the hello.java example
Trying to connect to pre-existing durable destinations on RabbitMQ. Using
qpid 0.16.
When trying to create a producer of consumer extending the Hello.java
example, the server logs the following:
{amqp_error,precondition_failed,
cannot redeclare exchange 'myExchange' in vhost '/' with
Hi there,
exchanges
exchange
typetopic/type
nameMsgServer/name
durabletrue/durable
sequencetrue/sequence
/exchange
/exchanges
I tried this, and it does not seem
I guess probably the easiest way to see whats going on with the broker
is to use the JMX console ...
http://qpid.apache.org/books/0.16/AMQP-Messaging-Broker-Java-Book/html/Qpid-JMX-Management-Console.html
Why do you assume that it doesn't work - do you get an error in the
client when sending the
I'm running 0.9.1 broker.
By new syntax I assume you mean binding url.
Can you direct me to old syntax.
Roger
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Java-example-Hello-java-throws-NPE-tp7581155p7581168.html
Sent from the Apache Qpid users mailing list archive at
The new syntax is the addressing format.
The old format is BURL which will work with 0-8/0-9 as well.
The hello.properties is using the addressing format.
If you want to use the older format, do the following
BURL:topic://amq.topic?routingkey='test'
The format is described here
Roger is using RabbitMQ for the server side.
As Rajith has already indicated, the Hello example wont work if you want to
use 0-9-1 as the newer address syntax was only implemented for AMQP-0-10
section of the client, but I see from your other emails you have already
figured out the BURL: prefix
On Tue, Aug 21, 2012 at 5:14 PM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
Roger is using RabbitMQ for the server side.
As Rajith has already indicated, the Hello example wont work if you want to
use 0-9-1 as the newer address syntax was only implemented for AMQP-0-10
section of the
We are using rabbitmq which is using 0-9. Don't know if it will ever move to
0-10 - some differences of opinion on AMQP front.
Played around and got burl to work on default exchange.
(BURL:direct:myQueue?routingkey='test')
--
View this message in context:
On Tue, Aug 21, 2012 at 5:21 PM, Roger roger.lefeb...@pason.com wrote:
We are using rabbitmq which is using 0-9. Don't know if it will ever move to
0-10 - some differences of opinion on AMQP front.
Understood.
Played around and got burl to work on default exchange.
On 21 August 2012 16:51, Roger roger.lefeb...@pason.com wrote:
Trying to connect to pre-existing durable destinations on RabbitMQ. Using
qpid 0.16.
When trying to create a producer of consumer extending the Hello.java
example, the server logs the following:
{amqp_error,precondition_failed,
18 matches
Mail list logo
