Problem with Fabric MQ Gateway when using http transport connecter for A-MQ

[ravishankarhassain]

I am trying to use http connector for connecting with the JBoss A-MQ (Which is embedded in JBoss Fuse ESB 6.2.1) . I have enabled and configured the http transport connector in the broker.xml which is in the mq-base profile. Also I have enabled the http connector in the profile properties. I have created a new Master/Slave broker profile and assigned it to 2 child containers. I have deployed Fabric MQ and HTTP gateway to the root container so that Fabric will handle and map the connections to the active node. From the MQ client (stand alone java program), I am using the url http://localhost:61616 as the broker url in order to connect with the current active broker node but it seems like the Fabric MQ Gateway is not able to map the client to the available broker in the fabric. But when I inspect the fabric registry I could see that the http connector is configured to a random port properly and if I use that port in my MQ client then connection is established sucessfully and I could the message to the broker. Also, I noted that instead of http connector If I use the openwire tcp connector tcp://localhost:61616 Fabric MQ gateway is able to map the client to the the available broker in the fabric. I am not sure whether its a bug or am I missing something. I have attached the screenshot below for your reference.

[paoloantinori]

Hi, please use official Red Hat support to JBoss Fuse issues.

[davsclaus]

closing old ticket