Hi Jeremy,
I don't have exact experience to help you but your plan seems doable.
The SWIG documentation for Perl on Windows doesn't list any obvious
limitations that look like they will get in your way. I'm pretty sure
any lack of development libs would have been noted there.
In your shoes, I wo
Hi Rafael,
yeah, you probably missed my earlier updates, my problem was that
because of a quirk on trunk that's causing both legacystore.so and
linearstore.so to be installed when I fired up "qpidd --auth no" the
broker failed to start at all, so what I had done was do:
qpidd --auth no --no-mo
Sorry - yes my next observation was going to be that the form for the 1-0
tools is user:pass@ (the username/password was and unfortunate abbreviation
rather than implying syntax) however at that time my flight was called so I
didn't have time to finish my mail :-)
I'll be adding the GUI necessary
It works for me when I run qpidd from the build directory with the
following options:
src/qpidd --load-module src/amqp.so
I'm guessing that means 1.0 support is still in a module and you need to
make sure it is loaded.
--Rafael
On Sun, Jan 12, 2014 at 11:32 AM, Fraser Adams <
fraser.ad...@b
Re; "I would say user:pass is consistent with most URL usages, user/pass
is the odd one out, so I for one am glad that has been changed."
I'd tend to agree with you there, though as I say the "/" is used by all
the Python tools (and possibly elsewhere) as I mentioned in my mail I
think it's pr
I think that would give you an exception due to two ports with the same
name, but change the name and essentially yes. The broker will assign the
ID if you start it up without one, yes, which is probably the best thing to
do generally if adding things under its feet :).
Sidenote: the easiest thin
Hi Robbie,
Just trying to digest your comments below with respect to enabling Rob's
magical new WS support.
At the moment my config.json has:
"ports" : [ {
"authenticationProvider" : "passwordFile",
"id" : "9e2707d9-10b4-4c3e-8439-cd6135419f19",
"name" : "AMQP",
"port" : "5672"
On 12 January 2014 17:28, Fraser Adams wrote:
> Hi again guys,
> I've just tried again with the Java Broker
>
> What I've discovered is that:
> ./send -a amqp://guest/guest@localhost/test
> [0x19cde50]:ERROR[0] (null)
>
> CONNECTION ERROR connection aborted
>
>
> However with:
> ./send -a amqp://g
On 12 January 2014 17:02, Fraser Adams wrote:
> Cheers Robbie, you're a *star*, you were indeed correct and it was that
> flipping "--no-module-dir"
>
> I manually deleted legacystore.so and fired up
> qpidd --auth no
>
> and
> ./send -a amqp://localhost/test
>
> Successfully adds things to my tes
Hi again guys,
I've just tried again with the Java Broker
What I've discovered is that:
./send -a amqp://guest/guest@localhost/test
[0x19cde50]:ERROR[0] (null)
CONNECTION ERROR connection aborted
However with:
./send -a amqp://guest:guest@localhost/test
*bingo* message arrives on the test que
Cheers Robbie, you're a *star*, you were indeed correct and it was that
flipping "--no-module-dir"
I manually deleted legacystore.so and fired up
qpidd --auth no
and
./send -a amqp://localhost/test
Successfully adds things to my test queue (I've not tried reading them
off yet, but so far so g
You look to be seeing the AMQP 0-10 handshake returned from the qpidd,
which would appear to be the broker is saying 'I dont support 1.0, try
using 0-10'.
Just because something was built doesnt mean it is actually in use. The
info at http://svn.apache.org/repos/asf/qpid/trunk/qpid/cpp/AMQP_1.0 co
I need some advice, we are currently upgrading our broker from 0.12 to 0.22
or later.
We are heavy Perl users both in Linux and Windows, for 0.12 we developed our
own client using the c libraries, this has worked fine but has proved
difficult to maintain and the maintainer who was much smarter tha
With the Java broker are you using a username/password (guest/guest should
work)?
-- Rob
On 12 Jan 2014 17:33, "Fraser Adams" wrote:
> Hi Robbie,
> Re "The AMQP 1.0 handshakes are AMQP 3 1 0 0 and AMQP 0 1 0 0", yeah
> that's what I'd have guessed too looking at the couple of #defines I found
>
Hi Robbie,
Re "The AMQP 1.0 handshakes are AMQP 3 1 0 0 and AMQP 0 1 0 0", yeah
that's what I'd have guessed too looking at the couple of #defines I
found in the Proton code.
TBH I've no real idea how to figure out if qpidd *definitely* has AMQP
1.0 support enabled, though as I say when I loo
Hi Fraser,
I'm not sure your assumption about 1.0 being enabled is correct, that looks
like the AMQP 0-10 handshake to me: AMQP 1 1 0 10.
The AMQP 1.0 handshakes are AMQP 3 1 0 0 and AMQP 0 1 0 0.
I must admit to having not used the 1.0 support in qpidd, but is it not in
its own module? In which
Hey all,
I thought I'd have a go at trying to send an AMQP 1.0 message between
Proton messenger and qpidd.
I've tried to keep things as simple as possible, but unfortunately it
still barfed, so I'd be grateful for some pointers.
I built qpidd 0.27 off trunk yesterday and fired it up with:
q
17 matches
Mail list logo
