[rabbitmq-discuss] Problems while trying interoperability

[Alexis Richardson]

Rob,

Anything to minimise Qpid / RabbitMQ deltas on how the spec is
implemented would be great - thanks.  We'll do the same if the case
arises.  And thanks very much for being on this group so we can work
with your team to ensure interop is real and not vapour.

Tanmay,

As Matthias pointed out, pending a patch of the type Rob mentions, you
can also do this as an interop workaround:

1) Qpid client -> RabbitMQ broker --- run RabbitMQ in "lax" mode (ie
we reduce our spec implementation surface for interop).
2) RabbitMQ client -> QPid server --- do not do the accessRequest and
use a hard-coded ticket# instead

For (1) lax mode is enabled by default so please *do* send us your logs.

Cheers

alexis






On 8/16/07, Robert Godfrey <rob.j.godfrey at gmail.com> wrote:
> Hi, at some point I added implementations of access ticket to the Qpid
> client to allow us to interoperate with the RabbitMQ broker... if the code
> has disappeared I can put it back in.
>
> At present Qpid does not implement the access ticket / realm parts of AMQP.
>
> Hope this helps,
> Rob
>
>
> On 16/08/07, Matthias Radestock <matthias at lshift.net> wrote:
> > Tanmay,
> >
> > Goel, Tanmay wrote:
> > > when I try to run a RabbitMQ client (attached,
> > > SimpleProducer.java) against Qpid broker (with the default configuration
> > > provided when I first downloaded it, no change), I get the following
> > > exception. The exception is thrown on this like of code: *
> > >
> > > *int ticket = ch.accessRequest("/test");*
> > >
> > > *Intuitively, this method is not provided by the Qpid broker. Is it?*
> >
> > You are probably right and this method is indeed unimplemented in Qpid.
> > It certainly wasn't when we ran the tests ~6 months ago, as noted in
> > http://www.rabbitmq.com/interoperability.html
> >
> > You can probably just skip that request and use a ticket number of 0,
> > with RabbitMQ's lax_mode enabled (which it is by default - see above
> page).
> >
> > > *Also, there is no "client-name" passed as a parameter at the time of
> > > establishing connection to the RabbitMQ connection constructor but is
> > > passed to the Qpid connection constructor. If and how will this effect?*
> >
> > I have no idea what the "client-name" value is for. Perhaps the QPid
> > client passes that value as part of the peer properties exchanged during
> > connection negotiation, in which case it's informational only, i.e. it
> > shouldn't affect the behaviour.
> >
> > > *Alternatively, when I tried to run a Qpid client against a RabbitMQ
> > > broker (again, with the default settings, virtual hosts, etc). I got the
> > > following error message at the first line of code: _connection = new
> > > AMQConnection("localhost", 5672, "guest", "guest", "clientid",
> "/data");*
> >
> > What do the RabbitMQ server logs (stdout, rabbit.log, rabbit-sasl.log)
> say?
> >
> > What version of QPid are you running? The M1 release?
> >
> > Regards,
> >
> > Matthias.
> >
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-discuss at lists.rabbitmq.com
> >
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> >
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>


-- 
Alexis Richardson
+44 20 7617 7339 (UK)
+44 77 9865 2911 (cell)
+1 650 206 2517 (US)