Hi Sashika,
Yes that is the usual behaviour for WSO2 servers when started with worker
node true. The login page will be visible, but you won't be allowed to
login.
Thanks,
On 9 September 2015 at 11:16, Sashika Wijesinghe <sash...@wso2.com> wrote:
> Hi Suho/Lasantha,
>
> I'm working on CEP distributed mode set up. When a worker node is started
> using "-DworkerNode=true" argument, I expected that UI of the worker node
> should not be visible. However CEP login page is visible when started with
> -DworkerNode=true argument, but can't access to CEP, because login
> functionality is not functioning.
>
> Appreciate your clarification on above situation.
>
> Thank You
>
> On Wed, Sep 9, 2015 at 11:00 AM, Sriskandarajah Suhothayan <s...@wso2.com>
> wrote:
>
>> Can you look into this
>>
>> Suho
>>
>> On Wed, Sep 9, 2015 at 10:59 AM, Shavantha Weerasinghe <
>> shavan...@wso2.com> wrote:
>>
>>> Hi Suho/Lasantha
>>>
>>> We observed the bellow exception when we set the hostName as
>>> *192.168.48.128* but the exception does not come if we set localhost.
>>> This is on the node that behaves as both manager and worker on
>>> *192.168.48.128.
>>> *Do we need to set the /etc/hosts if we are to use the IP
>>>
>>> <mode name="Distributed" enable="true">
>>> <nodeType>
>>> <worker enable="true"/>
>>> <manager enable="false">
>>> <hostName*>192.168.48.128*</hostName>
>>> <port>8904</port>
>>> </manager>
>>> <presenter enable="true">
>>> <hostName>localhost</hostName>
>>> <port>11000</port>
>>> </presenter>
>>> </nodeType>
>>>
>>> <management>
>>> <managers>
>>> <manager>
>>> <hostName>192.168.48.128</hostName>
>>> <port>8904</port>
>>> </manager>
>>> <manager>
>>> <hostName>192.168.48.128</hostName>
>>> <port>8905</port>
>>> </manager>
>>> </managers>
>>>
>>>
>>> [2015-09-09 05:14:57,550] ERROR
>>> {org.wso2.carbon.event.processor.core.internal.storm.manager.StormManagerServer}
>>> - Cannot start Storm Manager Server on 192.168.48.128:8905
>>> org.apache.thrift.transport.TTransportException: Could not create
>>> ServerSocket on address /192.168.48.128:8905.
>>> at
>>> org.apache.thrift.transport.TServerSocket.<init>(TServerSocket.java:93)
>>> at
>>> org.apache.thrift.transport.TServerSocket.<init>(TServerSocket.java:79)
>>> at
>>> org.wso2.carbon.event.processor.core.internal.storm.manager.StormManagerServer.<init>(StormManagerServer.java:41)
>>> at
>>> org.wso2.carbon.event.processor.core.internal.ds.EventProcessorServiceDS.activate(EventProcessorServiceDS.java:87)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>>
>>> Shavantha Weerasinghe
>>> Senior Software Engineer QA
>>> WSO2, Inc.
>>> lean.enterprise.middleware.
>>> http://wso2.com
>>> http://wso2.org
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>>
>>>
>>> On Tue, Sep 8, 2015 at 10:16 AM, Sriskandarajah Suhothayan <
>>> s...@wso2.com> wrote:
>>>
>>>> We are not supporting this for this release, we might support his in
>>>> future using SSO, but not for this release.
>>>>
>>>> Suho
>>>>
>>>> On Tue, Sep 8, 2015 at 9:45 AM, Tharik Kanaka <tha...@wso2.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> As Mohan mentioned gaining login session of management console is not
>>>>> possible with current implementation of analytics dashboards.
>>>>>
>>>>> Regards,
>>>>>
>>>>> On Tue, Sep 8, 2015 at 9:28 AM, Mohanadarshan Vivekanandalingam <
>>>>> mo...@wso2.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Sep 7, 2015 at 10:50 PM, Shavantha Weerasinghe <
>>>>>> shavan...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi All
>>>>>>>
>>>>>>> Appreciate if I can get a clarification on the two below points.
>>>>>>>
>>>>>>> 1.Is there a way we can configure for the cep admin to gain access
>>>>>>> to the analytic dashboard without entering the login again if he has
>>>>>>> logged
>>>>>>> into the management console.
>>>>>>>
>>>>>>
>>>>>> Hmm, I don't think this is possible as per current implementation..
>>>>>> @Damith or Tharik, please confirm..
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> 2. When we are accepting events from multiple sources (ex:
>>>>>>> soap/http) into a single stream there may be a need to stop receiving
>>>>>>> events into a specific events receiver. Is there away we can disable an
>>>>>>> event receiver without deleting it. The same could apply to event
>>>>>>> publishers as well
>>>>>>>
>>>>>>> No, it is not possible in CEP 4.0.0 but it is in the roadmap. We
>>>>>> already have jira [1] which is reported by you :)
>>>>>>
>>>>>> [1] https://wso2.org/jira/browse/CEP-506
>>>>>>
>>>>>> Thanks,
>>>>>> Mohan
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Shavantha Weerasinghe
>>>>>>> Senior Software Engineer QA
>>>>>>> WSO2, Inc.
>>>>>>> lean.enterprise.middleware.
>>>>>>> http://wso2.com
>>>>>>> http://wso2.org
>>>>>>> Tel : 94 11 214 5345
>>>>>>> Fax :94 11 2145300
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *V. Mohanadarshan*
>>>>>> *Senior Software Engineer,*
>>>>>> *Data Technologies Team,*
>>>>>> *WSO2, Inc. http://wso2.com <http://wso2.com> *
>>>>>> *lean.enterprise.middleware.*
>>>>>>
>>>>>> email: mo...@wso2.com
>>>>>> phone:(+94) 771117673
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> *Tharik Kanaka*
>>>>>
>>>>> WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka
>>>>>
>>>>> Email: tha...@wso2.com | Web: www.wso2.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *S. Suhothayan*
>>>> Technical Lead & Team Lead of WSO2 Complex Event Processor
>>>> *WSO2 Inc. *http://wso2.com
>>>> * <http://wso2.com/>*
>>>> lean . enterprise . middleware
>>>>
>>>>
>>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
>>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter:
>>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
>>>> http://lk.linkedin.com/in/suhothayan
>>>> <http://lk.linkedin.com/in/suhothayan>*
>>>>
>>>
>>>
>>
>>
>> --
>>
>> *S. Suhothayan*
>> Technical Lead & Team Lead of WSO2 Complex Event Processor
>> *WSO2 Inc. *http://wso2.com
>> * <http://wso2.com/>*
>> lean . enterprise . middleware
>>
>>
>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter:
>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
*Lasantha Fernando*
Senior Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com
email: lasan...@wso2.com
mobile: (+94) 71 5247551
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
