Was this sorted out?
On Wed, Jul 30, 2014 at 8:35 PM, Kishanthan Thangarajah wrote:
>
>
> On Wed, Jul 30, 2014 at 12:33 PM, Sewwandi Perera
> wrote:
>
>> Hi Kishanthan,
>>
>> I debugged the code and found that HazelcastClusteringAgent's init method
>> is never hit when AvoidInitiation is set
On Wed, Jul 30, 2014 at 12:33 PM, Sewwandi Perera 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 th
Hi Kishanthan,
I debugged the code and found that HazelcastClusteringAgent's init method is
never hit when AvoidInitiation is set to true.
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
mo
-- Sent from mobile --
On 29 Jul 2014 14:50, "Sewwandi Perera" wrote:
>
> Hi,
>
> We observed that the UI issue has come as a result of below configuration
in axis2.xml.
> false
>
> To check above behavior, we set "AvoidInitiation" property to "false" in
an AS server and found that management cons
Hi,
We observed that the UI issue has come as a result of below configuration
in axis2.xml.
false
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
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.c
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;
false
wka
127.0.0.1
4000
127.0.0.1
4001
