On Thu, May 3, 2018 at 9:50 PM, Harsha Kumara <hars...@wso2.com> wrote:
>
>
> On Thu, May 3, 2018 at 9:44 PM, Samitha Chathuranga <sami...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> AFAIU in Gateway nodes the <JMSConnectionDetails> in api-manager.xml defines
>> the connection details to the TM to listen to the JMS topic in TM, to get
>> the throttle decisions. The <ServiceURL> defined under that is used to
>> establish that connection initially.
>>
>> <JMSConnectionDetails>
>> (1) <ServiceURL>tcp://[Traffic-Manager-host]:5673</ServiceURL>
>>
>> Then under <JMSConnectionDetails> under <JMSConnectionParameters> we are
>> defining again the
>> <connectionfactory.TopicConnectionFactory> url, which is the actual broker
>> endpoint to listen to the topic.
>>
>> <JMSConnectionDetails>
>> .....
>>
>> <JMSConnectionParameters>
>> ...
>> <connectionfactory.TopicConnectionFactory>
>> (2) amqp://admin:admin@clientID/carbon?brokerlist='tcp://<Traffi
>> c-Manager-host>:5673?retries='5'%26connectdelay='50'
>> </connectionfactory.TopicConnectionFactory>
>>
>> Please correct me if my understanding is wrong.
>>
>> But in that url also we are defining Traffic-Manager-Host and Port. So what
>> is the use of defining it again
>> here too?
>>
>> If you put the url in ServiceURL, you can refer it in the ${jms.url} in
> the connection factory which is the default setting. But when you go for
> failover mode of TM, you can't define single url. Hence it would be best to
> change the connection factory URL with the failover MB configuration.
>
Like <connectionfactory.TopicConnectionFactory>amqp://admin:admin@clientID
/carbon?failover='roundrobin'%26cyclecount='2'%26brokerlist='tcp://
127.0.0.1:5673?retries='5'%26connectdelay='50';tcp://127.0.0.1:5674?retries='5'%26connectdelay='50'';tcp://127.0.0.1:5675?retries='5'%26connectdelay='50''</connectionfactory.TopicConnectionFactory>
> And in our docs [1] under* Single Traffic Manager* (tab) under *Step 6.6 -
> Configure and start the Gateway *it is
>> guided to include both (1) and (2). But under *HA of Traffic Manager* (tab)
>> guide, the (1) is not mentioned to
>> configure. Is this something missing in the doc?
>>
>> [1]
>> https://docs.wso2.com/display/AM210/Deploying+WSO2+API-M+in+a+Distributed+Setup#DeployingWSO2API-MinaDistributedSetup-Step6.6-ConfigureandstarttheGateway
>>
>>
>> Regards,
>>
>> Samitha
>>
>>
>>
>>
>>
>> --
>> *Samitha Chathuranga*
>> *Software Engineer*, *WSO2 Inc.*
>> lean.enterprise.middleware
>> Mobile: +94715123761
>>
>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>
>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>
--
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
