Hi Malaka/Rajith,

I followed as you suggested.

When I specify taskServerCount as 2, I couldn’t access the management
console. But when I specify taskServerCount as 1, I’m able to access the
management console. But still I got the same error [2].

[2] -
    at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1085)
    at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5318)
    at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5610)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
    at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
    at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)
[2016-09-26 10:52:11,284]  INFO - ClusterGroupCommunicator Waiting for 1
[registryTasks] task executor nodes...
[2016-09-26 10:52:11,284]  INFO - ClusterGroupCommunicator All task servers
activated for [registryTasks].
[2016-09-26 10:52:11,309]  INFO - JMXServerManager JMX Service URL  :
service:jmx:rmi://localhost:11112/jndi/rmi://localhost:10000/jmxrmi
[2016-09-26 10:52:11,313]  INFO - StartupFinalizerServiceComponent
Server           :  WSO2 Enterprise Service Bus-5.0.0
[2016-09-26 10:52:11,314]  INFO - StartupFinalizerServiceComponent WSO2
Carbon started in 21 sec
[2016-09-26 10:52:11,508]  INFO - CarbonUIServiceComponent Mgt Console URL
: https://mgt.esb.wso2.com:443/carbon/

Thanks,

Biruntha

Associate Software Engineer
WSO2
Email : [email protected]
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Mon, Sep 26, 2016 at 10:33 AM, Rajith Vitharana <[email protected]> wrote:

> Hi,
>
> That error comes when you start a *non* task node(in this case manager
> node) without starting a task node(worker node). (task node count specified
> in tasks-config.xml). So if you follow below steps, this shouldn't happen.
>
> 1) specify task server count(<taskServerCount>1</taskServerCount>) as 1
> in task-config.xml
> 2) start worker and then manager. (if worker correctly connects to the
> manger through cluster, this error message shouldn't come)
>
> Thanks,
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to