On Wed, Jul 30, 2014 at 12:33 PM, Sewwandi Perera <sewwa...@wso2.com> wrote:
> Hi Kishanthan,
>
> I debugged the code and found that HazelcastClusteringAgent's init method
> is never hit when AvoidInitiation is set to true.
>
Then there seems to an issue at your end. The cluster initialization is
handled within this method. It should get called once, if the cluster
configuration are correct as mentioned above. If not, the clustering will
not work. By default we set AvoidInitiation to true because, carbon kernel
does the cluster initialization once the transport is properly initialized.
>
> For more information; I access the Hazelcast OSGI service as shown below
> with the cardinality "0..1" since I don't use the Hazelcast instance in
> standalone
> mode.
>
> * @scr.reference name="hazelcast.instance.service"
> *
> interface="com.hazelcast.core.HazelcastInstance"
> * cardinality="0..1"
> * policy="dynamic"
> * bind="setHazelcastInstance"
> * unbind="unsetHazelcastInstance"
>
This is fine.
>
> Thanks and Regards,
> Sewwandi
>
>
> On Tue, Jul 29, 2014 at 4:10 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> -- Sent from mobile --
>>
>> On 29 Jul 2014 14:50, "Sewwandi Perera" <sewwa...@wso2.com> wrote:
>> >
>> > Hi,
>> >
>> > We observed that the UI issue has come as a result of below
>> configuration in axis2.xml.
>> > <parameter name="AvoidInitiation">false</parameter>
>> >
>> > To check above behavior, we set "AvoidInitiation" property to "false"
>> in an AS server and found that management console is inaccessible. This is
>> similar to the issue we observed in MB.
>> >
>> > But the next problem is, when I set the AvoidInitiation to 'true', to
>> get rid of the UI issue, the Hazelcast instance is not exposed through the
>> OSGI service. ("com.hazelcast.core.HazelcastInstance" was not listed under
>> services in OSGI console)
>> >
>> > In that case, how can I access the Hazelcast instance exposed by Carbon?
>>
>> Can you try debug HazelcastClusteringAgent's init method by setting
>> AvoidInitiation to true? That is where the service gets registered.
>>
>> >
>> > Thanks and Regards,
>> > Sewwandi
>> >
>> >
>> >
>> > On Tue, Jul 29, 2014 at 11:38 AM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>> >>
>> >> Set AvoidInitiation to 'true' and start again.
>> >>
>> >> Also to make sure a server is started properly, you should see the
>> below logs.
>> >>
>> >> [2014-07-29 10:58:43,632] INFO
>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS port
>> : 9443
>> >> [2014-07-29 10:58:43,633] INFO
>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP port
>> : 9763
>> >>
>> >> [2014-07-29 10:58:44,060] INFO
>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server
>> : ${product.name}-${product.version}
>> >> [2014-07-29 10:58:44,061] INFO
>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
>> Carbon started in 18 sec
>> >>
>> >>
>> >> On Mon, Jul 28, 2014 at 11:31 AM, Sewwandi Perera <sewwa...@wso2.com>
>> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> We recently modified WSO2 MB to use Hazelcast for coordination
>> instead of Apache Zookeeper.
>> >>>
>> >>> In clustered mode, we use following configurations in axis2.xml to
>> enable Clustering;
>> >>>
>> >>> <clustering
>> class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
>> >>> enable="true">
>> >>> <parameter name="AvoidInitiation">false</parameter>
>> >>> <parameter name="membershipScheme">wka</parameter>
>> >>> <parameter name="localMemberHost">127.0.0.1</parameter>
>> >>> <parameter name="localMemberPort">4000</parameter>
>> >>> <members>
>> >>> <member>
>> >>> <hostName>127.0.0.1</hostName>
>> >>> <port>4001</port>
>> >>> </member>
>> >>> </members>
>> >>>
>> >>> In standalone mode, we can access MB management console without any
>> issue.
>> >>>
>> >>> But in clustered mode, even though below log appears, we cannot
>> access management console using browser.
>> >>> INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt
>> Console URL : https://10.100.5.67:9443/carbon/
>> >>>
>> >>> Additionally, we see error traces neither in server side nor in
>> browser.
>> >>>
>> >>> What can be the cause behind this issue?
>> >>>
>> >>> Thanks and Regards,
>> >>> Sewwandi
>> >>>
>> >>> --
>> >>> Sewwandi Perera
>> >>> Software Engineer
>> >>>
>> >>> WSO2 Inc.; http://wso2.com
>> >>> lean.enterprise.middleware
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Kishanthan Thangarajah
>> >> Senior Software Engineer,
>> >> Platform Technologies Team,
>> >> WSO2, Inc.
>> >> lean.enterprise.middleware
>> >>
>> >> Mobile - +94773426635
>> >> Blog - http://kishanthan.wordpress.com
>> >> Twitter - http://twitter.com/kishanthan
>> >
>> >
>> >
>> >
>> > --
>> > Sewwandi Perera
>> > Software Engineer
>> >
>> > WSO2 Inc.; http://wso2.com
>> > lean.enterprise.middleware
>>
>
>
>
> --
> Sewwandi Perera
> Software Engineer
>
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
--
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware
Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>*
Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
