Hi Bhathiya/Dimithri,
There are two ways how we can use Stratos Load Balancer:
1. Populate the topology via the message broker (when working with Stratos)
2. Populate the topology via the loadbalancer.conf (when using as a
standalone load balancer)
In option 1: repository/conf/jndi.properties fil
Hi Imesh,
Looking at the code, seems that setting topology-event-listener to false
will only disable subscribing to the topology topic. It would still try to
subscribe to application-signup and domain-mapping topics. IMHO this should
be fixed so that its possible to disable subscribing to these tw
Hi,
I'm getting the same error. Is there a way to overcome this?
On Mon, Mar 2, 2015 at 4:58 PM, Bhathiya Supun wrote:
> Hi,
>
> Any update on this issue? I'm getting the same error when trying to start
> Stratos load balancer.
>
> On Mon, Feb 16, 2015 at 12:31 PM, Sajith Abeywardhana
> wrote
Hi,
Any update on this issue? I'm getting the same error when trying to start
Stratos load balancer.
On Mon, Feb 16, 2015 at 12:31 PM, Sajith Abeywardhana
wrote:
> Hi Imesh,
>
> Even I set to load balancer. conf file config as *topology-event-listener:
> false*;
>
> I'm still getting this ER
Hi Imesh,
Even I set to load balancer. conf file config as *topology-event-listener:
false*;
I'm still getting this ERROR message. Please advice me how to solve this?
[2015-02-16 12:26:54,489] INFO - CarbonUIServiceComponent Mgt Console URL
: https://10.100.7.19:9443/carbon/
[2015-02-16 12:2
Hi Sajith,
I think you are on the wrong direction. @Nirmal: Still SLB does not support
hazelcast clustering.
Consider SLB as a standard load balancer which does not know anything about
Carbon clustering. We just need to do a static load balancer configuration
and try to simulate how WSO2 products
On Fri, Feb 13, 2015 at 11:36 AM, Nirmal Fernando wrote:
> This is the static configuration, where you don't use dynamic member
> discovery. You need group_mgt_port for dynamic member discovery. Please use
> the ELB config,
>
I meant the attributes applicable for cluster sections.
> it should wo
This is the static configuration, where you don't use dynamic member
discovery. You need group_mgt_port for dynamic member discovery. Please use
the ELB config, it should work in SLB.
On Fri, Feb 13, 2015 at 11:29 AM, Sajith Abeywardhana
wrote:
> Yes. In the axis2.xml file, we do have configurat
Yes. In the axis2.xml file, we do have configuration as
**
But in Stratos load balancer configuration file dose not have
group_mgt_port.
# services {
# app-server { # service name, a unique identifier to identify a
service
# multi-tenant: true; # Set to true if the servi
SLB is using Hazelcast right? If so, group_mgt_port should be used in lb
conf.
On Fri, Feb 13, 2015 at 10:14 AM, Sajith Abeywardhana
wrote:
> Hi Imesh,
>
> Thanks for the reply. I set the configuration as *topology-event-listener:
> false; *
> Then I got below exception while starting the load b
Hi Imesh,
Thanks for the reply. I set the configuration as *topology-event-listener:
false; *
Then I got below exception while starting the load balancer.
Hi Nirmal,
In WOS2 ELB configuration file, there is a configuration as *group_mgt_port
4500; *[1] How can I map this configuration in the Str
Hi Sajith,
Stratos load balancer has a configuration file in repository/conf folder:
loadbalancer.conf. If you open it in a text editor you will find inline
comments describing each property:
# Enable/disable topology event listener
# If this property is set to true, load balancer will listen to
Hi All,
I'm getting this exception while starting the
*apache-stratos-load-balancer-4.1.0.
*Please can anybody tell me why this happens? And how to solve this?
Note -: *apache-activemq-5.10.0 is running..*
[2015-02-12 21:42:34,100] ERROR - AmqpTopicConnector Could not connect to
message broker
j
13 matches
Mail list logo
