We can use "qpid-route route flush broker" to delete all routes for a
broker.
Is there a simple command that can totally clear a broker, deleting all its
queues, exchanges, bindings, and routes?
r $Bs $EX $QUEUE
qpid-route -s -v -d queue add $Bd $broker $EX $QUEUE
So "push" or "pull" was the difference... Wonder why. :)
On Wed, Feb 3, 2016 at 11:33 AM, jjw tectec wrote:
> qpid-route commands were all successful (no errors at all), and "route
> map" is
B2:5673(queue=TestQueue) => Bd:5673(ex=TestExchange)
B2:5673(ex=TestExchange) <= Bs:5673(queue=TestQueue)
On Wed, Feb 3, 2016 at 10:45 AM, Gordon Sim wrote:
> On 02/03/2016 04:26 PM, jjw tectec wrote:
>
>> I followed your suggestion and ran "qpid-stat -q" "qpid-s
msgDrop byteIn
byteOut byteDrop
===
(Bd)TestExchangetopicY 0 100 0 100 9.30k
0 9.30k
On Tue, Feb 2, 2016 at 5:02 PM, Gordon Sim wrote:
> On 02/02/2016 09:08 PM, jjw tectec wrote:
>
> Sorry t
Gordon,
Thank you very much for your answer. Please see my comments and further
questions below:
On Mon, Feb 1, 2016 at 3:45 AM, Gordon Sim wrote:
> On 01/31/2016 10:19 PM, jjw tectec wrote:
>
>> I sent out the email more than 3 days ago, but it's still not appearing
>&
I sent out the email more than 3 days ago, but it's still not appearing in
the mailing list. Has it been deleted from the archive?
On Thu, Jan 28, 2016 at 1:02 PM, jjw tectec wrote:
> I've set up a simple 4-broker system, where between Bs (source broker) and
> Bd (destination
I ran the following script to set up a dynamic exchange route from Bs to
B1.
EX=TestExchange
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $Bs add exchange topic $EX
~/qpid/qpid-tools-0.32/src/py/qpid-config -a $B1 add exchange topic $EX
~/qpid/qpid-tools-0.32/src/py/qpid-route -v -d dynamic add $B
I've set up a simple 4-broker system, where between Bs (source broker) and
Bd (destination broker) are two middle brokers set up in parallel, like
this:
[image: Inline image 1]
The script that I used to set up all the resources & routes is shown at the
end of this message.
I attached a publisher
lke wrote:
> On both the broker and client end you can get some information from
> logging.
>
> export QPID_LOG_ENABLE=trace+
> then qpidd and qpid-send
>
> - Original Message -
> > From: "jjw tectec"
> > To: users@qpid.apache.org
> > Sent:
I'm trying to add encryption, but couldn't get things to work.
I've done the following (for a single broker scenario):
1) Ran the following script to create a certificate database:
mkdir ${CERT_DIR}
certutil -N -d ${CERT_DIR} -f ${CERT_PW_FILE}
certutil -S -d ${CERT_DIR} -n ${NICKNAME} -s "CN=${N
Ok, thank you so much!
On Tue, Jan 19, 2016 at 1:58 PM, Gordon Sim wrote:
> On 01/19/2016 07:56 PM, jjw tectec wrote:
>
>> Thanks Gordon. Adding the link option worked. However, even after
>>
>> msg.setProperty("x-amqp-0-10.routing-key", "keyX"); // p
s an expected behavior?
Thank you!
jjw
On Tue, Jan 19, 2016 at 11:53 AM, Gordon Sim wrote:
> On 01/19/2016 05:23 PM, jjw tectec wrote:
>
>> Hi Gordon,
>>
>> Yes, changing the key name to queue name made messages flow end-to-end.
>> I had also suspected that the routi
ibqpidtypes.so.1: error adding symbols: DSO missing from
command line
Do you know why was that?
Thanks very much
jjw
On Mon, Jan 18, 2016 at 4:20 AM, Gordon Sim wrote:
> On 01/15/2016 07:17 PM, jjw tectec wrote:
>
>> Hello,
>>
>> I'm trying to set up a federated br
Hello,
I'm trying to set up a federated broker system and testing 3 brokers so
far: B1->B2->B3. I'm not seeing messages published to B1 received by
subscriber attached to B3. However, in my tests, Pub->B1->B2->Sub and
Pub->B2->B3->Sub are both working. Below are some configuration details
that I'v
I've asked a couple of questions regarding this activity recently in this
mailing list and got some suggestions. Unfortunately I've not had the luck
to get this to work yet. So I'll try to be more specific and provide more
details on my tests.
We would like to have AMQP clients on an embedded devi
Thanks Gordon and Ted.
I got this to work now. :)
On Fri, Sep 4, 2015 at 3:12 AM, Gordon Sim wrote:
> On 09/03/2015 09:54 PM, jjw tectec wrote:
>
>> Hi Gordon,
>>
>> Thanks so much for your help. I think I got this to work partially now.
>> The Linear Store inside
ep 3, 2015 at 2:29 PM, Gordon Sim wrote:
> On 09/03/2015 08:16 PM, jjw tectec wrote:
>
>> Thanks for your reply. I had tried many different command options before,
>> they all had different problems. Below is the output of the execution:
>>
>> ./qpidd -p 5672
xception 0x0308 jdir::exists() threw JERR_JDIR_STAT: File stat failed.
(file="/home/mmos/qpid/qpid-cpp-0.34/build/src/linearstore.so/qls/dat2"
errno=20 (Not a directory))
On Thu, Sep 3, 2015 at 2:09 PM, Gordon Sim wrote:
> On 09/03/2015 07:43 PM, jjw tectec wrote:
>
>&g
Hello,
I'm trying to make my qpid broker persistent, but have been getting some
issues.
Below is my cmake output, which indicates Legacystore disabled and
Linearstore enabled. (I do see linearstore.so in the build/src folder by
the way.)
-- Found BerkeleyDB: /usr/lib/x86_64-linux-gnu/libdb_cxx.so
ector" refer to the way TCP/IP connections are established.
>> Listeners open passive ports for other processes to connect to and
>> connectors actively connect to other listening processes.
>>
>> -Ted
>>
>> On 08/28/2015 04:30 PM, jjw tectec wrote:
&
open its listener.
>
> However, simply fixing this problem isn't going to make this work. Can
> you provide some more detail as to what you want to see? Are there
> specific queues or topics on the brokers that you are using? What is the
> desired path for messages to fl
Hello,
I'm trying to run a quick test using Dispatch Router, and I think I need
help with configuration.
I'd like to set up such a router between two AMQP brokers, and routes
messages from BrokerA to BrokerB.
Right now, I have Qpid BrokerA running on port 5672, and Qpid BrokerB
running on port 5
;m reading / testing more to better understand it. Please let me
know if you got other thoughts. :)
Thanks again.
jjw
On Mon, Aug 24, 2015 at 10:27 AM, aconway wrote:
> On Mon, 2015-08-24 at 09:58 -0500, jjw tectec wrote:
> > We have the need to set up broker federation between qpid bro
We have the need to set up broker federation between qpid broker and Azure
Service Bus. I'm aware of the following discussion thread, and had tried
similar steps:
https://mail-archives.apache.org/mod_mbox/qpid-users/201403.mbox/%3c5317022a.2090...@redhat.com%3E
However, to my disappointment, the s
24 matches
Mail list logo
