No. Having a "/" in the exchange name is not allowed by the AMQP 0-x
specification that defined exchanges, it requires they must be formed
of basic A-Z or a-z letters, digits, dash, underscore, colon, or dots.
I believe the "/" was also reserved by the broker itself long l
Hello,
I'm using the Qpid Broker-J docker image version 9.2.1 [1]. I want to add a new
exchange of type topic with the name "/car/bought/customer" via the Broker-J
UI. Unfortunately, this is not working, because I get the error "Illegal or
reserved exchange name!&quo
Hi all,
I have a three-node cluster qpid-j 8.0.6
I create a topic and durable queue with the same name (for example, random
generated Ae8M6kKM) and make a binding. At this stage, I can send and receive
messages.
I move the master node to another server. After that, all messages that I sent
to
Hi Kristofor,
The Qpid Broker-J JSON store does not support storing exchange name as part
of binding attributes. Though, potentially, you can use description field
of binding and save the exchange name there. I am surprised that
non-existing attribute "_comments" is not removed from th
I would like to quickly identify exchange-queue bindings while examining the
raw json.
Currently, I see something similar to this queue definition with binding
block as :
{
"id" :
"name": "queuename",
"type" : "standard"
… (more irrel
our requirements.
>>>>
>>>> Thanks,
>>>> Rob
>>>>
>>>> On Mon, 11 Nov 2019 at 09:33, Rob Godfrey
>>>> wrote:
>>>>
>>>>> Hi Łukasz,
>>>>>
>>>>> firstly let me apologise
t;> Rob
>>>
>>> On Mon, 11 Nov 2019 at 09:33, Rob Godfrey
>>> wrote:
>>>
>>>> Hi Łukasz,
>>>>
>>>> firstly let me apologise for not getting back to you sooner.
>>>>
>>>> Secondly, unfortunately I a
gt;
>> Thanks,
>> Rob
>>
>> On Mon, 11 Nov 2019 at 09:33, Rob Godfrey
>> wrote:
>>
>>> Hi Łukasz,
>>>
>>> firstly let me apologise for not getting back to you sooner.
>>>
>>> Secondly, unfortunately I agree that there i
r.
>>
>> Secondly, unfortunately I agree that there is no current way to
>> explicitly tell the broker to ignore unknown exchange declare arguments,
>> and that adding this ability is a good idea. The simplest approach is
>> probably to add a configurable property t
t;
> firstly let me apologise for not getting back to you sooner.
>
> Secondly, unfortunately I agree that there is no current way to explicitly
> tell the broker to ignore unknown exchange declare arguments, and that
> adding this ability is a good idea. The simplest approach is proba
Hi Łukasz,
firstly let me apologise for not getting back to you sooner.
Secondly, unfortunately I agree that there is no current way to explicitly
tell the broker to ignore unknown exchange declare arguments, and that
adding this ability is a good idea. The simplest approach is probably to
add
Hello,
I'm working on using Qpid broker as an in-memory AMQP message broker, that
will be used in place of RabbitMQ for integration tests of my Java service.
While I managed to successfully run Qpid, I'm having issues with my
RabbitMQ connector library using some RMQ-specific exchan
Hi Alex
Thank you for the link to the docs.
You are right, connecting a fannout exchange to a topic exchange doesn't
make any sense, I realised that by now too. I a mafter the flexibility the
wildcard routing offers, that's the reason I want to use the topics.
So it seems like it com
-connect, the same messages would be sent again. The resuming of
message delivery from the previous point is not supported.
As for fanout exchange, it routes messages into all bound queues and
exchanges regardless message routing key.
I am not sure that you need to use topic exchanges, unless you are
ch of the message routing logic in the
broker as possible.
If I'd use a fannout exchange I would loose the routing behaviour. So
instead of using one, or only a few, topic exchanges, I would have to use
many fannout exchanges, correct? Is any of the two patterns superiour to the
other? At firs
nline again.
>
> I thought I need to create a topic exchange and create one LVQ per
> subscriber, to make sure that each one of them gets the same messages. Is
> that correct, is there a more elegant way then creating n queues?
>
So, firstly, if you want all the messages to go to all th
messages, or at least the last message of
the same value (LVQ). Even if a subscriber was offline, due to updates,
failures, or whatever, it should always receive the messages, once being
online again.
I thought I need to create a topic exchange and create one LVQ per
subscriber, to make sure that
Super, the work around is working.
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apa
On 08/05/2019 9:28 pm, Gordon Sim wrote:
On 08/05/2019 8:18 pm, Michael Ivanov wrote:
I hope this is the right place to ask about qpid jms.
I use qpid jms client 0.41.0 with qpidd broker 1.38.
I'm creating created a fanout exchange (qpid-config add exchange fan ABC)
and subscribe to it
On 08/05/2019 8:18 pm, Michael Ivanov wrote:
I hope this is the right place to ask about qpid jms.
I use qpid jms client 0.41.0 with qpidd broker 1.38.
I'm creating created a fanout exchange (qpid-config add exchange fan ABC)
and subscribe to it from java client using Topic
Hallo,
I hope this is the right place to ask about qpid jms.
I use qpid jms client 0.41.0 with qpidd broker 1.38.
I'm creating created a fanout exchange (qpid-config add exchange fan ABC)
and subscribe to it from java client using Topic and a MessageConsumer.
On server side a queue is cr
to a queue works ok. But the problem is when we try to send
to a exchange.Is there any way to send to an exchange from
qpid-cpp-1.38.0 to rabbitmq broker?
You don't describe what the problem you are having is. To send to an
exchange on rabbitmq via the 1.0 plugin[1] you use the '/exchang
to an exchange from
qpid-cpp-1.38.0 to rabbitmq broker?
You don't describe what the problem you are having is. To send to an
exchange on rabbitmq via the 1.0 plugin[1] you use the '/exchange/'
prefix to the address. The qpid::messaging API treats the '/' as
special, sepa
exchange.Is there any way to send to an exchange from
qpid-cpp-1.38.0 to rabbitmq broker?
Thanks in adavance
Regards
Este correo electrónico y, en su caso, cualquier fichero anexo al mismo,
contiene información de carácter confidencial exclusivamente dirigida a su
d'origine-
> De : Cyril Micoud
> Envoyé : jeudi 15 mars 2018 10:34
> À : users@qpid.apache.org
> Objet : RE: Qpid JMS 0.30.0 or Qpid Proton-J 0.26.0 to point-to-point
> message exchange?
>
> Hi Robbie,
>
> Thanks for your answer, I agree with you on the &quo
ssage
exchange?
Hi Robbie,
Thanks for your answer, I agree with you on the "dynamicQueues/" usage...
But about the VirtualHost/Exchange/Queue management, what is the best way with
Qpid Broker-J 7.0.x? REST api or JMS message or any other solution?
Cyril
-Message d'orig
Hi Robbie,
Thanks for your answer, I agree with you on the "dynamicQueues/" usage...
But about the VirtualHost/Exchange/Queue management, what is the best way with
Qpid Broker-J 7.0.x? REST api or JMS message or any other solution?
Cyril
-Message d'origine-
De :
ssage d'origine-
> De : Rob Godfrey
> Envoyé : mercredi 14 mars 2018 17:19
> À : users@qpid.apache.org
> Objet : Re: Qpid JMS 0.30.0 or Qpid Proton-J 0.26.0 to point-to-point message
> exchange?
>
> On 14 March 2018 at 17:13, Cyril Micoud wrote:
>
>> Thanks G
in that case...
Best regards
Cyril
-Message d'origine-
De : Rob Godfrey
Envoyé : mercredi 14 mars 2018 17:19
À : users@qpid.apache.org
Objet : Re: Qpid JMS 0.30.0 or Qpid Proton-J 0.26.0 to point-to-point message
exchange?
On 14 March 2018 at 17:13, Cyril Micoud wrote:
>
uot; java side.
>
> About JMS, I have seen a link (but where?) to manage VirtualHost, Exchange
> and Queue directly via message, it is always possible with Qpid JMS 0.30.0
> or our only way is the REST api?
>
>
Which broker are you using? Unfortunately there is not yet a s
irtualHost, Exchange and
Queue directly via message, it is always possible with Qpid JMS 0.30.0 or our
only way is the REST api?
Thanks again a ot by advance,
Best regards,
Cyril
-Message d'origine-
De : Gordon Sim
Envoyé : mercredi 14 mars 2018 14:20
À : users@qpid.apache.org
O
On 14/03/18 12:19, Cyril Micoud wrote:
how each system knew the dispatch router?
They just need a host and port; that would be the same even if one was
directly connecting to the other.
-
To unsubscribe, e-mail: users-unsubs
ut dispatch router?
>
> Thanks by advance,
> Bets regards,
>
> Cyril
>
>
> -Message d'origine-
> De : Gordon Sim
> Envoyé : mercredi 14 mars 2018 11:02
> À : users@qpid.apache.org
> Objet : Re: Qpid JMS 0.30.0 or Qpid Proton-J 0.26.0 to point-to-point messa
message
exchange?
On 14/03/18 08:40, Cyril Micoud wrote:
> Hi everybody,
>
> We are working with Qpid to set up interoperability between 2 systems,
> one in Java, the other in C ++.
>
> On the C ++ side, we use Qpid Proton 0.17.0 (not the last update due
> to system con
started on Qpid JMS 0.30.0 for the simplicity of JMS and
compatibility with 1.0 of AMQP.
In the nominal case, we use a Broker, but we also need point-to-point
access to transfer information from one system to another such as the
broker's address and the queues on which we can exc
simplicity of JMS and
compatibility with 1.0 of AMQP.
In the nominal case, we use a Broker, but we also need point-to-point access to
transfer information from one system to another such as the broker's address
and the queues on which we can exchange.
However, connection and exchange with the brok
Yes, I'm using Broker-J 7.0.0.
Thank you for pointing me the nodeAutoCreationPolicies and AMQP Management
protocol.
I tried nodeAutoCreationPolicies, it works but it's not flexible and it
depends on the broker specific condifguration.
AMQP Management protocol looks better, even if it's just a wo
On 31/01/18 13:18, Keith W wrote:
I think Dexter is using Qpid Broker-J.
I do apologise. I saw RabbitMQ and clearly didn't spend enough time
reading before responding!
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.
nd the API will be subject to further (probably
breaking) changes as the specification evolves.
Hope this helps.
On 31 January 2018 at 08:29, Gordon Sim wrote:
> On 30/01/18 23:29, dexter wrote:
>>
>> Hi,
>>
>> I'm trying to create dynamically an exchange type
On 30/01/18 23:29, dexter wrote:
Hi,
I'm trying to create dynamically an exchange type topic and some queues and
bind them with the topic using a bindingKey using the latest Java library
proton-j-0.25.0.jar on a Apache Qpid Broker-J 7.0.0 server.
If the exchange / queues are in place (cr
Hi,
I'm trying to create dynamically an exchange type topic and some queues and
bind them with the topic using a bindingKey using the latest Java library
proton-j-0.25.0.jar on a Apache Qpid Broker-J 7.0.0 server.
If the exchange / queues are in place (created using RabbitMQ library
amqp-c
Yes, that works for me!
Thank-you so much for your help!
On Mon, Dec 11, 2017 at 9:43 PM, Gordon Sim wrote:
> On 09/12/17 02:20, Michael Arnold wrote:
>
>> Thanks for the help - but am still stuck:
>>
>> 1. Added in a link name as follows:
>> string ReceiverAddress = "Topic.Subtopic/Subject; {c
On 09/12/17 02:20, Michael Arnold wrote:
Thanks for the help - but am still stuck:
1. Added in a link name as follows:
string ReceiverAddress = "Topic.Subtopic/Subject; {create: always,
node:{type: topic, durable: true}, link:{reliability: at-least-once,
durable: true, name: subscription-name}}"
QPIDConnection.setOption("protocol", string("amqp1.0"));
Could you please elaborate further?
On Fri, Dec 8, 2017 at 11:31 PM, Gordon Sim wrote:
> On 08/12/17 14:44, Michael Arnold wrote:
>
>> Disconnecting the QPID session that creates a durable topic exch
On 08/12/17 14:44, Michael Arnold wrote:
Disconnecting the QPID session that creates a durable topic exchange (and
thus closing the only open receiver) seems to delete the topic exchange and
its contents - any messages not yet retrieved from the exchange are lost
and any subsequent messages sent
Disconnecting the QPID session that creates a durable topic exchange (and
thus closing the only open receiver) seems to delete the topic exchange and
its contents - any messages not yet retrieved from the exchange are lost
and any subsequent messages sent while no receiver is open, are likewise
I wrote a library to support this type of thing a while ago. I've just
added an example equivalent to Gordon's (there may be some slight
similarities ;) ) to show the retrieval of bindings:
https://github.com/fourceu/fourc-qpid-manager/blob/master/examples/Bindings.cxx
The library hides the compli
nse.getContentObject().asList();
for (Variant::List::const_iterator i = contentIn.begin(); i != contentIn.end(); ++i) {
Variant::Map item = i->asMap();
Variant::Map values = item["_values"].asMap();
std::string queue = getName(values
ace Can't deliver to xxx#_yyy
I looked earlier in the log and it looks like it was able to successfully
create the response queue.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Using-QMF-to-know-about-consumers-in-a-topic-exchange-tp7663510p7663521.html
Sent f
.n2.nabble.com/Using-QMF-to-know-about-consumers-in-a-topic-exchange-tp7663510p7663520.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additio
On 26/05/17 18:09, mottese wrote:
I'm running that test program, but I noticed that I never receive a response.
I modified the connection to be:
Connection c(argc > 1 ? argv[1] : "localhost"); //, "{protocol:amqp1.0}");
And that worked. Any idea why this would change things?
Does your broke
age in context:
http://qpid.2158936.n2.nabble.com/Using-QMF-to-know-about-consumers-in-a-topic-exchange-tp7663510p7663518.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-uns
ery the bindings. The attached program will list all the
bindings. You could modify the approach to filter out all but those
where the exchange is "amq.topic". (You can't have the query do that
filtering for you with QMF).
/*
*
* Licensed to the Apache Software Foundation (ASF)
ect";
content["_what"] = "OBJECT";
content["_object_id"] = schemaId;
request.setContentObject(content);
Is there some way to modify this QMF request to get the information I'm
looking for? Thanks
Max
--
View this message in context:
http://q
It worked like a charm.
Thanks.
Vavricka
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Remove-alternate-exchange-tp7660147p7660212.html
Sent from the Apache Qpid users mailing list archive at Nabble.com
On 7 March 2017 at 14:25, Vavricka wrote:
> Hi,
>
> I have two exchanges with alternate exchange set to the other exchange.
>
> Below are the two exchanges in following format exchange>
>
> broadcast,broadcast_resend
> broadcast_resend,broadcast
>
>
Hi,
I have two exchanges with alternate exchange set to the other exchange.
Below are the two exchanges in following format
broadcast,broadcast_resend
broadcast_resend,broadcast
I am trying to remove exchange by REST API.
When I tried to remove exchange 'broadcast' J
On 02/03/17 09:18, Morgan Lindqvist wrote:
I am using AMQP 1.0, a requirement for the implementation. Can I not use an
"exchange" and connect it to a queue and write to the exchange and read from
the queue in this case?
Yes, you can. AMQP 1.0 doesn't cover the binding of t
Hi,
I will try getting the logs, but until then.
I am using AMQP 1.0, a requirement for the implementation. Can I not use an
"exchange" and connect it to a queue and write to the exchange and read from
the queue in this case?
I have big difficulties in identifying which part of quid t
Without the "name" field the ACL rule applies to "AMQP 1.0 establish sender
link to queue" and not to AMQP 0-10 publishing to an exchange.
See the table
http://qpid.apache.org/releases/qpid-cpp-1.36.0/cpp-broker/book/chap-Messaging_User_Guide-Security.html#tabl-Messaging_U
Hi Morgan,
You might be missing the exchange name. The publish rule should look
something like this:
acl allow producer publish exchange name=my_exchange routingkey=myRoutingKey
But without the logs it is just guessing.
Jakub
On Wed, Mar 1, 2017 at 8:13 PM, Morgan Lindqvist <
morgan.lin
Hi All,
I have an issue that I can not get working
Setup:
I have one exchange and three queues connected to it with a filter between
the exchange and each queue.
The issue I have is to get the users write access to the exchange.
acl allow producer access exchange name=nwEx
acl allow producer
.py",
>> line
>> 600, in sender
>> raise e
>> qpid.messaging.exceptions.MalformedAddress: unexpected token SLASH(/)
>> line:1,1: /test_queue
>>
>> How can I reference the default exchange as it has a queue called
>> test_queue bound to it
der
File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
600, in sender
raise e
qpid.messaging.exceptions.MalformedAddress: unexpected token SLASH(/)
line:1,1: /test_queue
How can I reference the default exchange as it has a queue called
test_queue bound to it
I created a queue using the command:
>> ./qpid-config add queue test_queue
Then I get something like this
./qpid-config exchanges -r
*Exchange '' (direct)bind [bd2dfd48-6f3f-4807-b591-df543a306403:0.0] =>
bd2dfd48-6f3f-4807-b591-df543a306403:0.0bind [qservice_queue
(/default)/qu(topic-localhost.16041.1)]
QUE-1002 : Deleted
Ram
On Sat, Oct 15, 2016 at 9:19 AM, Rob Godfrey
wrote:
> If the exchange is deleted there should be a log entry for that - look for
> the string EXH-1002 in the logs. As above the error you gave is simply
> that the client was
If the exchange is deleted there should be a log entry for that - look for
the string EXH-1002 in the logs. As above the error you gave is simply
that the client was trying to create an exchange but seemingly not
providing enough information to do so (missing type).
-- Rob
On 15 October 2016 at
The log is only saying this one, I know there was a exchange we create and
it was gone, I created exchange again and it looks ok, wondering how that
exchange got deleted, the exchange entry in default.json is also
disappeared.
Ram
On Oct 15, 2016 3:02 AM, "Rob Godfrey" wrote:
>
The error you get "[con:36(producer11476488793213@/10.16.
16.241:61948/default)/ch:0] CHN-1003
: Close : 404 - Unknown Exchange Type:" is not saying that the exchange has
been deleted, rather that the client has attempted to declare an exchange
but the type of the exchange (e.g. fano
14 23:50:58,181 INFO [IO-/10.16.16.241:61948] (q.m.c.close_forced)
- [con:36(ANONYMOUS@/10.16.16.241:61948/default)/ch:0]
[con:36(producer11476488793213@/10.16.16.241:61948/default)/ch:0] CHN-1003
: Close : 404 - Unknown Exchange Type:
These are my exchanges from other broker which is running
federated
brokers to be logically a single broker, therefore a message sent to any
one of the brokers can be received by an consumer. Further I want to use
headers exchange so the consumers only receive messages that they are
interested in based on fields in the headers.
To do this I have 3 qpid brokers
federated
brokers to be logically a single broker, therefore a message sent to any
one of the brokers can be received by an consumer. Further I want to use
headers exchange so the consumers only receive messages that they are
interested in based on fields in the headers.
To do this I have 3 qpid brokers
Just to be clear, AMQP 0-10 *requires* that a binding key is used to
uniquely identify every binding between an exchange and a queue. It does
allow for the fact that the binding may be the empty string, however only
one binding per queue may use this binding key on the given exchange. So I
don&#
Thank you Keith,
Issue raised: https://issues.apache.org/jira/browse/QPID-7339
Adel
> From: keith.w...@gmail.com
> Date: Fri, 1 Jul 2016 16:43:42 +0100
> Subject: Re: [Qpid Java Broker] Cannot bind fanout exchange to a queue
> without specify a binding key
> To: users@qpid.apa
Hi Adel
Yes, this is a defect in the Web Management Console (the UI). The UI
should not be demanding a binding key in this case. For the fanout
exchange, the binding is simply one between exchange and queue.
Actually, underneath the binding key field is used to name the Binding
entity that
Hello,
In the definition of the fanout exchange[1], it is mentioned "The fanout
exchange type routes messages to all queues bound to the exchange, regardless
of the message's routing key". However, using the web management console, when
I create a fanout exchange, it forces me t
That is correct. If you bind a queue to that exchange, you can receive
management updates. If they're simply dropped, there's no buildup of
resources.
-Ted
On 05/04/2016 05:00 PM, rammohan ganapavarapu wrote:
Rob/Steve,
Thank you for your reply, i assume it wont hold any resour
here are no messages 'in' the
> exchange, as they dont hold messages.
>
> Those numbers are simple counts of what has occurred during operation.
> The broker keeps those records and then supplied them to qpid-stat
> when it queried for the information.
>
> Robbie
>
&g
As Steve mentioned, the exchanges don't queue messages, they only
route them (to queues). That is, there are no messages 'in' the
exchange, as they dont hold messages.
Those numbers are simple counts of what has occurred during operation.
The broker keeps those records and then s
I am confused now, in previous email you said "They are not held in
memory". When qpid-stat says there are messages in that exchange those
messages should be some where right either in memory or in FS or qpid-stat
is displaying false output? so dropped messages will be gone and they
They are for management messages. They only exist in memory, never in the file
system.
> -Original Message-
> From: rammohan ganapavarapu [mailto:rammohanga...@gmail.com]
> Sent: Wednesday, May 04, 2016 3:03 PM
> To: users
> Subject: Re: Messages in qpid.management exch
any issue if those msg number grow if so how
> to resolve that issue? restarting qpidd may clear those messages but wanted
> to know if we can configure to set threshold and clear them automatically.
>
>
> qpid-stat -e
>
> Exchanges
> exchange type dur
> From: rammohan ganapavarapu [mailto:rammohanga...@gmail.com]
> > Sent: Wednesday, May 04, 2016 2:56 PM
> > To: users
> > Subject: Re: Messages in qpid.management exchange
> >
> > One more thing to add, does it impact qpid performance?
> >
> > Ram
> -Original Message-
> From: rammohan ganapavarapu [mailto:rammohanga...@gmail.com]
> Sent: Wednesday, May 04, 2016 2:56 PM
> To: users
> Subject: Re: Messages in qpid.management exchange
>
> One more thing to add, does it impact qpid performance?
>
> Ram
>
them automatically.
qpid-stat -e
Exchanges
exchange type dur bind msgIn msgOut msgDrop byteIn
byteOut byteDrop
qmf.default.directdirect 2 28.9m 28.9m 0
272g272g 0
amq.topic topicY 0 0 0 0
0 0
That works! Brilliant, many thanks.
I thought I'd thought of everything :p
On 12 November 2015 at 14:50, Jakub Scholz wrote:
> I think you have to use topic instead of exchange in the address, e.g.:
> test.topic; { node: { type: topic} }
>
> That should get your client worki
I think you have to use topic instead of exchange in the address, e.g.:
test.topic; { node: { type: topic} }
That should get your client working.
J.
On Thu, Nov 12, 2015 at 3:29 PM, Chris Richardson wrote:
> test.topic;{node:{type:exchange}}
>
simplified situation is that I have a 0.34 broker with a topic exchange
("test.topic") and an ACL which allows my user to access and publish to the
exchange, something like this:
#start acl
acl allow client@QPID access exchange name=test.topic
acl allow client@QPID publish exchange name=test.topic
On 08/26/2015 07:28 PM, Matt Broadstone wrote:
Is it possible with qpidd (amqp1.0) to receive notification on a sender
link whether a message sent to a topic exchange was actually delivered to a
receiver?
Not at present, no. It could be modified to release such messages
perhaps (that is what
Hi,
Is it possible with qpidd (amqp1.0) to receive notification on a sender
link whether a message sent to a topic exchange was actually delivered to a
receiver? Initially I had thought I might be able to use the "durable"
header, but I believe that only guarantees that the broker ha
you could create a new direct
exchange "mytopics" or whatever you want to call it...
> Are you using durable subscriptions?
> Yes, I am using durable subscriptions
>
OK - do the durable subscriptions come and go every hour, or is it a
fairly fixed number of subscriptions just wi
rn matching then you can actually just use a
> direct exchange instead which will be more efficient. In terms of
> performance I don't think there should be any issue with the pure
> number of topics...
>
> Are you using durable subscriptions? If not I don't think the use
u are not using pattern matching then you can actually just use a
direct exchange instead which will be more efficient. In terms of
performance I don't think there should be any issue with the pure
number of topics...
Are you using durable subscriptions? If not I don't think the use of
Hi,
Broker: Java
Topic: amq.topic
Exchange, subscriber, messages are all durable. HA with BDB, with 1 replica.
My use case need large number of short lived topics. Each topics have 2
producers and 3 to 4 subscribers and a topic could live for an hour or so
at a maximum. Are there any
On 04/07/2015 12:28 PM, Toralf Lund wrote:
I notice that I do use the same session for the sender and receiver
[...]
Once I sort out this issue, everything works as expected
Super, thanks for the update Toralf!
-
To unsubscr
making sure a "well-known" receiver queue is set up and bound to the
exchange. This is something that's tried and retried until it's
successful, but it turns out that the first attempt occurs before the
above mentioned sender initialisation. If I remove the receiver setup,
eve
On 03/27/2015 03:12 PM, Toralf Lund wrote:
I'm also setting up a temporary receiver with auto-create as a way of
making sure a "well-known" receiver queue is set up and bound to the
exchange. This is something that's tried and retried until it's
successful, but it
tring to
Session::createSender(), hoping to create and connect to an exchange
that does not originally exist:
pgs.data; { create: sender, delete: never, node: { type: topic,
durable: False } }
I then get the error message
Create failed for exchange pgs.data; not-found: not-found: Exchang
ng to create and connect to an exchange
that does not originally exist:
pgs.data; { create: sender, delete: never, node: { type: topic,
durable: False } }
I then get the error message
Create failed for exchange pgs.data; not-found: not-found: Exchange
not found: pgs.data
(/work/build/build
On 27/03/15 12:41, Gordon Sim wrote:
On 03/27/2015 08:52 AM, Toralf Lund wrote:
Hi,
I'm having problems with the auto-create functionality in the C++
messaging API. Simply put, I pass the following address string to
Session::createSender(), hoping to create and connect to an exchange
that
1 - 100 of 425 matches
Mail list logo
