You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Chamila De Alwis <ch...@wso2.com> on 2014/09/07 19:49:57 UTC
Access URL not accessible with load balancing
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. However the domain name of the php cartridge (
helloworld.stratos.com) is missing from load balancer's log.
TID: [0] [LB] [2014-09-07 15:41:16,733] INFO
{org.apache.stratos.messaging.message.processor.topology.MemberStartedMessageProcessor}
- Member started: [service] php [cluster] helloworld.php.domain [member]
helloworld.php.domaine70b695a-1ca0-4b84-9d99-2f1ae5b25f63
TID: [0] [LB] [2014-09-07 15:41:26,329] INFO
{org.apache.stratos.messaging.message.processor.topology.MemberActivatedMessageProcessor}
- Member activated: [service] php [cluster] helloworld.php.domain [member]
helloworld.php.domaine70b695a-1ca0-4b84-9d99-2f1ae5b25f63
I have mapped the load balancer's public IP with the provided domain name
in the /etc/hosts file. However I can't access the url provided by the
subscribed cartridge (http://helloworld.stratos.com:8280).
I can independently access the php cartridge through its public IP. And I
can access the cartridge with load balancing through the port 80 (
http://helloworld.stratos.com).
I assume it's something to do with the proxyPort port mapping specified in
the cartridge deployment but I'm not clear on the details.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
Re: Access URL not accessible with load balancing
Posted by Udara Liyanage <ud...@wso2.com>.
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.
Re: Access URL not accessible with load balancing
Posted by Prasanna Dangalla <pr...@wso2.com>.
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 <ni...@gmail.com>
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 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
> number of transport receivers in LB). Hence, if you require a Cartridge to
> be load balanced, and then it's a must to define the port mapping and it's
> not practical to define a default value due to the fact that people have
> the liberty to change the transport receiver configurations in LB.
>
> On Tue, Sep 9, 2014 at 8:36 AM, Akila Ravihansa Perera <ravihansa@wso2.com
> > wrote:
>
>> 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" <pr...@wso2.com> wrote:
>>
>>> Hi sajith,
>>>
>>> In LB's axis2.xml file. (in <LB_HOME>/repository/conf/axis2/axis2.xml),
>>> the below mentioned part is commented. Is this the reason because ports
>>> 8280 and 8243 are commented in this.
>>>
>>> <!-- uncomment for non blocking http transport based on HttpCore +
>>> NIO extensions -->
>>> <!-- transportReceiver name="http"
>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
>>> <parameter name="port" locked="false">8280</parameter>
>>> <parameter name="non-blocking" locked="false">true</parameter -->
>>> <!--parameter name="bind-address" locked="false">hostname or IP
>>> address</parameter-->
>>> <!--parameter name="WSDLEPRPrefix"
>>> locked="false">https://apachehost:port/somepath</parameter-->
>>> <!-- parameter name="httpGetProcessor"
>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>> </transportReceiver -->
>>>
>>> <!-- the non blocking https transport based on HttpCore + SSL-NIO
>>> extensions -->
>>> <!-- transportReceiver name="https"
>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
>>> <parameter name="port" locked="false">8243</parameter>
>>> <parameter name="non-blocking" locked="false">true</parameter -->
>>> <!--parameter name="bind-address" locked="false">hostname or IP
>>> address</parameter-->
>>> <!--parameter name="WSDLEPRPrefix"
>>> locked="false">https://apachehost:port/somepath</parameter-->
>>> <!-- parameter name="httpGetProcessor"
>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>> <parameter name="keystore" locked="false">
>>> <KeyStore>
>>>
>>> <Location>repository/resources/security/wso2carbon.jks</Location>
>>> <Type>JKS</Type>
>>> <Password>wso2carbon</Password>
>>> <KeyPassword>wso2carbon</KeyPassword>
>>> </KeyStore>
>>> </parameter>
>>> <parameter name="truststore" locked="false">
>>> <TrustStore>
>>>
>>> <Location>repository/resources/security/client-truststore.jks</Location>
>>> <Type>JKS</Type>
>>> <Password>wso2carbon</Password>
>>> </TrustStore>
>>> </parameter -->
>>> <!--<parameter name="SSLVerifyClient">require</parameter>
>>> supports optional|require or defaults to none -->
>>> <!-- /transportReceiver -->
>>>
>>>
>>> On Tue, Sep 9, 2014 at 12:04 AM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>> 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 <ud...@wso2.com> wrote:
>>>>
>>>>> Instead of 0 could you try with 80.
>>>>>
>>>>>
>>>>>
>>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Prasanna Dangalla
>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> cell: +94 777 55 80 30 | +94 718 11 27 51
>>> twitter: @prasa77
>>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Prasanna Dangalla
Software Engineer, WSO2, Inc.; http://wso2.com/
lean.enterprise.middleware
cell: +94 777 55 80 30 | +94 718 11 27 51
twitter: @prasa77
Re: Access URL not accessible with load balancing
Posted by Prasanna Dangalla <pr...@wso2.com>.
Hi Udara,
axis2.xml is attached herewith
Thanks
On Tue, Sep 9, 2014 at 9:58 AM, Chamila De Alwis <ch...@wso2.com> 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 transportReceiver port is
> defined at the nodes.pp as port 80 by default ($lb_httpPort)[1]. If the LB
> should accept requests at the port defined by the cartridge definition,
> shouldn't it be passed to LB through launch parameters or through the
> member activate event?
>
> [1] -
> https://github.com/apache/stratos/blob/4.0.0-rc4/tools/puppet3/manifests/nodes.pp
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Tue, Sep 9, 2014 at 8:57 AM, Nirmal Fernando <ni...@gmail.com>
> 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 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
>> number of transport receivers in LB). Hence, if you require a Cartridge to
>> be load balanced, and then it's a must to define the port mapping and it's
>> not practical to define a default value due to the fact that people have
>> the liberty to change the transport receiver configurations in LB.
>>
>> On Tue, Sep 9, 2014 at 8:36 AM, Akila Ravihansa Perera <
>> ravihansa@wso2.com> wrote:
>>
>>> 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" <pr...@wso2.com> wrote:
>>>
>>>> Hi sajith,
>>>>
>>>> In LB's axis2.xml file. (in <LB_HOME>/repository/conf/axis2/axis2.xml),
>>>> the below mentioned part is commented. Is this the reason because ports
>>>> 8280 and 8243 are commented in this.
>>>>
>>>> <!-- uncomment for non blocking http transport based on HttpCore +
>>>> NIO extensions -->
>>>> <!-- transportReceiver name="http"
>>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
>>>> <parameter name="port" locked="false">8280</parameter>
>>>> <parameter name="non-blocking" locked="false">true</parameter
>>>> -->
>>>> <!--parameter name="bind-address" locked="false">hostname or IP
>>>> address</parameter-->
>>>> <!--parameter name="WSDLEPRPrefix"
>>>> locked="false">https://apachehost:port/somepath</parameter-->
>>>> <!-- parameter name="httpGetProcessor"
>>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>>> </transportReceiver -->
>>>>
>>>> <!-- the non blocking https transport based on HttpCore + SSL-NIO
>>>> extensions -->
>>>> <!-- transportReceiver name="https"
>>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
>>>> <parameter name="port" locked="false">8243</parameter>
>>>> <parameter name="non-blocking" locked="false">true</parameter
>>>> -->
>>>> <!--parameter name="bind-address" locked="false">hostname or IP
>>>> address</parameter-->
>>>> <!--parameter name="WSDLEPRPrefix"
>>>> locked="false">https://apachehost:port/somepath</parameter-->
>>>> <!-- parameter name="httpGetProcessor"
>>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>>> <parameter name="keystore" locked="false">
>>>> <KeyStore>
>>>>
>>>> <Location>repository/resources/security/wso2carbon.jks</Location>
>>>> <Type>JKS</Type>
>>>> <Password>wso2carbon</Password>
>>>> <KeyPassword>wso2carbon</KeyPassword>
>>>> </KeyStore>
>>>> </parameter>
>>>> <parameter name="truststore" locked="false">
>>>> <TrustStore>
>>>>
>>>> <Location>repository/resources/security/client-truststore.jks</Location>
>>>> <Type>JKS</Type>
>>>> <Password>wso2carbon</Password>
>>>> </TrustStore>
>>>> </parameter -->
>>>> <!--<parameter name="SSLVerifyClient">require</parameter>
>>>> supports optional|require or defaults to none -->
>>>> <!-- /transportReceiver -->
>>>>
>>>>
>>>> On Tue, Sep 9, 2014 at 12:04 AM, Chamila De Alwis <ch...@wso2.com>
>>>> wrote:
>>>>
>>>>> 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 <ud...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Instead of 0 could you try with 80.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Prasanna Dangalla
>>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>>> lean.enterprise.middleware
>>>>
>>>> cell: +94 777 55 80 30 | +94 718 11 27 51
>>>> twitter: @prasa77
>>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
--
Prasanna Dangalla
Software Engineer, WSO2, Inc.; http://wso2.com/
lean.enterprise.middleware
cell: +94 777 55 80 30 | +94 718 11 27 51
twitter: @prasa77
Re: Access URL not accessible with load balancing
Posted by Prasanna Dangalla <pr...@wso2.com>.
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 <ni...@gmail.com>
wrote:
>
>
> On Tue, Sep 9, 2014 at 9:58 AM, Chamila De Alwis <ch...@wso2.com>
> 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.)
>
>>
>> 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 requests at the port defined by the cartridge definition,
>> shouldn't it be passed to LB through launch parameters or through the
>> member activate event?
>>
>
>> [1] -
>> https://github.com/apache/stratos/blob/4.0.0-rc4/tools/puppet3/manifests/nodes.pp
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Tue, Sep 9, 2014 at 8:57 AM, Nirmal Fernando <ni...@gmail.com>
>> 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 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
>>> number of transport receivers in LB). Hence, if you require a Cartridge to
>>> be load balanced, and then it's a must to define the port mapping and it's
>>> not practical to define a default value due to the fact that people have
>>> the liberty to change the transport receiver configurations in LB.
>>>
>>> On Tue, Sep 9, 2014 at 8:36 AM, Akila Ravihansa Perera <
>>> ravihansa@wso2.com> wrote:
>>>
>>>> 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" <pr...@wso2.com> wrote:
>>>>
>>>>> Hi sajith,
>>>>>
>>>>> In LB's axis2.xml file. (in
>>>>> <LB_HOME>/repository/conf/axis2/axis2.xml), the below mentioned part is
>>>>> commented. Is this the reason because ports 8280 and 8243 are commented in
>>>>> this.
>>>>>
>>>>> <!-- uncomment for non blocking http transport based on HttpCore +
>>>>> NIO extensions -->
>>>>> <!-- transportReceiver name="http"
>>>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
>>>>> <parameter name="port" locked="false">8280</parameter>
>>>>> <parameter name="non-blocking" locked="false">true</parameter
>>>>> -->
>>>>> <!--parameter name="bind-address" locked="false">hostname or
>>>>> IP address</parameter-->
>>>>> <!--parameter name="WSDLEPRPrefix"
>>>>> locked="false">https://apachehost:port/somepath</parameter-->
>>>>> <!-- parameter name="httpGetProcessor"
>>>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>>>> </transportReceiver -->
>>>>>
>>>>> <!-- the non blocking https transport based on HttpCore + SSL-NIO
>>>>> extensions -->
>>>>> <!-- transportReceiver name="https"
>>>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
>>>>> <parameter name="port" locked="false">8243</parameter>
>>>>> <parameter name="non-blocking" locked="false">true</parameter
>>>>> -->
>>>>> <!--parameter name="bind-address" locked="false">hostname or
>>>>> IP address</parameter-->
>>>>> <!--parameter name="WSDLEPRPrefix"
>>>>> locked="false">https://apachehost:port/somepath</parameter-->
>>>>> <!-- parameter name="httpGetProcessor"
>>>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>>>> <parameter name="keystore" locked="false">
>>>>> <KeyStore>
>>>>>
>>>>> <Location>repository/resources/security/wso2carbon.jks</Location>
>>>>> <Type>JKS</Type>
>>>>> <Password>wso2carbon</Password>
>>>>> <KeyPassword>wso2carbon</KeyPassword>
>>>>> </KeyStore>
>>>>> </parameter>
>>>>> <parameter name="truststore" locked="false">
>>>>> <TrustStore>
>>>>>
>>>>> <Location>repository/resources/security/client-truststore.jks</Location>
>>>>> <Type>JKS</Type>
>>>>> <Password>wso2carbon</Password>
>>>>> </TrustStore>
>>>>> </parameter -->
>>>>> <!--<parameter name="SSLVerifyClient">require</parameter>
>>>>> supports optional|require or defaults to none -->
>>>>> <!-- /transportReceiver -->
>>>>>
>>>>>
>>>>> On Tue, Sep 9, 2014 at 12:04 AM, Chamila De Alwis <ch...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> 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 <ud...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Instead of 0 could you try with 80.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Prasanna Dangalla
>>>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>>>> lean.enterprise.middleware
>>>>>
>>>>> cell: +94 777 55 80 30 | +94 718 11 27 51
>>>>> twitter: @prasa77
>>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Prasanna Dangalla
Software Engineer, WSO2, Inc.; http://wso2.com/
lean.enterprise.middleware
cell: +94 777 55 80 30 | +94 718 11 27 51
twitter: @prasa77
Re: Access URL not accessible with load balancing
Posted by Nirmal Fernando <ni...@gmail.com>.
On Tue, Sep 9, 2014 at 9:58 AM, Chamila De Alwis <ch...@wso2.com> 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.)
>
> 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 requests at the port defined by the cartridge definition,
> shouldn't it be passed to LB through launch parameters or through the
> member activate event?
>
> [1] -
> https://github.com/apache/stratos/blob/4.0.0-rc4/tools/puppet3/manifests/nodes.pp
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Tue, Sep 9, 2014 at 8:57 AM, Nirmal Fernando <ni...@gmail.com>
> 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 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
>> number of transport receivers in LB). Hence, if you require a Cartridge to
>> be load balanced, and then it's a must to define the port mapping and it's
>> not practical to define a default value due to the fact that people have
>> the liberty to change the transport receiver configurations in LB.
>>
>> On Tue, Sep 9, 2014 at 8:36 AM, Akila Ravihansa Perera <
>> ravihansa@wso2.com> wrote:
>>
>>> 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" <pr...@wso2.com> wrote:
>>>
>>>> Hi sajith,
>>>>
>>>> In LB's axis2.xml file. (in <LB_HOME>/repository/conf/axis2/axis2.xml),
>>>> the below mentioned part is commented. Is this the reason because ports
>>>> 8280 and 8243 are commented in this.
>>>>
>>>> <!-- uncomment for non blocking http transport based on HttpCore +
>>>> NIO extensions -->
>>>> <!-- transportReceiver name="http"
>>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
>>>> <parameter name="port" locked="false">8280</parameter>
>>>> <parameter name="non-blocking" locked="false">true</parameter
>>>> -->
>>>> <!--parameter name="bind-address" locked="false">hostname or IP
>>>> address</parameter-->
>>>> <!--parameter name="WSDLEPRPrefix"
>>>> locked="false">https://apachehost:port/somepath</parameter-->
>>>> <!-- parameter name="httpGetProcessor"
>>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>>> </transportReceiver -->
>>>>
>>>> <!-- the non blocking https transport based on HttpCore + SSL-NIO
>>>> extensions -->
>>>> <!-- transportReceiver name="https"
>>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
>>>> <parameter name="port" locked="false">8243</parameter>
>>>> <parameter name="non-blocking" locked="false">true</parameter
>>>> -->
>>>> <!--parameter name="bind-address" locked="false">hostname or IP
>>>> address</parameter-->
>>>> <!--parameter name="WSDLEPRPrefix"
>>>> locked="false">https://apachehost:port/somepath</parameter-->
>>>> <!-- parameter name="httpGetProcessor"
>>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>>> <parameter name="keystore" locked="false">
>>>> <KeyStore>
>>>>
>>>> <Location>repository/resources/security/wso2carbon.jks</Location>
>>>> <Type>JKS</Type>
>>>> <Password>wso2carbon</Password>
>>>> <KeyPassword>wso2carbon</KeyPassword>
>>>> </KeyStore>
>>>> </parameter>
>>>> <parameter name="truststore" locked="false">
>>>> <TrustStore>
>>>>
>>>> <Location>repository/resources/security/client-truststore.jks</Location>
>>>> <Type>JKS</Type>
>>>> <Password>wso2carbon</Password>
>>>> </TrustStore>
>>>> </parameter -->
>>>> <!--<parameter name="SSLVerifyClient">require</parameter>
>>>> supports optional|require or defaults to none -->
>>>> <!-- /transportReceiver -->
>>>>
>>>>
>>>> On Tue, Sep 9, 2014 at 12:04 AM, Chamila De Alwis <ch...@wso2.com>
>>>> wrote:
>>>>
>>>>> 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 <ud...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Instead of 0 could you try with 80.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Prasanna Dangalla
>>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>>> lean.enterprise.middleware
>>>>
>>>> cell: +94 777 55 80 30 | +94 718 11 27 51
>>>> twitter: @prasa77
>>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Access URL not accessible with load balancing
Posted by Chamila De Alwis <ch...@wso2.com>.
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 requests at the port defined by the cartridge definition,
shouldn't it be passed to LB through launch parameters or through the
member activate event?
[1] -
https://github.com/apache/stratos/blob/4.0.0-rc4/tools/puppet3/manifests/nodes.pp
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Tue, Sep 9, 2014 at 8:57 AM, Nirmal Fernando <ni...@gmail.com>
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 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
> number of transport receivers in LB). Hence, if you require a Cartridge to
> be load balanced, and then it's a must to define the port mapping and it's
> not practical to define a default value due to the fact that people have
> the liberty to change the transport receiver configurations in LB.
>
> On Tue, Sep 9, 2014 at 8:36 AM, Akila Ravihansa Perera <ravihansa@wso2.com
> > wrote:
>
>> 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" <pr...@wso2.com> wrote:
>>
>>> Hi sajith,
>>>
>>> In LB's axis2.xml file. (in <LB_HOME>/repository/conf/axis2/axis2.xml),
>>> the below mentioned part is commented. Is this the reason because ports
>>> 8280 and 8243 are commented in this.
>>>
>>> <!-- uncomment for non blocking http transport based on HttpCore +
>>> NIO extensions -->
>>> <!-- transportReceiver name="http"
>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
>>> <parameter name="port" locked="false">8280</parameter>
>>> <parameter name="non-blocking" locked="false">true</parameter -->
>>> <!--parameter name="bind-address" locked="false">hostname or IP
>>> address</parameter-->
>>> <!--parameter name="WSDLEPRPrefix"
>>> locked="false">https://apachehost:port/somepath</parameter-->
>>> <!-- parameter name="httpGetProcessor"
>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>> </transportReceiver -->
>>>
>>> <!-- the non blocking https transport based on HttpCore + SSL-NIO
>>> extensions -->
>>> <!-- transportReceiver name="https"
>>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
>>> <parameter name="port" locked="false">8243</parameter>
>>> <parameter name="non-blocking" locked="false">true</parameter -->
>>> <!--parameter name="bind-address" locked="false">hostname or IP
>>> address</parameter-->
>>> <!--parameter name="WSDLEPRPrefix"
>>> locked="false">https://apachehost:port/somepath</parameter-->
>>> <!-- parameter name="httpGetProcessor"
>>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>>> <parameter name="keystore" locked="false">
>>> <KeyStore>
>>>
>>> <Location>repository/resources/security/wso2carbon.jks</Location>
>>> <Type>JKS</Type>
>>> <Password>wso2carbon</Password>
>>> <KeyPassword>wso2carbon</KeyPassword>
>>> </KeyStore>
>>> </parameter>
>>> <parameter name="truststore" locked="false">
>>> <TrustStore>
>>>
>>> <Location>repository/resources/security/client-truststore.jks</Location>
>>> <Type>JKS</Type>
>>> <Password>wso2carbon</Password>
>>> </TrustStore>
>>> </parameter -->
>>> <!--<parameter name="SSLVerifyClient">require</parameter>
>>> supports optional|require or defaults to none -->
>>> <!-- /transportReceiver -->
>>>
>>>
>>> On Tue, Sep 9, 2014 at 12:04 AM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>> 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 <ud...@wso2.com> wrote:
>>>>
>>>>> Instead of 0 could you try with 80.
>>>>>
>>>>>
>>>>>
>>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Prasanna Dangalla
>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> cell: +94 777 55 80 30 | +94 718 11 27 51
>>> twitter: @prasa77
>>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
Re: Access URL not accessible with load balancing
Posted by Nirmal Fernando <ni...@gmail.com>.
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
number of transport receivers in LB). Hence, if you require a Cartridge to
be load balanced, and then it's a must to define the port mapping and it's
not practical to define a default value due to the fact that people have
the liberty to change the transport receiver configurations in LB.
On Tue, Sep 9, 2014 at 8:36 AM, Akila Ravihansa Perera <ra...@wso2.com>
wrote:
> 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" <pr...@wso2.com> wrote:
>
>> Hi sajith,
>>
>> In LB's axis2.xml file. (in <LB_HOME>/repository/conf/axis2/axis2.xml),
>> the below mentioned part is commented. Is this the reason because ports
>> 8280 and 8243 are commented in this.
>>
>> <!-- uncomment for non blocking http transport based on HttpCore +
>> NIO extensions -->
>> <!-- transportReceiver name="http"
>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
>> <parameter name="port" locked="false">8280</parameter>
>> <parameter name="non-blocking" locked="false">true</parameter -->
>> <!--parameter name="bind-address" locked="false">hostname or IP
>> address</parameter-->
>> <!--parameter name="WSDLEPRPrefix"
>> locked="false">https://apachehost:port/somepath</parameter-->
>> <!-- parameter name="httpGetProcessor"
>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>> </transportReceiver -->
>>
>> <!-- the non blocking https transport based on HttpCore + SSL-NIO
>> extensions -->
>> <!-- transportReceiver name="https"
>> class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
>> <parameter name="port" locked="false">8243</parameter>
>> <parameter name="non-blocking" locked="false">true</parameter -->
>> <!--parameter name="bind-address" locked="false">hostname or IP
>> address</parameter-->
>> <!--parameter name="WSDLEPRPrefix"
>> locked="false">https://apachehost:port/somepath</parameter-->
>> <!-- parameter name="httpGetProcessor"
>> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
>> <parameter name="keystore" locked="false">
>> <KeyStore>
>>
>> <Location>repository/resources/security/wso2carbon.jks</Location>
>> <Type>JKS</Type>
>> <Password>wso2carbon</Password>
>> <KeyPassword>wso2carbon</KeyPassword>
>> </KeyStore>
>> </parameter>
>> <parameter name="truststore" locked="false">
>> <TrustStore>
>>
>> <Location>repository/resources/security/client-truststore.jks</Location>
>> <Type>JKS</Type>
>> <Password>wso2carbon</Password>
>> </TrustStore>
>> </parameter -->
>> <!--<parameter name="SSLVerifyClient">require</parameter>
>> supports optional|require or defaults to none -->
>> <!-- /transportReceiver -->
>>
>>
>> On Tue, Sep 9, 2014 at 12:04 AM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>> 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 <ud...@wso2.com> wrote:
>>>
>>>> Instead of 0 could you try with 80.
>>>>
>>>>
>>>>
>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>
>>>
>>>
>>
>>
>> --
>> Prasanna Dangalla
>> Software Engineer, WSO2, Inc.; http://wso2.com/
>> lean.enterprise.middleware
>>
>> cell: +94 777 55 80 30 | +94 718 11 27 51
>> twitter: @prasa77
>>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Access URL not accessible with load balancing
Posted by Akila Ravihansa Perera <ra...@wso2.com>.
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" <pr...@wso2.com> wrote:
> Hi sajith,
>
> In LB's axis2.xml file. (in <LB_HOME>/repository/conf/axis2/axis2.xml),
> the below mentioned part is commented. Is this the reason because ports
> 8280 and 8243 are commented in this.
>
> <!-- uncomment for non blocking http transport based on HttpCore + NIO
> extensions -->
> <!-- transportReceiver name="http"
> class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
> <parameter name="port" locked="false">8280</parameter>
> <parameter name="non-blocking" locked="false">true</parameter -->
> <!--parameter name="bind-address" locked="false">hostname or IP
> address</parameter-->
> <!--parameter name="WSDLEPRPrefix"
> locked="false">https://apachehost:port/somepath</parameter-->
> <!-- parameter name="httpGetProcessor"
> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
> </transportReceiver -->
>
> <!-- the non blocking https transport based on HttpCore + SSL-NIO
> extensions -->
> <!-- transportReceiver name="https"
> class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
> <parameter name="port" locked="false">8243</parameter>
> <parameter name="non-blocking" locked="false">true</parameter -->
> <!--parameter name="bind-address" locked="false">hostname or IP
> address</parameter-->
> <!--parameter name="WSDLEPRPrefix"
> locked="false">https://apachehost:port/somepath</parameter-->
> <!-- parameter name="httpGetProcessor"
> locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
> <parameter name="keystore" locked="false">
> <KeyStore>
>
> <Location>repository/resources/security/wso2carbon.jks</Location>
> <Type>JKS</Type>
> <Password>wso2carbon</Password>
> <KeyPassword>wso2carbon</KeyPassword>
> </KeyStore>
> </parameter>
> <parameter name="truststore" locked="false">
> <TrustStore>
>
> <Location>repository/resources/security/client-truststore.jks</Location>
> <Type>JKS</Type>
> <Password>wso2carbon</Password>
> </TrustStore>
> </parameter -->
> <!--<parameter name="SSLVerifyClient">require</parameter>
> supports optional|require or defaults to none -->
> <!-- /transportReceiver -->
>
>
> On Tue, Sep 9, 2014 at 12:04 AM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> 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 <ud...@wso2.com> wrote:
>>
>>> Instead of 0 could you try with 80.
>>>
>>>
>>>
>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>
>>
>>
>
>
> --
> Prasanna Dangalla
> Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
> cell: +94 777 55 80 30 | +94 718 11 27 51
> twitter: @prasa77
>
Re: Access URL not accessible with load balancing
Posted by Prasanna Dangalla <pr...@wso2.com>.
Hi sajith,
In LB's axis2.xml file. (in <LB_HOME>/repository/conf/axis2/axis2.xml), the
below mentioned part is commented. Is this the reason because ports 8280
and 8243 are commented in this.
<!-- uncomment for non blocking http transport based on HttpCore + NIO
extensions -->
<!-- transportReceiver name="http"
class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
<parameter name="port" locked="false">8280</parameter>
<parameter name="non-blocking" locked="false">true</parameter -->
<!--parameter name="bind-address" locked="false">hostname or IP
address</parameter-->
<!--parameter name="WSDLEPRPrefix"
locked="false">https://apachehost:port/somepath</parameter-->
<!-- parameter name="httpGetProcessor"
locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
</transportReceiver -->
<!-- the non blocking https transport based on HttpCore + SSL-NIO
extensions -->
<!-- transportReceiver name="https"
class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
<parameter name="port" locked="false">8243</parameter>
<parameter name="non-blocking" locked="false">true</parameter -->
<!--parameter name="bind-address" locked="false">hostname or IP
address</parameter-->
<!--parameter name="WSDLEPRPrefix"
locked="false">https://apachehost:port/somepath</parameter-->
<!-- parameter name="httpGetProcessor"
locked="false">org.wso2.carbon.transport.nhttp.api.NHttpGetProcessor</parameter>
<parameter name="keystore" locked="false">
<KeyStore>
<Location>repository/resources/security/wso2carbon.jks</Location>
<Type>JKS</Type>
<Password>wso2carbon</Password>
<KeyPassword>wso2carbon</KeyPassword>
</KeyStore>
</parameter>
<parameter name="truststore" locked="false">
<TrustStore>
<Location>repository/resources/security/client-truststore.jks</Location>
<Type>JKS</Type>
<Password>wso2carbon</Password>
</TrustStore>
</parameter -->
<!--<parameter name="SSLVerifyClient">require</parameter>
supports optional|require or defaults to none -->
<!-- /transportReceiver -->
On Tue, Sep 9, 2014 at 12:04 AM, Chamila De Alwis <ch...@wso2.com> wrote:
> 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 <ud...@wso2.com> wrote:
>
>> Instead of 0 could you try with 80.
>>
>>
>>
>> Touched, not typed. Erroneous words are a feature, not a typo.
>>
>
>
--
Prasanna Dangalla
Software Engineer, WSO2, Inc.; http://wso2.com/
lean.enterprise.middleware
cell: +94 777 55 80 30 | +94 718 11 27 51
twitter: @prasa77
Re: Access URL not accessible with load balancing
Posted by Chamila De Alwis <ch...@wso2.com>.
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 <ud...@wso2.com> wrote:
> Instead of 0 could you try with 80.
>
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
>
Re: Access URL not accessible with load balancing
Posted by Udara Liyanage <ud...@wso2.com>.
Instead of 0 could you try with 80.
Touched, not typed. Erroneous words are a feature, not a typo.
Re: Access URL not accessible with load balancing
Posted by Chamila De Alwis <ch...@wso2.com>.
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 0?
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Mon, Sep 8, 2014 at 7:28 PM, Udara Liyanage <ud...@wso2.com> wrote:
>
> 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.
>
Re: Access URL not accessible with load balancing
Posted by Udara Liyanage <ud...@wso2.com>.
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.
Re: Access URL not accessible with load balancing
Posted by Chamila De Alwis <ch...@wso2.com>.
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 <sa...@wso2.com> wrote:
> Hi Chamila,
>
> Please check the port values in LB's axis2.xml file. (in
> <LB_HOME>/repository/conf/axis2/axis2.xml),
> <transportReceiver name="http" section
>
> I think those values are set via puppet. So you will have to configure
> those values in puppet master accordingly
>
> Thanks,
> Sajith
>
> On Mon, Sep 8, 2014 at 3:10 PM, Chamila De Alwis <ch...@wso2.com>
> 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,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Sun, Sep 7, 2014 at 11:19 PM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>> 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. However the domain name of the php cartridge (
>>> helloworld.stratos.com) is missing from load balancer's log.
>>>
>>> TID: [0] [LB] [2014-09-07 15:41:16,733] INFO
>>> {org.apache.stratos.messaging.message.processor.topology.MemberStartedMessageProcessor}
>>> - Member started: [service] php [cluster] helloworld.php.domain [member]
>>> helloworld.php.domaine70b695a-1ca0-4b84-9d99-2f1ae5b25f63
>>> TID: [0] [LB] [2014-09-07 15:41:26,329] INFO
>>> {org.apache.stratos.messaging.message.processor.topology.MemberActivatedMessageProcessor}
>>> - Member activated: [service] php [cluster] helloworld.php.domain [member]
>>> helloworld.php.domaine70b695a-1ca0-4b84-9d99-2f1ae5b25f63
>>>
>>> I have mapped the load balancer's public IP with the provided domain
>>> name in the /etc/hosts file. However I can't access the url provided by the
>>> subscribed cartridge (http://helloworld.stratos.com:8280).
>>>
>>> I can independently access the php cartridge through its public IP. And
>>> I can access the cartridge with load balancing through the port 80 (
>>> http://helloworld.stratos.com).
>>>
>>> I assume it's something to do with the proxyPort port mapping specified
>>> in the cartridge deployment but I'm not clear on the details.
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>
>
>
> --
> *--*
> *Sajith Kariyawasam*
> *Mobile: +94772269575 <%2B94772269575>*
>
Re: Access URL not accessible with load balancing
Posted by Sajith Kariyawasam <sa...@wso2.com>.
Hi Chamila,
Please check the port values in LB's axis2.xml file. (in
<LB_HOME>/repository/conf/axis2/axis2.xml),
<transportReceiver name="http" section
I think those values are set via puppet. So you will have to configure
those values in puppet master accordingly
Thanks,
Sajith
On Mon, Sep 8, 2014 at 3:10 PM, Chamila De Alwis <ch...@wso2.com> 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,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Sun, Sep 7, 2014 at 11:19 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> 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. However the domain name of the php cartridge (
>> helloworld.stratos.com) is missing from load balancer's log.
>>
>> TID: [0] [LB] [2014-09-07 15:41:16,733] INFO
>> {org.apache.stratos.messaging.message.processor.topology.MemberStartedMessageProcessor}
>> - Member started: [service] php [cluster] helloworld.php.domain [member]
>> helloworld.php.domaine70b695a-1ca0-4b84-9d99-2f1ae5b25f63
>> TID: [0] [LB] [2014-09-07 15:41:26,329] INFO
>> {org.apache.stratos.messaging.message.processor.topology.MemberActivatedMessageProcessor}
>> - Member activated: [service] php [cluster] helloworld.php.domain [member]
>> helloworld.php.domaine70b695a-1ca0-4b84-9d99-2f1ae5b25f63
>>
>> I have mapped the load balancer's public IP with the provided domain name
>> in the /etc/hosts file. However I can't access the url provided by the
>> subscribed cartridge (http://helloworld.stratos.com:8280).
>>
>> I can independently access the php cartridge through its public IP. And I
>> can access the cartridge with load balancing through the port 80 (
>> http://helloworld.stratos.com).
>>
>> I assume it's something to do with the proxyPort port mapping specified
>> in the cartridge deployment but I'm not clear on the details.
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
--
*--*
*Sajith Kariyawasam*
*Mobile: +94772269575*
Re: Access URL not accessible with load balancing
Posted by Chamila De Alwis <ch...@wso2.com>.
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 Alwis <ch...@wso2.com> wrote:
> 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. However the domain name of the php cartridge (
> helloworld.stratos.com) is missing from load balancer's log.
>
> TID: [0] [LB] [2014-09-07 15:41:16,733] INFO
> {org.apache.stratos.messaging.message.processor.topology.MemberStartedMessageProcessor}
> - Member started: [service] php [cluster] helloworld.php.domain [member]
> helloworld.php.domaine70b695a-1ca0-4b84-9d99-2f1ae5b25f63
> TID: [0] [LB] [2014-09-07 15:41:26,329] INFO
> {org.apache.stratos.messaging.message.processor.topology.MemberActivatedMessageProcessor}
> - Member activated: [service] php [cluster] helloworld.php.domain [member]
> helloworld.php.domaine70b695a-1ca0-4b84-9d99-2f1ae5b25f63
>
> I have mapped the load balancer's public IP with the provided domain name
> in the /etc/hosts file. However I can't access the url provided by the
> subscribed cartridge (http://helloworld.stratos.com:8280).
>
> I can independently access the php cartridge through its public IP. And I
> can access the cartridge with load balancing through the port 80 (
> http://helloworld.stratos.com).
>
> I assume it's something to do with the proxyPort port mapping specified in
> the cartridge deployment but I'm not clear on the details.
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>