Posted to Architecture group.

On Mon, Sep 9, 2013 at 3:10 PM, Chamara Ariyarathne <[email protected]>wrote:

> https://wso2.org/jira/browse/BAM-809
> https://wso2.org/jira/browse/BAM-880
> https://wso2.org/jira/browse/ESBJAVA-2410
>
>
> On Mon, Sep 9, 2013 at 3:01 PM, Chamara Ariyarathne <[email protected]>wrote:
>
>> This has been a doubt for several products as I have seen issues while
>> Statistics publishing, Accessing management consoles etc.
>>
>> When the
>>     <!--
>>        Host name or IP address of the machine hosting this server
>>        e.g. www.wso2.org, 192.168.1.10
>>        This is will become part of the End Point Reference of the
>>        services deployed on this server instance.
>>      -->
>>     <!--HostName>localhost</HostName-->
>>
>> property is not set, and when the carbon server is started on a Ubuntu
>> machine, the pickup of host name happens differently for several services.
>>
>> I saw this recently with API Manager.
>>
>> As you can see here.
>>
>> [2013-09-09 09:11:59,167]  INFO - PassThroughHttpSSLListener Pass-through
>> HTTPS Listener started on 0:0:0:0:0:0:0:0:8243
>> [2013-09-09 09:11:59,168]  INFO - PassThroughHttpListener Starting
>> Pass-through HTTP Listener...
>> [2013-09-09 09:11:59,169]  INFO - PassThroughHttpListener Pass-through
>> HTTP Listener started on 0:0:0:0:0:0:0:0:8280
>> [2013-09-09 09:11:59,173]  INFO - NioSelectorPool Using a shared selector
>> for servlet write/read
>> [2013-09-09 09:11:59,202]  INFO - NioSelectorPool Using a shared selector
>> for servlet write/read
>> [2013-09-09 09:11:59,275]  INFO - TaskServiceImpl Task service starting
>> in STANDALONE mode...
>> [2013-09-09 09:11:59,293]  INFO - RegistryEventingServiceComponent
>> Successfully Initialized Eventing on Registry
>> [2013-09-09 09:11:59,394]  INFO - JMXServerManager JMX Service URL  :
>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>> [2013-09-09 09:11:59,394]  INFO - StartupFinalizerServiceComponent Server
>>           :  WSO2 API Manager-1.5.0
>> [2013-09-09 09:11:59,395]  INFO - StartupFinalizerServiceComponent WSO2
>> Carbon started in 55 sec
>> [2013-09-09 09:12:00,322]  INFO - CarbonUIServiceComponent Mgt Console
>> URL  : https://localhost:9443/carbon/
>> [2013-09-09 09:12:00,322]  INFO - CarbonUIServiceComponent API Publisher
>> Default Context : http://localhost:9763/publisher
>> [2013-09-09 09:12:00,322]  INFO - CarbonUIServiceComponent API Store
>> Default Context : http://localhost:9763/store
>> [2013-09-09 09:12:00,408]  INFO - APIKeyMgtServiceComponent Setting
>> default carbon host for thrift key management service: 10.100.1.90
>> [2013-09-09 09:12:00,429]  INFO - APIKeyMgtServiceComponent Started
>> thrift key mgt service at port:10398
>>
>> UI services are bound to "localhost" and "APIKeyMgtServiceComponent" is
>> bound to the ipaddress "10.100.1.90"
>>
>> One can argue since this is same machine this is no problem. But I've
>> seen the Key Management services fail when the KeyMgt Server is bound to ip
>> and client in the same Carbon server calls to localhost.
>>
>> And this can be more troublesome when One machine has more than one
>> network interfaces.
>>
>>
>> --
>> *Chamara Ariyarathne*
>> Senior Software Engineer - QA;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; *+94772786766*
>>
>
>
>
> --
> *Chamara Ariyarathne*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *+94772786766*
>



-- 
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to