Thanks Sashika, I think this is due to recent version upgrades.

@Mano could you please check?

On Mon, Sep 14, 2015 at 11:30 AM, Sashika Wijesinghe <[email protected]>
wrote:

> Hi Nirmal,
>
> I tried to install 'Machine learner core' feature in a fresh CEP pack
> (13th September Jenkins pack) , but couldn't continue installation due to
> below issue.
>
> Cannot complete the install because of a conflicting dependency. Software
> being installed: WSO2 Carbon - Machine Learner Core Feature 1.0.1.SNAPSHOT
> (org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT) Software currently
> installed: WSO2 Carbon - Event Publisher Feature 5.0.1
> (org.wso2.carbon.event.publisher.feature.group 5.0.1) Only one of the
> following can be installed at once: WSO2 Carbon - Event Output Email
> Adapter Server Feature 5.0.1
> (org.wso2.carbon.event.output.adapter.email.server.feature.jar 5.0.1) WSO2
> Carbon - Event Output Email Adapter Server Feature 5.0.2.SNAPSHOT
> (org.wso2.carbon.event.output.adapter.email.server.feature.jar
> 5.0.2.SNAPSHOT) Cannot satisfy dependency: From: WSO2 Carbon - Event Output
> Email Adapter Server Feature 5.0.1
> (org.wso2.carbon.event.output.adapter.email.server.feature.group 5.0.1) To:
> org.wso2.carbon.event.output.adapter.email.server.feature.jar [5.0.1]
> Cannot satisfy dependency: From: WSO2 Carbon - Event Output Email Adapter
> Server Feature 5.0.2.SNAPSHOT
> (org.wso2.carbon.event.output.adapter.email.server.feature.group
> 5.0.2.SNAPSHOT) To:
> org.wso2.carbon.event.output.adapter.email.server.feature.jar
> [5.0.2.SNAPSHOT] Cannot satisfy dependency: From: WSO2 Carbon - Event
> Publisher Output Adapter Feature 5.0.1
> (org.wso2.carbon.event.output.adapter.feature.group 5.0.1) To:
> org.wso2.carbon.event.output.adapter.email.server.feature.group [5.0.1]
> Cannot satisfy dependency: From: WSO2 Carbon - Event Publisher Feature
> 5.0.1 (org.wso2.carbon.event.publisher.feature.group 5.0.1) To:
> org.wso2.carbon.event.output.adapter.feature.group [5.0.1] Cannot satisfy
> dependency: From: WSO2 Carbon - Machine Learner Core Feature 1.0.1.SNAPSHOT
> (org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT) To:
> org.wso2.carbon.event.output.adapter.email.server.feature.group
> [5.0.2.SNAPSHOT,5.1.0)
>
> Appreciate your help on this matter.
>
> Thanks.
>
> On Mon, Sep 14, 2015 at 10:02 AM, Nirmal Fernando <[email protected]> wrote:
>
>> Shared the ML p2-repo with Sashika.
>>
>> On Sun, Sep 13, 2015 at 10:40 PM, Shavantha Weerasinghe <
>> [email protected]> wrote:
>>
>>> Hi Sashika
>>>
>>> I got the p2 from lasantha last week will share tomorrow
>>> On Sep 12, 2015 10:24 PM, "Sashika Wijesinghe" <[email protected]> wrote:
>>>
>>>> Hi All,
>>>>
>>>> May I know the location to download P2 repository to add ML features
>>>> for CEP?
>>>>
>>>> Thanks
>>>>
>>>> On Wed, Sep 9, 2015 at 12:02 PM, Sashika Wijesinghe <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi Lasantha,
>>>>>
>>>>> Thanks for the clarification.
>>>>>
>>>>> In the documentation it has mentioned that '-DworkerNode=true"
>>>>> argument will deactivate the UI bundle, So I thought there should not be
>>>>> any UI component when a user tried to access to the worker node.
>>>>> And I felt its good if we are not enabling the login page. because
>>>>> when I tried to login to the CEP using worker node I got '*login
>>>>> failed*' error message.
>>>>>
>>>>> Thanks & Regards,
>>>>>
>>>>> On Wed, Sep 9, 2015 at 11:21 AM, Lasantha Fernando <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> 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 <[email protected]>
>>>>>> 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 <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> Can you look into this
>>>>>>>>
>>>>>>>> Suho
>>>>>>>>
>>>>>>>> On Wed, Sep 9, 2015 at 10:59 AM, Shavantha Weerasinghe <
>>>>>>>> [email protected]> 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 <
>>>>>>>>> [email protected]> 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 <[email protected]>
>>>>>>>>>> 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
>>>>>>>>>>> <[email protected]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Sep 7, 2015 at 10:50 PM, Shavantha Weerasinghe <
>>>>>>>>>>>> [email protected]> 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
>>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>> 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: [email protected]
>>>>>>>>>>>> phone:(+94) 771117673
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>> *Tharik Kanaka*
>>>>>>>>>>>
>>>>>>>>>>> WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka
>>>>>>>>>>>
>>>>>>>>>>> Email: [email protected] | 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
>>>>>>>> [email protected]
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> *Sashika WijesingheSoftware Engineer - QA Team*
>>>>>>> Mobile : +94 (0) 774537487
>>>>>>> [email protected]
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Dev mailing list
>>>>>>> [email protected]
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Lasantha Fernando*
>>>>>> Senior Software Engineer - Data Technologies Team
>>>>>> WSO2 Inc. http://wso2.com
>>>>>>
>>>>>> email: [email protected]
>>>>>> mobile: (+94) 71 5247551
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> *Sashika WijesingheSoftware Engineer - QA Team*
>>>>> Mobile : +94 (0) 774537487
>>>>> [email protected]
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Sashika WijesingheSoftware Engineer - QA Team*
>>>> Mobile : +94 (0) 774537487
>>>> [email protected]
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> [email protected]
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> [email protected]
>



-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to