Hi,
We added port 8280 manually to the template file and it worked.
Thanks
On Tue, Sep 9, 2014 at 10:16 AM, Nirmal Fernando
wrote:
>
>
> On Tue, Sep 9, 2014 at 9:58 AM, Chamila De Alwis
> wrote:
>
>> Thanks Nirmal! That clears it up.
>>
>> In our case, it seems that LB is not opening the
On Tue, Sep 9, 2014 at 9:58 AM, Chamila De Alwis wrote:
> Thanks Nirmal! That clears it up.
>
> In our case, it seems that LB is not opening the port specified as the
> proxyPort by the cartridge.
>
Yes, unfortunately such a dynamism is hard to implement :-) (you need to
restart LB etc.)
>
> Ac
Hi Udara,
axis2.xml is attached herewith
Thanks
On Tue, Sep 9, 2014 at 9:58 AM, Chamila De Alwis wrote:
> Thanks Nirmal! That clears it up.
>
> In our case, it seems that LB is not opening the port specified as the
> proxyPort by the cartridge.
>
> According to the puppet module template the t
Thanks Nirmal! That clears it up.
In our case, it seems that LB is not opening the port specified as the
proxyPort by the cartridge.
According to the puppet module template the transportReceiver port is
defined at the nodes.pp as port 80 by default ($lb_httpPort)[1]. If the LB
should accept reque
Hi Prasanna,
Could you please attach the axis2.xml of the running LB instance.
Touched, not typed. Erroneous words are a feature, not a typo.
Hi Akila,
Template files too looks the same. Above part was taken from the template
file
On Tue, Sep 9, 2014 at 8:57 AM, Nirmal Fernando
wrote:
> Hi All,
>
> Let me explain the rationale behind defining a proxy port. Proxy port is a
> way to let LB know, that LB should redirect all the request
Hi All,
Let me explain the rationale behind defining a proxy port. Proxy port is a
way to let LB know, that LB should redirect all the requests that are
coming to it (i.e. proxy port) to mapped host port (i.e. port). This
mapping becomes vital when LB exposes multiple ports (i.e. you can define n
Hi Prasanna,
This commenting is not relevant since LB axis2.xml is deployed via Puppet.
Please check Puppet lb module templates.
On 9 Sep 2014 08:19, "Prasanna Dangalla" wrote:
> Hi sajith,
>
> In LB's axis2.xml file. (in /repository/conf/axis2/axis2.xml),
> the below mentioned part is commented
Hi sajith,
In LB's axis2.xml file. (in /repository/conf/axis2/axis2.xml), the
below mentioned part is commented. Is this the reason because ports 8280
and 8243 are commented in this.
On Tue, Sep 9, 2014 at
Setting proxyPort to 80 works successfully.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Mon, Sep 8, 2014 at 10:42 PM, Udara Liyanage wrote:
> Instead of 0 could you try with 80.
>
>
>
> Touched, not typed. Erroneous words are a feature
Instead of 0 could you try with 80.
Touched, not typed. Erroneous words are a feature, not a typo.
Hi Udara,
I altogether removed the proxyPort from the php cartridge. Now the
subscription provides port 0 as the access URL which again is not
accessible.
I'm not clear on how the access URL is constructed. But if the proxyPort is
not provided shouldn't it default to the port provided rather than
Hi,
Then either php cartridge proxy port should be changed to 80 or nodes.pp
should be changed to 8280
Touched, not typed. Erroneous words are a feature, not a typo.
Hi Sajith,
The value is set to 80. This is the value provided as default in the
nodes.pp.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Mon, Sep 8, 2014 at 6:00 PM, Sajith Kariyawasam wrote:
> Hi Chamila,
>
> Please check the port values
Hi Chamila,
Please check the port values in LB's axis2.xml file. (in
/repository/conf/axis2/axis2.xml),
wrote:
> Update:
>
> I redeployed the load balancer with added proxyPort mapping and still the
> cartridge isn't accessible through port 8280, only through port 80.
>
>
> Regards,
> Cham
Update:
I redeployed the load balancer with added proxyPort mapping and still the
cartridge isn't accessible through port 8280, only through port 80.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Sun, Sep 7, 2014 at 11:19 PM, Chamila De Alw
Hi,
I've deployed my stratos installation with the attached policies with load
balancing enabled. When I subscribe to the lb enabled cartridge the
subscription completes successfully. The load balancer receives the
notification that the cartridge (php in my case) was activated
successfully. Howeve
17 matches
Mail list logo