Did not do any task server config change..Attched the config

On 13 March 2014 11:03, Isuru Perera <[email protected]> wrote:

> The nodes are waiting to communicate with other nodes.
>
> See:
> [2014-03-12 21:43:01,932]  INFO
> {org.wso2.carbon.ntask.core.impl.clustered.ClusterGroupCommunicator} -
>  Waiting for 2 task executor nodes...
>
> Make sure each node is in the same cluster domain.
>
>
> On Thu, Mar 13, 2014 at 10:53 AM, Vijayaratha Vijayasingam <
> [email protected]> wrote:
>
>>
>> Hi all;
>> I'm trying to do 3 node setup as mentioned in the guide[1]
>>
>> I stared the seed node first and it started successfully.
>> But other 2 nodes are not started fully.That is, i can not access the
>> management console. There is no any warning or errors in other two nodes.
>> The logs are;[2,3]
>> What i'm doing wrong here?
>>
>> *member node 2*
>>
>> [2014-03-12 21:39:47,228]  INFO
>> {org.apache.cassandra.streaming.StreamInSession} -  Finished streaming
>> session 1 from /10.21.9.12
>> [2014-03-12 21:39:47,275]  INFO
>> {org.apache.cassandra.thrift.CassandraDaemon} -  Binding thrift service to /
>> 10.21.9.13:9160
>> [2014-03-12 21:39:47,276]  INFO
>> {org.apache.cassandra.thrift.CassandraDaemon} -  Using TFastFramedTransport
>> with a max frame size of 15728640 bytes.
>> [2014-03-12 21:39:47,277]  INFO
>> {org.apache.cassandra.thrift.CassandraDaemon} -  Using
>> synchronous/threadpool thrift server on /10.21.9.13 : 9160
>> [2014-03-12 21:39:47,277]  INFO
>> {org.wso2.carbon.cassandra.server.CassandraServerController} -  Cassandra
>> Server Controller Thread was destroyed succe
>> ssfully
>> [2014-03-12 21:39:47,277]  INFO
>> {org.apache.cassandra.thrift.CassandraDaemon} -  Listening for thrift
>> clients...
>> [2014-03-12 21:40:29,514]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>  Hazelcast initialized in 60408ms
>> [2014-03-12 21:40:29,533]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>  Local member: [dd1a4696-883c-4a4b-a32d-77fb447
>> 2e85c] - Host:127.0.0.1, Remote Host:null, Port: 4000, HTTP:9763,
>> HTTPS:9443, Domain: wso2.carbon.domain, Sub-domain:worker, Active:true
>> [2014-03-12 21:40:29,778]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>  Cluster initialization completed
>> [2014-03-12 21:40:29,873]  INFO
>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} -  Task service
>> starting in CLUSTERED mode...
>> [2014-03-12 21:40:32,921]  INFO
>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -  Task
>> scheduled: [-1234][BAM_NOTIFICATION_DISPATCHER_TAS
>> K][NOTIFIER]
>> [2014-03-12 21:40:32,926]  INFO
>> {org.wso2.carbon.ntask.core.impl.clustered.ClusterGroupCommunicator} -
>>  Waiting for 2 task executor nodes...
>> [2014-03-12 21:41:51,384]  INFO {org.apache.cassandra.gms.Gossiper} -
>>  Node /10.21.9.14 is now part of the cluster
>> [2014-03-12 21:41:51,385]  INFO {org.apache.cassandra.gms.Gossiper} -
>>  InetAddress /10.21.9.14 is now UP
>> [2014-03-12 21:42:22,450]  INFO
>> {org.apache.cassandra.streaming.StreamOut} -  Beginning transfer to /
>> 10.21.9.14
>> [2014-03-12 21:42:22,451]  INFO
>> {org.apache.cassandra.streaming.StreamOut} -  Flushing memtables for
>> [CFS(Keyspace='BAM_UTIL_KS', ColumnFamily='bam_no
>> tification_messages')]...
>> [2014-03-12 21:42:22,451]  INFO
>> {org.apache.cassandra.streaming.StreamOut} -  Stream context metadata [], 0
>> sstables.
>> [2014-03-12 21:42:22,451]  INFO
>> {org.apache.cassandra.streaming.StreamOutSession} -  Streaming to /
>> 10.21.9.14
>> [2014-03-12 21:42:22,460]  INFO
>> {org.apache.cassandra.streaming.FileStreamTask} -  Finished streaming
>> session to /10.21.9.14
>>
>> [1]
>> https://docs.wso2.org/display/CLUSTER420/Clustering+Business+Activity+Monitor
>>
>> *node 3*
>>
>> *[*2014-03-12 21:41:56,859]  INFO
>> {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
>>  Permission cache updated for tenant -1234
>> [2014-03-12 21:41:56,883]  INFO
>> {org.wso2.carbon.bam.toolbox.deployer.internal.DashboardServiceComponent} -
>>  Successfully setted dashboard services
>> [2014-03-12 21:41:57,159]  INFO
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>  Thrift Server started at 10.21.9.14
>> [2014-03-12 21:41:57,167]  INFO
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>  Thrift SSL port : 7711
>> [2014-03-12 21:41:57,169]  INFO
>> {org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiver} -
>>  Thrift port : 7611
>> [2014-03-12 21:41:57,999]  INFO
>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -  HTTPS port
>>       : 9443
>> [2014-03-12 21:41:57,999]  INFO
>> {org.wso2.carbon.core.transports.http.HttpTransportListener} -  HTTP port
>>      : 9763
>> [2014-03-12 21:41:58,012]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>  Cluster domain: wso2.carbon.domain
>> [2014-03-12 21:41:58,012]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>  Using multicast based membership management sc
>> heme
>> [2014-03-12 21:42:16,278]  INFO
>> {org.apache.cassandra.streaming.StreamInSession} -  Finished streaming
>> session 1 from /10.21.9.13
>> [2014-03-12 21:42:16,338]  INFO
>> {org.apache.cassandra.thrift.CassandraDaemon} -  Binding thrift service to /
>> 10.21.9.14:9160
>> [2014-03-12 21:42:16,339]  INFO
>> {org.apache.cassandra.thrift.CassandraDaemon} -  Using TFastFramedTransport
>> with a max frame size of 15728640 bytes.
>> [2014-03-12 21:42:16,340]  INFO
>> {org.apache.cassandra.thrift.CassandraDaemon} -  Using
>> synchronous/threadpool thrift server on /10.21.9.14 : 9160
>> [2014-03-12 21:42:16,340]  INFO
>> {org.wso2.carbon.cassandra.server.CassandraServerController} -  Cassandra
>> Server Controller Thread was destroyed succe
>> ssfully
>> [2014-03-12 21:42:16,340]  INFO
>> {org.apache.cassandra.thrift.CassandraDaemon} -  Listening for thrift
>> clients...
>> [2014-03-12 21:42:58,441]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>  Hazelcast initialized in 60423ms
>> [2014-03-12 21:42:58,460]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>  Local member: [956a14f4-4e3d-4054-8458-bf8f6fd
>> def59] - Host:127.0.0.1, Remote Host:null, Port: 4000, HTTP:9763,
>> HTTPS:9443, Domain: wso2.carbon.domain, Sub-domain:worker, Active:true
>> [2014-03-12 21:42:58,701]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>  Cluster initialization completed
>> [2014-03-12 21:42:58,795]  INFO
>> {org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl} -  Task service
>> starting in CLUSTERED mode...
>> [2014-03-12 21:43:01,927]  INFO
>> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -  Task
>> scheduled: [-1234][BAM_NOTIFICATION_DISPATCHER_TAS
>> K][NOTIFIER]
>> [2014-03-12 21:43:01,932]  INFO
>> {org.wso2.carbon.ntask.core.impl.clustered.ClusterGroupCommunicator} -
>>  Waiting for 2 task executor nodes...
>> --
>> -Ratha
>> mobile: (+94)755906608
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>



-- 
-Ratha
mobile: (+94)755906608
<tasks-configuration xmlns:svns="http://org.wso2.securevault/configuration";>

    <!-- 
      The currently running server mode; possible values are:-
      STANDALONE, CLUSTERED, REMOTE, AUTO.
      In AUTO mode, the server startup checks whether clustering is enabled in the system, 
      if so, CLUSTERED mode will be used, or else, the the server mode will be STANDALONE.
    -->
    <taskServerMode>AUTO</taskServerMode>
    
    <!-- 
      To be used in CLUSTERED mode to notify how many servers are there in 
      the task server cluster, the servers wait till this amount of servers
      are activated before the tasks are scheduled -->
    <taskServerCount>2</taskServerCount>
    
    <!-- The address to which the remote task server should dispatch the trigger messages to, 
      usually this would be an endpoint to a load balancer -->
    <taskClientDispatchAddress>https://localhost:9448</taskClientDispatchAddress>
    
    <!-- The address of the remote task server -->
    <remoteServerAddress>https://localhost:9443</remoteServerAddress>
    
    <!-- The username to authenticate to the remote task server -->
    <remoteServerUsername>admin</remoteServerUsername>
    
    <!-- The password to authenticate to the remote task server -->
    <remoteServerPassword>admin</remoteServerPassword>

    <!-- Below contain a sample to be used when using with secure vault -->
    <!--remoteServerPassword svns:secretAlias="remote.task.server.password"></remoteServerPassword-->

</tasks-configuration>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to