Hello everyone,
Sorry about the other e-mail (which created a different thread) and it was
missing Alex's email. So I am now replying to all for this one. Hopefully, this
will come under the original e-mail thread.
I also figured it out as I discovered I had to specify the type to be a topic.
Forwarding this to the mailing list. I also figured it out as I discovered I
had to specify the type to be a topic. This is what I did previously:
./spout test.fanout
This is where I got the NPE. After some trial and error plus Alex's tip from
below, I was able to get it working with this comma
Thank you Robbie and Rob. Good point about lack of transactions in HBase.
That is the kind of info I was looking for.
Rob -- in one of our application stacks, HBase is the only "system of records",
by which
I mean it is the only system with DR and HA built in. If we store queue data in
HBase, it
On 26 March 2013 18:52, Fraser Adams wrote:
> I think that examples of some of the SASL and other security options are
> definitely worth including in a sample qpidd.conf that one is always
> something of a black art with traps for the unwary etc. the mailing list
> might go quite quiet if there
On 26 March 2013 17:39, Gordon Sim wrote:
> On 03/26/2013 04:12 PM, Bill Freeman wrote:
>
>> Qpid brokers speak AMQP on the wire. Excluding command line arguments,
>> config files, stuff in the data directory, and possibly *nix signals,
>> brokers don't communicate in any way but AMQP. Specific
On 26 March 2013 19:13, Gordon Sim wrote:
> On 03/26/2013 05:56 PM, Justin Ross wrote:
>
>> (A little trouble with my list subscription, so I'm using nabble to
>> reply.)
>>
>> "I would have these categories on the front page in some way (with more
>> detail on each and indeed on each aspect or s
I think that examples of some of the SASL and other security options are
definitely worth including in a sample qpidd.conf that one is always
something of a black art with traps for the unwary etc. the mailing list
might go quite quiet if there were lots of good examples for various
security us
On 03/25/2013 09:55 PM, Rob Godfrey wrote:
So... another small niggle with the build (not sure if auto-tools suffers
the same issue)... I ran the cmake build on a machine with an old version
of proton installed (0.2)... This caused the build to fail as it detected
proton but clearly 0.2 is not a
On 03/26/2013 05:57 PM, Connor Poske wrote:
We use it to set log levels and log file location on the broker, that's about
it.
Thanks, Connor! Anyone else?
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For addit
On 03/26/2013 06:33 PM, Fraser Adams wrote:
Hi again Gordon,
you mentioned "the entire cluster module has been removed" I've just
looked in /usr/local/lib/qpid/daemon and ha.so has been put in there by
the cmake build on trunk.
I'm guessing that this shouldn't be there now given that statement?
On 25/03/13 19:15, Gordon Sim wrote:
does anyone have any thoughts on the "Bad argument:
|cluster-mechanism=DIGEST-MD5 ANONYMOUS|" issue. As I say below when I
did cmake on 0.20
That is an option that is no longer supported (the entire cluster
module has been removed). Looks like it just ha
On 03/26/2013 05:56 PM, Justin Ross wrote:
(A little trouble with my list subscription, so I'm using nabble to reply.)
"I would have these categories on the front page in some way (with more
detail on each and indeed on each aspect or sub-component) available via
links."
This suggests that the
We use it to set log levels and log file location on the broker, that's about
it.
From: Gordon Sim [g...@redhat.com]
Sent: Tuesday, March 26, 2013 10:57 AM
To: users@qpid.apache.org
Subject: Do you use qpidd.conf, if so for what? (was Re: Ubuntu cmake woe
(A little trouble with my list subscription, so I'm using nabble to reply.)
"I would have these categories on the front page in some way (with more
detail on each and indeed on each aspect or sub-component) available via
links."
This suggests that the categories you listed are not now present o
A default qpidd.conf file has previously shipped with the c++ install.
However the only setting currently in it is now obsolete and must be
removed.
The suggestion has been to keep the conf file and have some commented
out examples of commonly used options.
My question is what options would
Many thanks - Bill
On Tue, Mar 26, 2013 at 1:39 PM, Gordon Sim wrote:
> On 03/26/2013 04:12 PM, Bill Freeman wrote:
>
>> Qpid brokers speak AMQP on the wire. Excluding command line arguments,
>> config files, stuff in the data directory, and possibly *nix signals,
>> brokers don't communicate i
On 03/26/2013 05:07 PM, Fraser Adams wrote:
Hi Gordon,
I was thinking about this thread earlier on today and something just
struck me about the general tool "for creating,
deleting and listing objects of any type" that you attached previously
and is being discussed here.
I think that the general
On 03/26/2013 04:12 PM, Bill Freeman wrote:
Qpid brokers speak AMQP on the wire. Excluding command line arguments,
config files, stuff in the data directory, and possibly *nix signals,
brokers don't communicate in any way but AMQP. Specifically, there is no
separate port, and no recognizably no
Hi Gordon,
I was thinking about this thread earlier on today and something just
struck me about the general tool "for creating,
deleting and listing objects of any type" that you attached previously
and is being discussed here.
I think that the general premise is that it provides a more "gener
Hello Rob,
I got the NPE from the System.out to the console, but it did not provide
sufficient information as shown below.
[Client] warning Exception received from broker: internal-error:
Exception processing command: java.lang.NullPointerException [caused by 1
\x00:\x00]
internal-error: Exce
So, long term that XML config is indeed going away, but 0.22 only removes
the broker XML configuration, and simply makes the virtualhosts XML
configuration optional.
The VirtualHosts XML confguration can still be used in 0.22 and is indeed
actually necessary to conduct most virtualhost level conf
I really like the box as well. It's clear and concise.
I like the fact that the layout is fluid, so it should work well on
different devices.
(William Henry has every device under the Sun, I usually enlist him to
help me with that).
The links on right hand side is nice to have from the main page.
As a slight aside, given that Jeremy's original question asked about
creating a fanout exchange with the context of "from the XML config"
it's probably worth mentioning the work that Robbie and yourself have
been leading on to migrate off/deprecate the XML config towards
configuration via the p
Hi Jeremy,
when you say you got an NPE from the Java Broker, do you mean that there
was an NPE in the log or System.out from the broker? If so can you post
the stack trace here - we should definitely not do that no matter what
address you are using.
thanks,
Rob
On 26 March 2013 17:11, Jeremy Wa
Please pardon me if my questions are all clearly answered in the
documentation. I've been reading for a while, and am still in doubt.
While I have done C++ and Java programming in the past, I have a lot more
experience in C, and I've mostly been a Python programmer of late. So also
please excuse
Hello Alex,
Thank you for your help! I was able to get it configured correctly. I created
three queues to bind to the exchange. I then connected separate listeners
(using drain) to each queue. I attempted to send a message to the exchange
using spout, but I got a NullPointerException from the J
On 03/26/2013 02:05 PM, Justin Ross wrote:
For my next iteration, I plan to try something new: I'm going
to promote "source modules" (Qpid Java, Qpid C++, Qpid Proton) more on
the front page.
I don't think that is the view that we should be presenting to users.
While it does match the release
Hi, everyone. It's clearly been too long since my last update!
http://people.apache.org/~jross/transom/2013-03-26/
Previous version: http://people.apache.org/~jross/transom/2013-02-11/
A complete list of changes follows. To summarize: The look and feel
isn't changed much since last time.
Hi Jason,
On 26 March 2013 13:26, Jason Barto wrote:
> Rob,
> thanks for your quick response - I've consolidated the code into a single
> java file and would gladly publish it - frankly being new to AMQP 1.0 and
> its client libraries I'd value the feedback. I think I may have determined
> the
Rob,
thanks for your quick response - I've consolidated the code into a single
java file and would gladly publish it - frankly being new to AMQP 1.0 and
its client libraries I'd value the feedback. I think I may have determined
the reason for the slow down - not sure why it didn't occur to me earl
Hi Jeremy,
You need to add into a virtual host configuration an exchange
configuration like in the example below:
test
...
fanout
test.fanout
...
my-queue
Hmmm not sure if that is the problem. Changing the hermes-config.xml file
to connectionURLString did not do the job ! Is nobody using Hermes ?
We are looking for a flexible and user friendly way to send various payload
to QPID. Hermes does the trick when talking JMS to jboss ;-)
Venlig hilsen /
Hi,
I don't know why is that but the property you need to set is
connectionURLString, there is no setter for connectionURL in
AMQConnectionFactory. HermesJMS did not offer this property, probably the QPID
plugin needs to updated? When you set it manually in hermes-config.xml, it
will, sort of
We are struggling with HermesJMS and QPID. When connecting from HermesJMS
the connectionurl appears to be ignored or is incorrect. QPID is up and
running and we can connect through JConsole.
Connectionurl: tcp://localhost:5276
javax.jms.JMSException: The connection factory wasn't created with a
34 matches
Mail list logo
