date:20150912

Re: [Dev] Clarifications on CEP

2015-09-12 Thread Sriskandarajah Suhothayan

To add ML feature we need the p2 repo of ML,
@Nirmal do you have one ?

Suho

On Sat, Sep 12, 2015 at 10:24 PM, Sashika Wijesinghe 
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 
> 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 
>> 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 
>>> 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
>>
>> 
>> 
>> 
>> 
>> 192.168.48.128*
>> 8904
>> 
>> 
>> localhost
>> 11000
>> 
>> 
>>
>> 
>> 
>> 
>> 192.168.48.128
>> 8904
>> 
>> 
>> 192.168.48.128
>> 8905
>> 
>> 
>>
>>
>> [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.(TServerSocket.java:93)
>> at
>> org.apache.thrift.transport.TServerSocket.(TServerSocket.java:79)
>> at
>> org.wso2.carbon.event.processor.core.internal.storm.manager.StormManagerServer.(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 
>>> 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
>>
>>

Re: [Dev] Clarifications on CEP

2015-09-12 Thread Sashika Wijesinghe

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 
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 
> 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 
>> 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
>
> 
> 
> 
> 
> 192.168.48.128*
> 8904
> 
> 
> localhost
> 11000
> 
> 
>
> 
> 
> 
> 192.168.48.128
> 8904
> 
> 
> 192.168.48.128
> 8905
> 
> 
>
>
> [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.(TServerSocket.java:93)
> at
> org.apache.thrift.transport.TServerSocket.(TServerSocket.java:79)
> at
> org.wso2.carbon.event.processor.core.internal.storm.manager.StormManagerServer.(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 
>> 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,

Re: [Dev] [APIM] Timeout error when creating APIs using APIM 1.9.0 REST API

2015-09-12 Thread Nuwan Wimalasekara

Hi Udara,

Please refer below links[1] and [2]

[1]
https://github.com/nuwanw/product-apim/blob/master/modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/am/integration/test/utils/clients/APIPublisherRestClient.java

[2]
https://github.com/nuwanw/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/samples/YouTubeAPITestCase.java

Thanks,
Nuwnw

On Fri, Sep 11, 2015 at 10:39 PM, Udara Liyanage  wrote:

> Hi Nuwan,
>
> Could you please point me to the test case location, me too is looking for
> a similar sample.
>
> On Fri, Sep 11, 2015 at 3:39 PM, Nuwan Wimalasekara 
> wrote:
>
>> Hi Udara,
>>
>> In APIM integration test, HTTP endpoint is used to call the
>> RestAPI(Publisher and Store) and It is working fine without any issue. This
>> should work
>>
>> Thanks,
>> Nuwanw
>>
>> On Fri, Sep 11, 2015 at 9:41 AM, Nuwan Dias  wrote:
>>
>>> They run on HTTPS only. If you send an http request, it automatically
>>> redirects to https.
>>>
>>> On Fri, Sep 11, 2015 at 8:46 AM, Udara Liyanage  wrote:
>>>
 Hi,

 I could create APIs by changing to port 9443 and protocol to HTTPS.
 However why does REST APIs runs on HTTP?

 curl -X POST -c cookies
 https://localhost:9443/publisher/site/blocks/user/login/ajax/login.jag
 -d 'action=login=admin=admin' -k


 curl -b cookies -k
 https://localhost:9443/publisher/site/blocks/item-add/ajax/add.jag -d
 "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
 a phone
 number=phone,mobile,multimedia=nonsecured===Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
 x...@ee.com=xx=g...@ww.com"
 -d'endpoint_config={"production_endpoints":{"url":"
 http://ws.cdyne.com/phoneverify/phoneverify.asmx","config":null},"endpoint_type":"http
 "}';

 On Fri, Sep 11, 2015 at 4:18 AM, Udara Liyanage  wrote:

> Hi,
>
> I got this error while trying the sample Add API command mentioned in
> the doc . No
> backend error is displayed, any idea?
>
>
>  $ curl -X POST -c cookies
> http://localhost:9763/publisher/site/blocks/user/login/ajax/login.jag
> -d 'action=login=admin=admin'
> {"error" : false}
>
>
>  $ curl -X POST -b cookies
> http://localhost:9763/publisher/site/blocks/item-add/ajax/add.jag -d
> "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
> a phone
> number=phone,mobile,multimedia=nonsecured=Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
> x...@ee.com=xx=g...@ww.com"
> -d'endpoint_config={"production_endpoints":{"url":"
> http://ws.cdyne.com/phoneverify/phoneverify.asmx
> ","config":null},"endpoint_type":"http"}';
> {"error" : true, "message" : "*timeout*"}
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>



 --

 Udara Liyanage
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware

 web: http://udaraliyanage.wordpress.com
 phone: +94 71 443 6897

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>



-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Configuration issue in permission tree - MB

2015-09-12 Thread Johann Nallathamby

Hi Dilini,

There is a good chance of this being a bug in MB side, if they have not
used proper permissions for the services, service operations and/or UI
menus items. Or else they could be using contradicting permissions for any
of the above. Have you confirmed with MB team that they have used
permissions properly?

I would suggest that you clear it from MB side first, and confirm that this
is indeed an issue in permission management component, and then we can take
a look at the issue, because AFAIK we don't have such issues in IS. For now
I will move the issue to MB project [1], if MB team can confirm as this is
happening due to a bug in permission management, then you can move it back
to IDENTITY.

[1] https://wso2.org/jira/browse/MB-1270

Regards.

On Fri, Sep 11, 2015 at 3:25 PM, Dilini Gunatilake  wrote:

> Hi All,
>
> This is regarding a known issue of the permission tree. When you try to
> configure permissions of a Role in Management Console, we can either select
> the parent and enable all the permissions under the parent or deselect the
> parent and enable only few permissions under the parent. In this case, even
> it is possible to select only few permissions in the UI, it does not
> apply.
>
> For example, in Message Broker (MB), there are permissions under Queues to
> Add, Browse, Delete and Purge queues. If I want to allow a user only to Add
> and Browse queues, I will have to deselect Queue parent element and select
> only Add and Browse child elements. After applying this, the user will not
> be able to access the entire Queue section, not only Purge and Delete
> functions.
>
> I have also raised an issue in JIRA [1]. Can you please explain how to
> achieve the above mentioned scenario in MB?
>
> [1] https://wso2.org/jira/browse/IDENTITY-3573
>
> Thank you.
>
> Regards,
>
> --
>
> *Dilini GunatilakeSoftware Engineer - QA Team*
> Mobile : +94 (0) 771 162518
> dili...@wso2.com
>

-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Integration Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Jaggery] Error in using WSReqwest.

2015-09-12 Thread Manuranga Perera

please try installing ws feature

On Thu, Sep 10, 2015 at 10:34 AM, Sachith Punchihewa 
wrote:

> Hi Manuranga,
>
> As per the discussion we had yesterday i installed the following jaggry
> features to the product.But the error was their as before.
>
>
>- org.jaggeryjs.feature
>- org.jaggeryjs.modules.carbon.feature
>- org.jaggeryjs.modules.process.feature
>- org.jaggeryjs.modules.uuid.feature
>- org.jaggeryjs.modules.sso.feature
>- org.jaggeryjs.modules.i18n.feature
>- org.jaggeryjs.modules.jaggery-test.feature
>
>
> Then i copy pasted the ws folder to the carbon home as you mention above
> then i get the following error.
> Is there is another feature that i need to install?
>
>
> *Error :*
>>
>> [2015-09-10 10:04:52,677] ERROR
>> {org.jaggeryjs.jaggery.core.manager.ModuleManager} -  Error while adding
>> HostObject : WSRequest org.jaggeryjs.hostobjects.ws.WSRequestHostObject
>> cannot be found by org.jaggeryjs.jaggery.core_0.10.1
>> java.lang.ClassNotFoundException:
>> org.jaggeryjs.hostobjects.ws.WSRequestHostObject cannot be found by
>> org.jaggeryjs.jaggery.core_0.10.1
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>> at java.lang.Class.forName0(Native Method)
>> at java.lang.Class.forName(Class.java:195)
>> at
>> org.jaggeryjs.jaggery.core.manager.ModuleManager.initHostObjects(ModuleManager.java:279)
>> at
>> org.jaggeryjs.jaggery.core.manager.ModuleManager.initModule(ModuleManager.java:141)
>> at
>> org.jaggeryjs.jaggery.core.manager.ModuleManager.loadModule(ModuleManager.java:95)
>> at
>> org.jaggeryjs.jaggery.core.manager.ModuleManager.init(ModuleManager.java:84)
>> at
>> org.jaggeryjs.jaggery.core.manager.ModuleManager.(ModuleManager.java:64)
>> at
>> org.jaggeryjs.jaggery.core.manager.CommonManager.initialize(CommonManager.java:69)
>> at
>> org.jaggeryjs.jaggery.core.manager.WebAppManager.(WebAppManager.java:92)
>> at
>> org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer$JaggeryConfListener.lifecycleEvent(TomcatJaggeryWebappsDeployer.java:290)
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
>> at
>> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>> at
>> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
>> at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:347)
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5591)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
>> at
>> org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:345)
>> at
>> org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:267)
>> at
>> org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer.handleWebappDeployment(TomcatJaggeryWebappsDeployer.java:212)
>> at
>> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleExplodedWebappDeployment(TomcatGenericWebappsDeployer.java:246)
>> at
>> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleHotDeployment(TomcatGenericWebappsDeployer.java:172)
>> at
>> org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer.deploy(TomcatJaggeryWebappsDeployer.java:115)
>> at
>> org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deployThisWebApp(AbstractWebappDeployer.java:204)
>> at
>> org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deploy(AbstractWebappDeployer.java:111)
>> at
>> org.jaggeryjs.jaggery.deployer.JaggeryDeployer.deploy(JaggeryDeployer.java:59)
>> at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
>> at
>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>> at
>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>> at
>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:135)
>> at
>> org.wso2.carbon.core.CarbonAxisConfigurator.deployServices(CarbonAxisConfigurator.java:567)
>> at
>> org.wso2.carbon.core.internal.DeploymentServerStartupObserver.completingServerStartup(DeploymentServerStartupObserver.java:51)
>> at
>>

Re: [Dev] Clarifications on CEP

Re: [Dev] Clarifications on CEP

Re: [Dev] [APIM] Timeout error when creating APIs using APIM 1.9.0 REST API

Re: [Dev] Configuration issue in permission tree - MB

Re: [Dev] [Jaggery] Error in using WSReqwest.

5 matches

Site Navigation

Mail list logo

Footer information