Grouper Users - Open Discussion List

[Keith Hazelton <>]

It's an AMQP version issue: 0.9.1 is supported by RabbitMQ, 1.0 is significantly rearchitected and a ActiveMQ support 

RabbitMQ points to a plugin that supports 1.0 but cautions it's not been updated in a while

Here's the github location for the AMQP 1.0 plugin for RabbitMQ: https://github.com/rabbitmq/rabbitmq-amqp1.0 

               --Keith

On Mon, Apr 1, 2019 at 10:42 AM Crawford, Jeffrey <> wrote:

Good Morning,

 

Long story short, our campus uses RedHat FUSE for the messaging queue. We need the routing capabilities of the AMQP, and the RedHat version of ActiveMQ seems to have AMQP capabilities. However when we have tried connect to it using the RabbitMQ connection parameters we get the following error:

 

2019-03-22 16:01:14,129: [AMQP Connection 172.16.92.142:62007] ERROR ForgivingExceptionHandler.log(124) -  - An unexpected connection driver error occured

com.rabbitmq.client.MalformedFrameException: AMQP protocol version mismatch; we are version 0-9-1, server sent signature 0,1,0,0

        at com.rabbitmq.client.impl.Frame.protocolVersionMismatch(Frame.java:170)

        at com.rabbitmq.client.impl.Frame.readFrom(Frame.java:107)

        at com.rabbitmq.client.impl.SocketFrameHandler.readFrame(SocketFrameHandler.java:164)

        at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:571)

        at java.lang.Thread.run(Thread.java:748)

 

Looks like there was a discussion on this back in Aug of 2017 regarding the protocol mismatch between Chris and Keith. I’m not sure what the result of that was.

 

I’m not sure if the RabbitMQ configuration items are supposed to be generic with AMQP, however our “queue expert” is asking the question if Grouper could support AMQP 1.0 since this is what the ActiveMQ version supports. I do notice that in the configuration area notes that the routingKey parameter is ignored for all queues except rabbit. Are there any goals to support AMQP 1.0?

 

If we should be using ActiveMQ natively where we have different stems/folders going to different exchanges that might work to but I was hoping to use the routing capabilities of AMQP so we didn’t have to have a bunch of loader configs for different areas of the folder structure. I didn’t see a way to create a loader config that was pinned to a specific folder though so perhaps I’m missing a good example of how to do this. Any pointers in that regard would be appreciated.

 

Also, let me know if I’m approaching this wrong.

 

Thanks

Jeffrey C.

--

_______________________
Keith Hazelton 
Internet2 Trust and Identity