date:20160527

Re: [Dev] ESB 5 Beta - Shared subscriber doesn't connect

2016-05-27 Thread Ravindra Ranwala

Hi Manuranga,

The shared subscription feature works fine and we used to test it with HornetQ
broker. This could be due to some missing configuration. Could you please
follow the blog post [1], and check the correctness in your configuration.


[1] http://ravindraranwala.blogspot.com/


Thanks & Regards,

On Fri, May 27, 2016 at 8:51 PM, Manuranga Perera  wrote:

> I am trying to connect to IBM MQ using JMS 2
>
> http://ws.apache.org/ns/synapse"; name="TReaderPxy2"
> startOnLoad="true">
>
>   
>  
>  
>  
>   
>
>topic
>mySub
>TestQ49
>true
>1
> name="transport.jms.ConnectionFactory">myTopicParams
>2.0
>true
> 
>
> First ESB instance can connect successfully and I can publish messages.
> But when I start another identical instance I see following error.
> It connects if subscriber names are distinct, but then messages are
> cloned, not shared.
>
> Please help me identify the issue.
>
> TID: [-1234] [] [2016-05-27 11:11:07,719]  INFO
> {org.apache.axis2.transport.jms.JMSListener} -  JMS listener started
> {org.apache.axis2.transport.jms.JMSListener}
> TID: [-1234] [] [2016-05-27 11:11:07,720] DEBUG
> {org.apache.axis2.transport.jms.JMSEndpoint} -  JMS reply destination type
> not given. default queue {org.apache.axis2.transport.jms.JMSEndpoint}
> TID: [-1234] [] [2016-05-27 11:11:07,738] DEBUG
> {org.apache.axis2.transport.jms.JMSUtils} -  Creating a GenericConnection
> using credentials : (null/null) {org.apache.axis2.transport.jms.JMSUtils}
> TID: [-1234] [] [2016-05-27 11:11:08,011]  INFO
> {org.apache.axis2.transport.jms.JMSListener} -  Connection attempt: 1 for
> JMS Provider for service: TReaderPxy2 was successful!
> {org.apache.axis2.transport.jms.JMSListener}
> TID: [-1234] [] [2016-05-27 11:11:08,011] DEBUG
> {org.apache.axis2.transport.jms.ServiceTaskManager} -  The JMS Connection,
> Session and MessageConsumer will be cached and shared between successive
> poller task invocations {org.apache.axis2.transport.jms.ServiceTaskManager}
> TID: [-1234] [] [2016-05-27 11:11:08,017]  INFO
> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Task manager for
> service : TReaderPxy2 [re-]initialized
> {org.apache.axis2.transport.jms.ServiceTaskManager}
> TID: [-1] [] [2016-05-27 11:11:08,020] DEBUG
> {org.apache.axis2.transport.jms.ServiceTaskManager} -  New poll task
> starting : thread id = 82
> {org.apache.axis2.transport.jms.ServiceTaskManager}
> TID: [-1] [] [2016-05-27 11:11:08,026] DEBUG
> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Connected to the JMS
> connection factory : USAPP2D.TCF
> {org.apache.axis2.transport.jms.ServiceTaskManager}
> TID: [-1] [] [2016-05-27 11:11:08,027] DEBUG
> {org.apache.axis2.transport.jms.JMSUtils} -  Creating a TopicConnection
> using credentials : (null/null) {org.apache.axis2.transport.jms.JMSUtils}
> TID: [-1] [] [2016-05-27 11:11:08,055] DEBUG
> {org.apache.axis2.transport.jms.ServiceTaskManager} -  JMS Connection for
> service : TReaderPxy2 created and started
> {org.apache.axis2.transport.jms.ServiceTaskManager}
> TID: [-1] [] [2016-05-27 11:11:08,056] DEBUG
> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Creating a new JMS
> Session for service : TReaderPxy2
> {org.apache.axis2.transport.jms.ServiceTaskManager}
> TID: [-1] [] [2016-05-27 11:11:08,113] DEBUG
> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Creating a new JMS
> MessageConsumer for service : TReaderPxy2
> {org.apache.axis2.transport.jms.ServiceTaskManager}
> TID: [-1] [] [2016-05-27 11:11:08,143] DEBUG
> {org.apache.axis2.transport.jms.ServiceTaskManager} -  JMS Destination with
> JNDI name : TestQ49 found for service TReaderPxy2
> {org.apache.axis2.transport.jms.ServiceTaskManager}
> TID: [-1] [] [2016-05-27 11:11:08,198] ERROR
> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Error creating JMS
> consumer for service : TReaderPxy2. JMSWMQ0026: Failed to subscribe to
> topic 'TestQ49' with selector 'none' using MQSUB.
> {org.apache.axis2.transport.jms.ServiceTaskManager}
> com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ0026: Failed
> to subscribe to topic 'TestQ49' with selector 'none' using MQSUB.
> There may have been a problem creating the subscription due to it being
> used by another message consumer.
> Make sure any message consumers using this subscription are closed before
> trying to create a new subscription under the same name. Please see the
> linked exception for more information.
> at
> com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:472)
> at
> com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:214)
> at
> com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:212)
> at
> com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:112)
> at
> com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialize(WMQConsumerShadow.java:1038)
> a

Re: [Dev] [GSOC 16] Initial Project Progress

2016-05-27 Thread Imesh Gunaratne

On Sat, May 28, 2016 at 12:42 AM, Osura Rathnayake 
wrote:

> Hi mentors,
>
> Sorry for the late reply. ARM portal doesn't have certain features like
> Active Directory but it doesn't matter because they can be implemented
> using classic portal and they work hand in hand. So all the features in
> classic plus the new features in ARM can be used if we choose ARM model.
> Therefore I think it's fruitful if we stick to ARM model, and the other
> important thing is sooner or later Microsoft will develop the ARM fully so
> eventually classic model will be obsolete(I think).
>

+1 We may need to go ahead with what they provide at the moment.

>
> As we discussed in our last hangout, using a main program I could list out
> the IP addresses of the VMs where Application Servers are installed. Please
> arrange another hangout so that we can discuss the next project goal.
>
> Yes will have a hangout next week, it would be better if you can send
details in a mail first.

Thanks

>
>
>
> On Wed, May 25, 2016 at 9:08 PM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh,
>>
>> okay i will find out the differences and update you. meanwhile i will
>> check azure sdk for java if it has all the classes we want.
>>
>> On Wed, May 25, 2016 at 9:31 AM, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Tue, May 24, 2016 at 10:22 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi mentors,

 As you might already know, Azure has two deployment models , azure
 classic (old portal) and azure resource manager (ARM)(new portal).
 Unfortunately some functionalities of classic is not available in ARM vice
 versa[1] but microsoft is rapidly developing all the functionalities across
 both models. Also certain API references [2] are not available for both the
 models, for an example, for network both classic and ARM API references are
 available but for network security groups only classic is available, while
 network security groups is a supported feature in ARM. shall we have a
 hangout to discuss this matter?

>>>
>>> IMO it would be okay to stick to one model. Can you please research on
>>> this and list out the differences between two models? That would help us to
>>> take a decision on this.
>>>
>>> Thanks
>>>

 [1]
 https://blog.kloud.com.au/2016/04/05/azure-classic-vs-azure-resource-manager/

 [2] https://msdn.microsoft.com/en-us/library/azure/mt420159.aspx



 On Fri, May 20, 2016 at 11:05 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Are you joining the hangout now?
>
> On Thu, May 19, 2016 at 7:37 PM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> It's no problem. Okay let's have a hangout at 11 o'clock tomorrow.
>>
>> On Thursday, May 19, 2016, Isuru Haththotuwa  wrote:
>>
>>> Hi Osura,
>>>
>>> Sorry for the delayed response.
>>>
>>> Shall we have a hangout at 11 AM on 20th May (Friday)?
>>>
>>> On Tue, May 17, 2016 at 9:09 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Imesh,

 Shall we have a hangout on Thursday or so?


 On Thu, May 12, 2016 at 8:26 PM, Imesh Gunaratne 
 wrote:

> Hi Osura,
>
> On Thu, May 12, 2016 at 8:09 PM, Osura Rathnayake <
> osura...@gmail.com> wrote:
>
>> Hi Mentors,
>>
>> I created a github repository so that all the work related to
>> this project can be accumulated with ease.
>> here is the link
>> https://github.com/osuran/azure-membership-scheme.
>>
>
> Great! Will you be able to arrange a Hangout and demonstrate what
> you did so far?
>
> Thanks
>
> On Thu, May 12, 2016 at 8:09 PM, Osura Rathnayake <
> osura...@gmail.com> wrote:
>
>> Hi Mentors,
>>
>> I created a github repository so that all the work related to
>> this project can be accumulated with ease.
>> here is the link
>> https://github.com/osuran/azure-membership-scheme.
>>
>> On Wed, May 11, 2016 at 11:22 AM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Hi Mentors,
>>>
>>> I sorted out all the errors and the cluster is up and running.
>>> Now I can see the log messages of members joining and leaving.
>>>
>>>
>>> On Wed, May 11, 2016 at 11:04 AM, Isuru Haththotuwa <
>>> isu...@wso2.com> wrote:
>>>
 Hi Osura,

 Please refer [1] for configuring deployment synchronizer.

 Initially, its ok even if you disable the deployment
 synchronizer and test the clustering.

 [1].
 https://docs.wso2.com/display/CLUSTER44x/Configuring+SVN-Based+Deployment+Synchronizer

>

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-27 Thread Awanthika Senarath

Thanks Susankha,

[+ Kavith]

Will have a look at this,



Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Sat, May 28, 2016 at 4:31 AM, Susankha Nirmala  wrote:

>
>
> On Fri, May 27, 2016 at 4:01 PM, Susankha Nirmala 
> wrote:
>
>> I was able to start ESB 5.0.0 using DevStudio 3.8.0 (with carbonserver
>> 4.4) with Java 1.7 and 1.8. Because, as I explained, in the DevS 3.8 we are
>> passing "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters(refer [1]).
>> Attached the screenshots to the mail.
>>
>>  @ Awanthika,
>>
>> You can pass the same "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
>> parameters in the DevStudio 4.1.0 (revert relevant changes in the commit
>> [2]). When you are testing, don't test with the selfhost devstudio, and
>> build the p2 locally and install that to fresh eclipse Mars pack.
>>
>> [1]-
>> https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>> [2]-
>> https://github.com/wso2/devstudio-tooling-platform/commit/e17477078563fc145da99a5460a6ef18af385822#diff-54e1d0cafafda5466af0c4671299155b
>>
>> Thanks.
>> /Susankha.
>>
>
>
>
>
>>
>> On Thu, May 26, 2016 at 9:45 PM, Susankha Nirmala 
>> wrote:
>>
>>>
>>> On Thu, May 26, 2016 at 9:02 PM, Awanthika Senarath 
>>> wrote:
>>>
 Hello Susankha,

 We cannot have those VM arguments in serverdefinition.xml as ESB 5.0.0
 which is based on carbon 4.4.1 has a different wso2carbon.sh which will not
 be able to start if we pass those VM arguments. So the option is to
 integrate a new server for carbon 4.4.1.

>>>
>>> ESB 5.0.0 is using the Carbon Kernel version 4.4.5 and in the
>>> "wso2server.sh" carbon file, it will check the Java version like below and
>>> assign the values of the VM parameters to the "JVM_MEM_OPTS" variable,
>>> according to the java version. Then use the "$JVM_MEM_OPTS" parameter in
>>> the
>>> system property section (refer [1])
>>>
>>>
>>> if [ -z "$JVM_MEM_OPTS" ]; then
>>>java_version=$("$JAVACMD" -version 2>&1 | awk -F '"' '/version/
>>> {print $2}')
>>>JVM_MEM_OPTS="-Xms256m -Xmx1024m"
>>>if [ "$java_version" \< "1.8" ]; then
>>>   JVM_MEM_OPTS="$JVM_MEM_OPTS -XX:MaxPermSize=256m"
>>>fi
>>> fi
>>>
>>> .
>>>
>>> while [ "$status" = "$START_EXIT_STATUS" ]
>>> do
>>> $JAVACMD \
>>> -Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
>>> $JVM_MEM_OPTS \
>>>
>>> Without creating a new server for ESB 5.0.0 (Carbon Kernel 4.4.5), we
>>> can use the same CarbonServer44 component.
>>> We can check the JAVA version and according to that, we can set the
>>> relavent VM parameters.
>>> I think that is the best way to handle this issue, without introduce a
>>> new CarbonSever vertion inside the DevStudio.
>>>
>>>
>>> [1]-
>>> https://github.com/wso2/carbon-kernel/blob/v4.4.5/distribution/kernel/carbon-home/bin/wso2server.sh
>>>
>>>
>>>
>>>



 Regards
 Awanthika

 Awanthika Senarath
 Software Engineer, WSO2 Inc.
 Mobile: +94717681791



 On Fri, May 27, 2016 at 9:15 AM, Susankha Nirmala 
 wrote:

>
>
> On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala 
> wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake <
>> jasin...@wso2.com> wrote:
>>
>>>
>>>
>>> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath <
>>> awanth...@wso2.com> wrote:
>>>
 Hello Nuwan,

 Please find my comments inline,

 I have noticed following issues while testing.


 https://wso2.org/jira/browse/TOOLS-3412

 As I have mentioned before this is a OS specific issue which comes
 in Linux and not a blocker. We will attempt to fix this as we move on.

 https://wso2.org/jira/browse/TOOLS-3416

>>>
>>> Actually this issue happens only when the server is started in JDK
>>> 1.7 if server runs on JDK 1.8 this issue won't be there , reason for 
>>> this
>>> issue is ,  memory settings are defined in two different ways for JDK 7 
>>> and
>>> 8  in carbons server , So we have to find  a way to distinguish  these 
>>> two
>>> settings inside the eclipse
>>>
>>
>>
>> This error happens due to missing "-Xms256m -Xmx1024m -XX:
>> MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 
>> 5.0.0
>> is support for Java 1.7.0 and 1.8.0 (refer [3]).
>> ESB 4.9.0 also supported for both Java versions and in the
>> carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
>> -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].
>>
>> With the Java 1.8, PermSize VM parameter not using, because in Java 8
>> PermGen is replace with Metaspace. But we need to support Both Java
>> versions (1.7 and 1.8).
>> We can p

Re: [Dev] Invalid Query error in AnalyticsDataAPI

2016-05-27 Thread Fathima Dilhasha

Hi Inosh,

Thank You.
I have configured analytics from API manager to DAS.
I will refer to the documentation links you have provided.

Regards,
Dilhasha
On 27 May 2016 21:59, "Inosh Goonewardena"  wrote:

Hi Dilhansa,

This query should be lucene query. Please refer [1]. Do you have data
published and indexed in DAS? If so, first you can check whether your query
is giving results from DAS data explorer. Please refer 'Searching by a
query' section in [2].

[1] https://docs.wso2.com/display/DAS301/Query+Language+Reference
[2]
https://docs.wso2.com/display/DAS301/Data+Explorer#DataExplorer-Searchingforrecordsofatable

On Fri, May 27, 2016 at 9:33 PM, Fathima Dilhasha  wrote:

> Following are some variations I tried out.
>
>
>-
>
>String query = "SELECT * FROM " + tables.get(i) + " WHERE " + columnName + 
> " = " + year + ";";
>
>-
>
>String query = "SELECT * FROM " + tables.get(i) + " WHERE " + columnName + 
> " = '" + year + "';";
>
>-
>
>String query = tables.get(i) + " : " + "SELECT * FROM " + tables.get(i) + 
> " WHERE " + columnName + " = " + year + ";";
>
>- I tried to use a 'PreparedStatement' as well. But that requires a
>database connection.
>
> Any help is appreciated.
>
> On Fri, May 27, 2016 at 5:54 PM, Fathima Dilhasha 
> wrote:
>
>> Hi,
>>
>> I'm trying to call "*search(int tenantId, String tableName, String
>> query, int start, int count)*" in *"org.wso2.carbon.analytics.*
>>
>> *api.AnalyticsDataAPI".*
>> The query I'm using is as follows.
>>
>> String query = "SELECT * FROM " + tables.get(i) + " WHERE " +
>> columnName + " = " + year;
>>
>> The error is as follows.
>>
>>
>> *[2016-05-27 17:45:45,152] ERROR
>> {org.wso2.carbon.analytics.dataservice.core.indexing.AnalyticsDataIndexer}
>> -  Error in index search: Invalid query, a term must have a
>> fieldjava.lang.RuntimeException: Invalid query, a term must have a field*
>>
>> I did various changes to the above mentioned query and tried out. But it
>> still gives the same error.
>> Am I doing something wrong?
>>
>> Thanks.
>> Dilhasha
>>
>> --
>> Fathima Dilhasha
>> *Software Engineer*
>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>> <%2B94%20%280%29%20773%20451194>
>> dilha...@wso2.com 
>>
>
>
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-27 Thread Susankha Nirmala

I was able to start ESB 5.0.0 using DevStudio 3.8.0 (with carbonserver 4.4)
with Java 1.7 and 1.8. Because, as I explained, in the DevS 3.8 we are
passing "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters(refer [1]).
Attached the screenshots to the mail.

 @ Awanthika,

You can pass the same "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
parameters in the DevStudio 4.1.0 (revert relevant changes in the commit
[2]). When you are testing, don't test with the selfhost devstudio, and
build the p2 locally and install that to fresh eclipse Mars pack.

[1]-
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
[2]-
https://github.com/wso2/devstudio-tooling-platform/commit/e17477078563fc145da99a5460a6ef18af385822#diff-54e1d0cafafda5466af0c4671299155b

Thanks.
/Susankha.

On Thu, May 26, 2016 at 9:45 PM, Susankha Nirmala  wrote:

>
> On Thu, May 26, 2016 at 9:02 PM, Awanthika Senarath 
> wrote:
>
>> Hello Susankha,
>>
>> We cannot have those VM arguments in serverdefinition.xml as ESB 5.0.0
>> which is based on carbon 4.4.1 has a different wso2carbon.sh which will not
>> be able to start if we pass those VM arguments. So the option is to
>> integrate a new server for carbon 4.4.1.
>>
>
> ESB 5.0.0 is using the Carbon Kernel version 4.4.5 and in the
> "wso2server.sh" carbon file, it will check the Java version like below and
> assign the values of the VM parameters to the "JVM_MEM_OPTS" variable,
> according to the java version. Then use the "$JVM_MEM_OPTS" parameter in
> the
> system property section (refer [1])
>
>
> if [ -z "$JVM_MEM_OPTS" ]; then
>java_version=$("$JAVACMD" -version 2>&1 | awk -F '"' '/version/ {print
> $2}')
>JVM_MEM_OPTS="-Xms256m -Xmx1024m"
>if [ "$java_version" \< "1.8" ]; then
>   JVM_MEM_OPTS="$JVM_MEM_OPTS -XX:MaxPermSize=256m"
>fi
> fi
>
> .
>
> while [ "$status" = "$START_EXIT_STATUS" ]
> do
> $JAVACMD \
> -Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
> $JVM_MEM_OPTS \
>
> Without creating a new server for ESB 5.0.0 (Carbon Kernel 4.4.5), we can
> use the same CarbonServer44 component.
> We can check the JAVA version and according to that, we can set the
> relavent VM parameters.
> I think that is the best way to handle this issue, without introduce a new
> CarbonSever vertion inside the DevStudio.
>
>
> [1]-
> https://github.com/wso2/carbon-kernel/blob/v4.4.5/distribution/kernel/carbon-home/bin/wso2server.sh
>
>
>
>
>>
>>
>>
>> Regards
>> Awanthika
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Fri, May 27, 2016 at 9:15 AM, Susankha Nirmala 
>> wrote:
>>
>>>
>>>
>>> On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala 
>>> wrote:
>>>


 On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake >>> > wrote:

>
>
> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath <
> awanth...@wso2.com> wrote:
>
>> Hello Nuwan,
>>
>> Please find my comments inline,
>>
>> I have noticed following issues while testing.
>>
>>
>> https://wso2.org/jira/browse/TOOLS-3412
>>
>> As I have mentioned before this is a OS specific issue which comes in
>> Linux and not a blocker. We will attempt to fix this as we move on.
>>
>> https://wso2.org/jira/browse/TOOLS-3416
>>
>
> Actually this issue happens only when the server is started in JDK 1.7
> if server runs on JDK 1.8 this issue won't be there , reason for this 
> issue
> is ,  memory settings are defined in two different ways for JDK 7 and 8  
> in
> carbons server , So we have to find  a way to distinguish  these two
> settings inside the eclipse
>


 This error happens due to missing "-Xms256m -Xmx1024m -XX:
 MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
 is support for Java 1.7.0 and 1.8.0 (refer [3]).
 ESB 4.9.0 also supported for both Java versions and in the
 carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
 -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].

 With the Java 1.8, PermSize VM parameter not using, because in Java 8
 PermGen is replace with Metaspace. But we need to support Both Java
 versions (1.7 and 1.8).
 We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
 parameters and when we are starting server in Java 1.8.0 it will give the
 following warning, but continue the starting process.

 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
 MaxPermSize=256m; support was removed in 8.0

 If you directly run ESB with Java 1.8.0, you can see above warning log.
 The best thing we can do is use the same VM parameters define in the
 wso2carbon.sh file in the carbon.definition.xml (that's what we have done
 with carbonserver 4.2 and that's why

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

2016-05-27 Thread Deependra Ariyadewa

This issue also exists in the  WSO2 API Manager Analytics  SNAPSHOT pack [1]

[1] Build WSO2 API Manager Analytics - Distribution (May 27, 2016 3:24:17
PM)

On Fri, May 27, 2016 at 1:08 AM, Bhathiya Jayasekara 
wrote:

> Thanks.
>
> On Fri, May 27, 2016 at 10:37 AM, Megala Uthayakumar 
> wrote:
>
>> We will do a release tonight.
>>
>> Thanks
>>
>> On Fri, May 27, 2016 at 10:33 AM, Bhathiya Jayasekara 
>> wrote:
>>
>>> We still have carbon dashboard 1.0.15 in APIM. Will upgrade. When are
>>> you planning to release this?
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>> On Fri, May 27, 2016 at 10:31 AM, Bhathiya Jayasekara >> > wrote:
>>>
 +Ruwan

 On Fri, May 27, 2016 at 10:20 AM, Megala Uthayakumar 
 wrote:

> Hi,
> This fix is available in carbon-dashboards 1.0.17-SNAPSHOT. Is APIM
> 2.0.0 SNAPSHOT uses the same version?
>
> Thanks.
>
> On Fri, May 27, 2016 at 10:02 AM, Deependra Ariyadewa 
> wrote:
>
>> This error still exists in the APIM 2.0.0 SNAPSHOT pack built on 26th
>> May 2016.
>>
>> On Thu, May 19, 2016 at 11:54 PM, Megala Uthayakumar > > wrote:
>>
>>> Hi,
>>>
>>> We have moved the fix for the google connectivity problem with the
>>> commit [1].
>>>
>>> [1]
>>> https://github.com/wso2/carbon-dashboards/commit/9e74ed2a788256cc429ffe35b6543c139d4c2ddb
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Megala
>>>
>>> On Wed, May 18, 2016 at 12:52 PM, Sinthuja Ragendran <
>>> sinth...@wso2.com> wrote:
>>>
 Hi Megala,

 Please check the shindig-server feature and try to remove the
 unwanted files from there it self, hence we can omit this behaviour.

 Thanks,
 Sinthuja.

 On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon 
 wrote:

> >>Can't we fix this during the shinding-server feature generation?
> +1
> So that every product using shindig does not have to unzip and zip
> the war file to fix it.
>
> Cheers,
> Ruwan
>
> On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran <
> sinth...@wso2.com> wrote:
>
>> Hi Tanya,
>>
>> Can't we fix this during the shinding-server feature generation?
>>
>> Thanks,
>> Sinthuja.
>>
>> On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara > > wrote:
>>
>>> Adding Bhathiya.
>>>
>>> We got same exception yesterday in APIM as well. We will need to
>>> same thing for DS as well.
>>>
>>> Thanks,
>>> Harsha
>>>
>>> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon <
>>> ruw...@wso2.com> wrote:
>>>
 Thanks Tanya for the information. We will follow the same as in
 DS.

 On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma <
 ta...@wso2.com> wrote:

> Hi Ruwan,
>
> Usually this error is thrown as shindig is trying to load some
> google analytics apis. So when there is no internet connection 
> this error
> can be observed.
> To get rid of this error we have to remove google related
> stuff from shindig features.txt file
>
> *features-extras/analytics/feature.xml*
> *features-extras/com.google.gadgets.analytics/feature.xml*
>
> But since we don't maintain a shindig fork, we can't do this
> from carbon-dashboards level. So in the Dashboard Server level we 
> are
> replacing the features.txt file with a file which doesn't have 
> above 2
> entries [1]. We'll have to do the same for apim analytics as well.
>
> [1]
> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>
> Thanks,
> Tanya
>
> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon <
> ruw...@wso2.com> wrote:
>
>> Hi DS team,
>> I am getting the following error in APIM 2.0.0-SNAPSHOT which
>> integrate DS features. Any Idea why? can we not print those 
>> errors due to
>> outside dependencies?
>>
>> ---
>>
>> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib.
>> One of the two will be used. Which one is undefined.
>>
>> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources
>> from res:features/features.txt are loading.
>>
>> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor
>> being used does not support secure parsing.

[Dev] [DEV] WSO2 Dashboard Server 2.1.0-M2 Released!

2016-05-27 Thread Lasantha Samarakoon

*WSO2 Dashboard Server 2.1.0-M2 Released!*

WSO2 Dashboard Server team is pleased to announce the release of WSO2
Dashboard Server 2.1.0 Milestone 2 [1]. This release comes with the
following bug fixes and features.

Bug

   - [UES-938 ] -
   FileNotFoundException at deploying artifact .car file
   - [UES-940 ] - Error in extracting
   file name from file path

Improvement

   - [UES-893 ] - 404 should be
   thrown when trying to access a non anon page by giving the url
   - [UES-937 ] - Allow user to
   choose a theme when the dashboard is created
   - [UES-950 ] - Create ES extension
   for DS compatible gadgets
   - [UES-951 ] - Update dashboard
   view theme

Moderation

   - [UES-939 ] - Error 400 page
   should match with other error response pages

New Feature

   - [UES-941 ] - Support to iframe
   the gadgets into different webpage
   - [UES-948 ] - Support to provide
   gadget load order for Dashboard Server
   - [UES-949 ] - Gadget generation
   framework



Reporting Issues

Issues can be reported through the Public JIRA project [2] for WSO2
Dashboard Server.

[1] https://github.com/wso2/product-ds/releases/tag/v2.1.0-m2
[2] https://wso2.org/jira/browse/UES



Regards,

WSO2 Dashboard Server Team


*Lasantha Samarakoon* | Software Engineer
WSO2, Inc.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 (71) 214 1576
Email:  lasant...@wso2.com
Web:www.wso2.com

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

Re: [Dev] [GSOC 16] Initial Project Progress

2016-05-27 Thread Osura Rathnayake

Hi mentors,

Sorry for the late reply. ARM portal doesn't have certain features like
Active Directory but it doesn't matter because they can be implemented
using classic portal and they work hand in hand. So all the features in
classic plus the new features in ARM can be used if we choose ARM model.
Therefore I think it's fruitful if we stick to ARM model, and the other
important thing is sooner or later Microsoft will develop the ARM fully so
eventually classic model will be obsolete(I think).

As we discussed in our last hangout, using a main program I could list out
the IP addresses of the VMs where Application Servers are installed. Please
arrange another hangout so that we can discuss the next project goal.




On Wed, May 25, 2016 at 9:08 PM, Osura Rathnayake 
wrote:

> Hi Imesh,
>
> okay i will find out the differences and update you. meanwhile i will
> check azure sdk for java if it has all the classes we want.
>
> On Wed, May 25, 2016 at 9:31 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Tue, May 24, 2016 at 10:22 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi mentors,
>>>
>>> As you might already know, Azure has two deployment models , azure
>>> classic (old portal) and azure resource manager (ARM)(new portal).
>>> Unfortunately some functionalities of classic is not available in ARM vice
>>> versa[1] but microsoft is rapidly developing all the functionalities across
>>> both models. Also certain API references [2] are not available for both the
>>> models, for an example, for network both classic and ARM API references are
>>> available but for network security groups only classic is available, while
>>> network security groups is a supported feature in ARM. shall we have a
>>> hangout to discuss this matter?
>>>
>>
>> IMO it would be okay to stick to one model. Can you please research on
>> this and list out the differences between two models? That would help us to
>> take a decision on this.
>>
>> Thanks
>>
>>>
>>> [1]
>>> https://blog.kloud.com.au/2016/04/05/azure-classic-vs-azure-resource-manager/
>>>
>>> [2] https://msdn.microsoft.com/en-us/library/azure/mt420159.aspx
>>>
>>>
>>>
>>> On Fri, May 20, 2016 at 11:05 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Are you joining the hangout now?

 On Thu, May 19, 2016 at 7:37 PM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> It's no problem. Okay let's have a hangout at 11 o'clock tomorrow.
>
> On Thursday, May 19, 2016, Isuru Haththotuwa  wrote:
>
>> Hi Osura,
>>
>> Sorry for the delayed response.
>>
>> Shall we have a hangout at 11 AM on 20th May (Friday)?
>>
>> On Tue, May 17, 2016 at 9:09 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Imesh,
>>>
>>> Shall we have a hangout on Thursday or so?
>>>
>>>
>>> On Thu, May 12, 2016 at 8:26 PM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Osura,

 On Thu, May 12, 2016 at 8:09 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Mentors,
>
> I created a github repository so that all the work related to this
> project can be accumulated with ease.
> here is the link https://github.com/osuran/azure-membership-scheme
> .
>

 Great! Will you be able to arrange a Hangout and demonstrate what
 you did so far?

 Thanks

 On Thu, May 12, 2016 at 8:09 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Mentors,
>
> I created a github repository so that all the work related to this
> project can be accumulated with ease.
> here is the link https://github.com/osuran/azure-membership-scheme
> .
>
> On Wed, May 11, 2016 at 11:22 AM, Osura Rathnayake <
> osura...@gmail.com> wrote:
>
>> Hi Mentors,
>>
>> I sorted out all the errors and the cluster is up and running.
>> Now I can see the log messages of members joining and leaving.
>>
>>
>> On Wed, May 11, 2016 at 11:04 AM, Isuru Haththotuwa <
>> isu...@wso2.com> wrote:
>>
>>> Hi Osura,
>>>
>>> Please refer [1] for configuring deployment synchronizer.
>>>
>>> Initially, its ok even if you disable the deployment
>>> synchronizer and test the clustering.
>>>
>>> [1].
>>> https://docs.wso2.com/display/CLUSTER44x/Configuring+SVN-Based+Deployment+Synchronizer
>>>
>>> On Wed, May 11, 2016 at 10:55 AM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi All,

 Thank you very much. I got it sorted out. I created a new user
 and granted permission on it.
 Can you please tell me the format of svn url and access
 protocol when configuring  , my
 repository is /home/as

[Dev] WSO2 App Manager 1.2.0-ALPHA Released!

2016-05-27 Thread Lahiru Cooray

*WSO2 App Manager 1.2.0-ALPHA Released!*


WSO2 App Manager team is pleased to announce WSO2 App Manager 1.2.0-ALPHA
release. Download distribution here
.
This release comes with following new features, bug fixes and improvements.

Bug Fixes
WSO2 App Manager 1.2.0-alpha resolved issues


Improvements
[APPM-1437]  - Navigation
improvement to Store
[APPM-1440]  - New theme for store
UI

New Features
[APPM-1442]  - New asset type -
Sites.
[APPM-1443]  - Configurable
subscription options for Web App and Sites asset types.
[APPM-1444]  - Multiple version
support for Web App and Sites  asset types.
[APPM-1446]  - Java APIs for all
key App Manager functionalities that need to be integrated with device
management functionalities.
[APPM-1445]  - Role based
visibility control for mobile apps
[APPM-1441]  - Redesign product
REST APIs with JAX-RS implementation and secure with OAuth
[APPM-1447]  - Associate business
owner for apps
Tasks
[APPM-1438]  - Responsive store UI
by Boostrap3 upgrade
[APPM-1439]  - Kernal version
upgrade to 4.4.5




Reporting Problems
Issues can be reported through public JIRA
 project assigned to WSO2 AppM.


Thanks,
App Manager team


-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] APIM 2.0.0-SNAPSHOT Nightly build - 27/05/2016

2016-05-27 Thread Bhathiya Jayasekara

Hi all,

Please find APIM 2.0.0 SNAPSHOT nightly build here[1].

[1]
https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/wso2am-2.0.0-SNAPSHOT-27-05-2016.zip

Thanks,

-- 
*Bhathiya Jayasekara*
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invalid Query error in AnalyticsDataAPI

2016-05-27 Thread Inosh Goonewardena

Hi Dilhansa,

This query should be lucene query. Please refer [1]. Do you have data
published and indexed in DAS? If so, first you can check whether your query
is giving results from DAS data explorer. Please refer 'Searching by a
query' section in [2].

[1] https://docs.wso2.com/display/DAS301/Query+Language+Reference
[2]
https://docs.wso2.com/display/DAS301/Data+Explorer#DataExplorer-Searchingforrecordsofatable

On Fri, May 27, 2016 at 9:33 PM, Fathima Dilhasha  wrote:

> Following are some variations I tried out.
>
>
>-
>
>String query = "SELECT * FROM " + tables.get(i) + " WHERE " + columnName + 
> " = " + year + ";";
>
>-
>
>String query = "SELECT * FROM " + tables.get(i) + " WHERE " + columnName + 
> " = '" + year + "';";
>
>-
>
>String query = tables.get(i) + " : " + "SELECT * FROM " + tables.get(i) + 
> " WHERE " + columnName + " = " + year + ";";
>
>- I tried to use a 'PreparedStatement' as well. But that requires a
>database connection.
>
> Any help is appreciated.
>
> On Fri, May 27, 2016 at 5:54 PM, Fathima Dilhasha 
> wrote:
>
>> Hi,
>>
>> I'm trying to call "*search(int tenantId, String tableName, String
>> query, int start, int count)*" in *"org.wso2.carbon.analytics.*
>>
>> *api.AnalyticsDataAPI".*
>> The query I'm using is as follows.
>>
>> String query = "SELECT * FROM " + tables.get(i) + " WHERE " +
>> columnName + " = " + year;
>>
>> The error is as follows.
>>
>>
>> *[2016-05-27 17:45:45,152] ERROR
>> {org.wso2.carbon.analytics.dataservice.core.indexing.AnalyticsDataIndexer}
>> -  Error in index search: Invalid query, a term must have a
>> fieldjava.lang.RuntimeException: Invalid query, a term must have a field*
>>
>> I did various changes to the above mentioned query and tried out. But it
>> still gives the same error.
>> Am I doing something wrong?
>>
>> Thanks.
>> Dilhasha
>>
>> --
>> Fathima Dilhasha
>> *Software Engineer*
>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>> <%2B94%20%280%29%20773%20451194>
>> dilha...@wso2.com 
>>
>
>
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the Jira project for "carbon-gateway-framework"

2016-05-27 Thread Lahiru Sandaruwan

Thanks Isuru.

On Fri, May 27, 2016 at 12:43 AM, Isuru Udana  wrote:

> Hi Lahiru,
>
> Jira project is,
>
> https://wso2.org/jira/browse/CGF
>
> Readme updated.
>
> Thanks.
>
>
> On Wed, May 25, 2016 at 9:41 PM, Lahiru Sandaruwan 
> wrote:
>
>> Hi,
>>
>> $subject? Shall we update in Readme?
>>
>> Thanks.
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> phone: +94773325954
>> email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> *Isuru Udana*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>



-- 
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

phone: +94773325954
email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invalid Query error in AnalyticsDataAPI

2016-05-27 Thread Fathima Dilhasha

Following are some variations I tried out.


   -

   String query = "SELECT * FROM " + tables.get(i) + " WHERE " +
columnName + " = " + year + ";";

   -

   String query = "SELECT * FROM " + tables.get(i) + " WHERE " +
columnName + " = '" + year + "';";

   -

   String query = tables.get(i) + " : " + "SELECT * FROM " +
tables.get(i) + " WHERE " + columnName + " = " + year + ";";

   - I tried to use a 'PreparedStatement' as well. But that requires a
   database connection.

Any help is appreciated.

On Fri, May 27, 2016 at 5:54 PM, Fathima Dilhasha  wrote:

> Hi,
>
> I'm trying to call "*search(int tenantId, String tableName, String query,
> int start, int count)*" in *"org.wso2.carbon.analytics.*
>
> *api.AnalyticsDataAPI".*
> The query I'm using is as follows.
>
> String query = "SELECT * FROM " + tables.get(i) + " WHERE " +
> columnName + " = " + year;
>
> The error is as follows.
>
>
> *[2016-05-27 17:45:45,152] ERROR
> {org.wso2.carbon.analytics.dataservice.core.indexing.AnalyticsDataIndexer}
> -  Error in index search: Invalid query, a term must have a
> fieldjava.lang.RuntimeException: Invalid query, a term must have a field*
>
> I did various changes to the above mentioned query and tried out. But it
> still gives the same error.
> Am I doing something wrong?
>
> Thanks.
> Dilhasha
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com 
>



-- 
Fathima Dilhasha
*Software Engineer*
Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
<%2B94%20%280%29%20773%20451194>
dilha...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Missing required capability in osgi component

2016-05-27 Thread Fathima Dilhasha

Hi Akila,

Thanks for the suggestion. But unfortunately, it didn't work for me. :(

Regards,
Dilhasha

On Fri, May 27, 2016 at 6:56 PM, Akila Ravihansa Perera 
wrote:

> What I'm suggesting is, instead of;
>
>
>
>
>
> */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" * 
> @scr.reference name="analytics.component" 
> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
> cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
> unbind="unsetAnalyticsDataAPI" */*
>
> try following;
>
>
>
> */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" * 
> @scr.reference name="analytics.component"
> ** * interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI"
> ** * cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
> unbind="unsetAnalyticsDataAPI"** */*
>
> The interface's fully qualified name should be in one line.
>
> On Fri, May 27, 2016 at 6:01 PM, Fathima Dilhasha 
> wrote:
>
>> Hi Akila,
>>
>> Do you suggest that the @scr.reference needs to be specified in one line
>> as follows?
>>
>>
>>
>>
>> ** @scr.reference name="analytics.component" 
>> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" 
>> cardinality="1..1" * policy="dynamic" bind="setAnalyticsDataAPI" 
>> unbind="unsetAnalyticsDataAPI"*
>>
>> @scr.reference interface is not specified in two lines though.
>>
>> Thanks.
>>
>>
>>
>> On Fri, May 27, 2016 at 5:05 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Fathima,
>>>
>>> The problem is with your service definition;
>>>
>>>
>>>
>>>
>>>
>>> */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" * 
>>> @scr.reference name="analytics.component" 
>>> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
>>> cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
>>> unbind="unsetAnalyticsDataAPI" */*
>>>
>>> Notice that @scr.reference interface is split into two lines? This is
>>> the root cause. Happened to me once ;)
>>>
>>> Thanks.
>>>
>>> On Fri, May 27, 2016 at 1:45 PM, Fathima Dilhasha 
>>> wrote:
>>>
 Please find attached pom.xml.

 On Fri, May 27, 2016 at 1:02 PM, Sameera Jayasoma 
 wrote:

> Can you attach the Pom.xml ?
>
>
> On Friday, May 27, 2016, Fathima Dilhasha  wrote:
>
>> The service is available and I can actually use it without any
>> problem. I'm calling some methods on it and they are working fine.
>> On 27 May 2016 12:17, "Sameera Jayasoma"  wrote:
>>
>>> Looks like this service is not available in your OSGi environment.
>>>
>>> *org.wso2.carbon.analytics.api.AnalyticsDataAPI*
>>>
>>> Can you double check on this?
>>>
>>> On Fri, May 27, 2016 at 12:08 PM, Anjana Fernando 
>>> wrote:
>>>
 Hi Sameera/Niranjan,

 You guys have any idea on to why this is happening? .. here, even
 though the OSGi is available and accessible to that bundle, it is still
 giving that message.

 Cheers,
 Anjana.

 On Fri, May 27, 2016 at 10:15 AM, Fathima Dilhasha <
 dilha...@wso2.com> wrote:

> Hi,
>
> I'm trying to build an osgi component which uses "
> *org.wso2.carbon.analytics.api.AnalyticsDataAPI*". When I add the
> bundle to carbon server, the bundle is working as expected. But in 
> the osgi
> console when I diagnose the bundle I get the following.
>
>
>
>
> *Direct constraints which are unresolved:Missing required
> capability Require-Capability: osgi.service;
> filter="(objectClass=org.wso2.carbon.analytics.api.AnalyticsDataAPI)"*
> Following are the imported packages in the written osgi component.
>
> 
>
> org.apache.commons.logging.*; 
> version="${commons.logging.version}",
> org.osgi.service.component; 
> version="${imp.pkg.version.osgi.service.component}",
> org.osgi.framework; version="${imp.pkg.version.osgi.framework}",
> org.wso2.carbon.core; version="${wso2das.version}",
> org.wso2.carbon.analytics.api.*; 
> version=${wso2analytics.api.version},
> org.wso2.carbon.analytics.datasource.commons.exception.*; 
> resolution:=optional
> 
>
>
> Following are the scr tags specified in the component.
>
>
>
>
>
>
>
> */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" 
> * @scr.reference name="analytics.component" 
> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
> cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
> unbind="unsetAnalyticsDataAPI" */*
>
> I highly appreciate any help on understandng this issue.
>
> Thanks
> Regards,

[Dev] ESB 5 Beta - Shared subscriber doesn't connect

2016-05-27 Thread Manuranga Perera

I am trying to connect to IBM MQ using JMS 2

http://ws.apache.org/ns/synapse"; name="TReaderPxy2"
startOnLoad="true">
   
  
 
 
 
  
   
   topic
   mySub
   TestQ49
   true
   1
   myTopicParams
   2.0
   true


First ESB instance can connect successfully and I can publish messages.
But when I start another identical instance I see following error.
It connects if subscriber names are distinct, but then messages are cloned,
not shared.

Please help me identify the issue.

TID: [-1234] [] [2016-05-27 11:11:07,719]  INFO
{org.apache.axis2.transport.jms.JMSListener} -  JMS listener started
{org.apache.axis2.transport.jms.JMSListener}
TID: [-1234] [] [2016-05-27 11:11:07,720] DEBUG
{org.apache.axis2.transport.jms.JMSEndpoint} -  JMS reply destination type
not given. default queue {org.apache.axis2.transport.jms.JMSEndpoint}
TID: [-1234] [] [2016-05-27 11:11:07,738] DEBUG
{org.apache.axis2.transport.jms.JMSUtils} -  Creating a GenericConnection
using credentials : (null/null) {org.apache.axis2.transport.jms.JMSUtils}
TID: [-1234] [] [2016-05-27 11:11:08,011]  INFO
{org.apache.axis2.transport.jms.JMSListener} -  Connection attempt: 1 for
JMS Provider for service: TReaderPxy2 was successful!
{org.apache.axis2.transport.jms.JMSListener}
TID: [-1234] [] [2016-05-27 11:11:08,011] DEBUG
{org.apache.axis2.transport.jms.ServiceTaskManager} -  The JMS Connection,
Session and MessageConsumer will be cached and shared between successive
poller task invocations {org.apache.axis2.transport.jms.ServiceTaskManager}
TID: [-1234] [] [2016-05-27 11:11:08,017]  INFO
{org.apache.axis2.transport.jms.ServiceTaskManager} -  Task manager for
service : TReaderPxy2 [re-]initialized
{org.apache.axis2.transport.jms.ServiceTaskManager}
TID: [-1] [] [2016-05-27 11:11:08,020] DEBUG
{org.apache.axis2.transport.jms.ServiceTaskManager} -  New poll task
starting : thread id = 82
{org.apache.axis2.transport.jms.ServiceTaskManager}
TID: [-1] [] [2016-05-27 11:11:08,026] DEBUG
{org.apache.axis2.transport.jms.ServiceTaskManager} -  Connected to the JMS
connection factory : USAPP2D.TCF
{org.apache.axis2.transport.jms.ServiceTaskManager}
TID: [-1] [] [2016-05-27 11:11:08,027] DEBUG
{org.apache.axis2.transport.jms.JMSUtils} -  Creating a TopicConnection
using credentials : (null/null) {org.apache.axis2.transport.jms.JMSUtils}
TID: [-1] [] [2016-05-27 11:11:08,055] DEBUG
{org.apache.axis2.transport.jms.ServiceTaskManager} -  JMS Connection for
service : TReaderPxy2 created and started
{org.apache.axis2.transport.jms.ServiceTaskManager}
TID: [-1] [] [2016-05-27 11:11:08,056] DEBUG
{org.apache.axis2.transport.jms.ServiceTaskManager} -  Creating a new JMS
Session for service : TReaderPxy2
{org.apache.axis2.transport.jms.ServiceTaskManager}
TID: [-1] [] [2016-05-27 11:11:08,113] DEBUG
{org.apache.axis2.transport.jms.ServiceTaskManager} -  Creating a new JMS
MessageConsumer for service : TReaderPxy2
{org.apache.axis2.transport.jms.ServiceTaskManager}
TID: [-1] [] [2016-05-27 11:11:08,143] DEBUG
{org.apache.axis2.transport.jms.ServiceTaskManager} -  JMS Destination with
JNDI name : TestQ49 found for service TReaderPxy2
{org.apache.axis2.transport.jms.ServiceTaskManager}
TID: [-1] [] [2016-05-27 11:11:08,198] ERROR
{org.apache.axis2.transport.jms.ServiceTaskManager} -  Error creating JMS
consumer for service : TReaderPxy2. JMSWMQ0026: Failed to subscribe to
topic 'TestQ49' with selector 'none' using MQSUB.
{org.apache.axis2.transport.jms.ServiceTaskManager}
com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ0026: Failed to
subscribe to topic 'TestQ49' with selector 'none' using MQSUB.
There may have been a problem creating the subscription due to it being
used by another message consumer.
Make sure any message consumers using this subscription are closed before
trying to create a new subscription under the same name. Please see the
linked exception for more information.
at
com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:472)
at
com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:214)
at
com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:212)
at
com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:112)
at
com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialize(WMQConsumerShadow.java:1038)
at
com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.initialize(WMQSyncConsumerShadow.java:134)
at
com.ibm.msg.client.wmq.internal.WMQMessageConsumer.(WMQMessageConsumer.java:470)
at
com.ibm.msg.client.wmq.internal.WMQSession.createDurableSubscriber(WMQSession.java:897)
at
com.ibm.msg.client.jms.internal.JmsSessionImpl.createDurableSubscriber(JmsSessionImpl.java:1166)
at com.ibm.mq.jms.MQSession.createDurableSubscriber(MQSession.java:539)
at org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:794)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.crea

Re: [Dev] Missing required capability in osgi component

2016-05-27 Thread Akila Ravihansa Perera

What I'm suggesting is, instead of;





*/** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool"
* @scr.reference name="analytics.component"
interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" *
cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI"
unbind="unsetAnalyticsDataAPI" */*

try following;



*/** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool"
* @scr.reference name="analytics.component"
** * interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI"
** * cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI"
unbind="unsetAnalyticsDataAPI"** */*

The interface's fully qualified name should be in one line.

On Fri, May 27, 2016 at 6:01 PM, Fathima Dilhasha  wrote:

> Hi Akila,
>
> Do you suggest that the @scr.reference needs to be specified in one line
> as follows?
>
>
>
>
> ** @scr.reference name="analytics.component" 
> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" cardinality="1..1" 
> * policy="dynamic" bind="setAnalyticsDataAPI" unbind="unsetAnalyticsDataAPI"*
>
> @scr.reference interface is not specified in two lines though.
>
> Thanks.
>
>
>
> On Fri, May 27, 2016 at 5:05 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Fathima,
>>
>> The problem is with your service definition;
>>
>>
>>
>>
>>
>> */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" * 
>> @scr.reference name="analytics.component" 
>> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
>> cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
>> unbind="unsetAnalyticsDataAPI" */*
>>
>> Notice that @scr.reference interface is split into two lines? This is the
>> root cause. Happened to me once ;)
>>
>> Thanks.
>>
>> On Fri, May 27, 2016 at 1:45 PM, Fathima Dilhasha 
>> wrote:
>>
>>> Please find attached pom.xml.
>>>
>>> On Fri, May 27, 2016 at 1:02 PM, Sameera Jayasoma 
>>> wrote:
>>>
 Can you attach the Pom.xml ?


 On Friday, May 27, 2016, Fathima Dilhasha  wrote:

> The service is available and I can actually use it without any
> problem. I'm calling some methods on it and they are working fine.
> On 27 May 2016 12:17, "Sameera Jayasoma"  wrote:
>
>> Looks like this service is not available in your OSGi environment.
>>
>> *org.wso2.carbon.analytics.api.AnalyticsDataAPI*
>>
>> Can you double check on this?
>>
>> On Fri, May 27, 2016 at 12:08 PM, Anjana Fernando 
>> wrote:
>>
>>> Hi Sameera/Niranjan,
>>>
>>> You guys have any idea on to why this is happening? .. here, even
>>> though the OSGi is available and accessible to that bundle, it is still
>>> giving that message.
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Fri, May 27, 2016 at 10:15 AM, Fathima Dilhasha <
>>> dilha...@wso2.com> wrote:
>>>
 Hi,

 I'm trying to build an osgi component which uses "
 *org.wso2.carbon.analytics.api.AnalyticsDataAPI*". When I add the
 bundle to carbon server, the bundle is working as expected. But in the 
 osgi
 console when I diagnose the bundle I get the following.




 *Direct constraints which are unresolved:Missing required
 capability Require-Capability: osgi.service;
 filter="(objectClass=org.wso2.carbon.analytics.api.AnalyticsDataAPI)"*
 Following are the imported packages in the written osgi component.

 

 org.apache.commons.logging.*; version="${commons.logging.version}",
 org.osgi.service.component; 
 version="${imp.pkg.version.osgi.service.component}",
 org.osgi.framework; version="${imp.pkg.version.osgi.framework}",
 org.wso2.carbon.core; version="${wso2das.version}",
 org.wso2.carbon.analytics.api.*; 
 version=${wso2analytics.api.version},
 org.wso2.carbon.analytics.datasource.commons.exception.*; 
 resolution:=optional
 


 Following are the scr tags specified in the component.







 */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" 
 * @scr.reference name="analytics.component" 
 interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
 cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
 unbind="unsetAnalyticsDataAPI" */*

 I highly appreciate any help on understandng this issue.

 Thanks
 Regards,
 Dilhasha


 --
 Fathima Dilhasha
 *Software Engineer*
 Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
 <%2B94%20%280%29%20773%20451194>
 dilha...@wso2.com

 ___
 Dev mailing list
 Dev@wso2.org
>

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 5.1.0 RC1

2016-05-27 Thread Niranjan Karunanandham

Hi all,

I have tested Carbon 5.1.0 RC1 with the following and found no issue.

   - Built carbon-datasources and tested a sample.
   - Built msf4j and tested the stockquote sample
   - Built carbon-caching and tested a sample
   - Tested JMX support by connect to the server via "Local Process"

[x] Stable - go ahead and release

Regards,
Nira

On Fri, May 27, 2016 at 5:19 PM, Nipuni Perera  wrote:

> Hi all,
>
> I have tested features below and no issues found.
>
>1. java.util.logging
>2. built carbon-jndi and tested a sample
>
> [x] Stable - go ahead and release
>
> Thanks,
> Nipuni
>
> On Fri, May 27, 2016 at 12:44 PM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the 1st Release Candidate of WSO2 Carbon Kernel 5.1.0
>>
>> This release fixed the following issues:
>> https://wso2.org/jira/issues/?filter=13077
>>
>> Please download and test your products with Kernel 5.1.0 RC1 and vote.
>>
>> *Source and binary distribution files:*
>>
>> https://github.com/wso2/carbon-kernel/releases/download/v5.1.0-rc1/wso2carbon-kernel-5.1.0.zip
>>
>> *Maven Staging repository:*
>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1020/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/carbon-kernel/releases/tag/v5.1.0-rc1
>>
>> [ ] Broken - do not releaes (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you,
>> Carbon Team
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> Nipuni Perera
> Software Engineer; WSO2 Inc.; http://wso2.com
> Email: nip...@wso2.com
> Git hub profile: https://github.com/nipuni
> Blog : http://nipunipererablog.blogspot.com/
> Mobile: +94 (71) 5626680
> 
>
>


-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Missing required capability in osgi component

2016-05-27 Thread Fathima Dilhasha

Hi Akila,

Do you suggest that the @scr.reference needs to be specified in one line as
follows?




** @scr.reference name="analytics.component"
interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI"
cardinality="1..1" * policy="dynamic" bind="setAnalyticsDataAPI"
unbind="unsetAnalyticsDataAPI"*

@scr.reference interface is not specified in two lines though.

Thanks.



On Fri, May 27, 2016 at 5:05 PM, Akila Ravihansa Perera 
wrote:

> Hi Fathima,
>
> The problem is with your service definition;
>
>
>
>
>
> */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" * 
> @scr.reference name="analytics.component" 
> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
> cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
> unbind="unsetAnalyticsDataAPI" */*
>
> Notice that @scr.reference interface is split into two lines? This is the
> root cause. Happened to me once ;)
>
> Thanks.
>
> On Fri, May 27, 2016 at 1:45 PM, Fathima Dilhasha 
> wrote:
>
>> Please find attached pom.xml.
>>
>> On Fri, May 27, 2016 at 1:02 PM, Sameera Jayasoma 
>> wrote:
>>
>>> Can you attach the Pom.xml ?
>>>
>>>
>>> On Friday, May 27, 2016, Fathima Dilhasha  wrote:
>>>
 The service is available and I can actually use it without any problem.
 I'm calling some methods on it and they are working fine.
 On 27 May 2016 12:17, "Sameera Jayasoma"  wrote:

> Looks like this service is not available in your OSGi environment.
>
> *org.wso2.carbon.analytics.api.AnalyticsDataAPI*
>
> Can you double check on this?
>
> On Fri, May 27, 2016 at 12:08 PM, Anjana Fernando 
> wrote:
>
>> Hi Sameera/Niranjan,
>>
>> You guys have any idea on to why this is happening? .. here, even
>> though the OSGi is available and accessible to that bundle, it is still
>> giving that message.
>>
>> Cheers,
>> Anjana.
>>
>> On Fri, May 27, 2016 at 10:15 AM, Fathima Dilhasha > > wrote:
>>
>>> Hi,
>>>
>>> I'm trying to build an osgi component which uses "
>>> *org.wso2.carbon.analytics.api.AnalyticsDataAPI*". When I add the
>>> bundle to carbon server, the bundle is working as expected. But in the 
>>> osgi
>>> console when I diagnose the bundle I get the following.
>>>
>>>
>>>
>>>
>>> *Direct constraints which are unresolved:Missing required
>>> capability Require-Capability: osgi.service;
>>> filter="(objectClass=org.wso2.carbon.analytics.api.AnalyticsDataAPI)"*
>>> Following are the imported packages in the written osgi component.
>>>
>>> 
>>>
>>> org.apache.commons.logging.*; version="${commons.logging.version}",
>>> org.osgi.service.component; 
>>> version="${imp.pkg.version.osgi.service.component}",
>>> org.osgi.framework; version="${imp.pkg.version.osgi.framework}",
>>> org.wso2.carbon.core; version="${wso2das.version}",
>>> org.wso2.carbon.analytics.api.*; 
>>> version=${wso2analytics.api.version},
>>> org.wso2.carbon.analytics.datasource.commons.exception.*; 
>>> resolution:=optional
>>> 
>>>
>>>
>>> Following are the scr tags specified in the component.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" * 
>>> @scr.reference name="analytics.component" 
>>> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
>>> cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
>>> unbind="unsetAnalyticsDataAPI" */*
>>>
>>> I highly appreciate any help on understandng this issue.
>>>
>>> Thanks
>>> Regards,
>>> Dilhasha
>>>
>>>
>>> --
>>> Fathima Dilhasha
>>> *Software Engineer*
>>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>>> <%2B94%20%280%29%20773%20451194>
>>> dilha...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Anjana Fernando*
>> Senior Technical Lead
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Software Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://blog.sameera.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . E

[Dev] Invalid Query error in AnalyticsDataAPI

2016-05-27 Thread Fathima Dilhasha

Hi,

I'm trying to call "*search(int tenantId, String tableName, String query,
int start, int count)*" in *"org.wso2.carbon.analytics.*

*api.AnalyticsDataAPI".*
The query I'm using is as follows.

String query = "SELECT * FROM " + tables.get(i) + " WHERE " +
columnName + " = " + year;

The error is as follows.


*[2016-05-27 17:45:45,152] ERROR
{org.wso2.carbon.analytics.dataservice.core.indexing.AnalyticsDataIndexer}
-  Error in index search: Invalid query, a term must have a
fieldjava.lang.RuntimeException: Invalid query, a term must have a field*

I did various changes to the above mentioned query and tried out. But it
still gives the same error.
Am I doing something wrong?

Thanks.
Dilhasha

-- 
Fathima Dilhasha
*Software Engineer*
Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
<%2B94%20%280%29%20773%20451194>
dilha...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC 2016]Proposal 03: [ML]Visual(Deep) Neural Network Builder -Project Progress

2016-05-27 Thread Supun Sethunga

Hi Lakini,

Sorry for the delayed response. As the first part of the project, you can
start the work on the UI/drag and drop feature, as the core of your project
is based around that. Therefore, shall we try to get a basic version of
drag and drop UI, by the mid-term evaluation? (No need to connect the UI
with the dl4j, for the first phase)  So this would be include:

   - A link/re-direct to go to Visual builder, upon selecting the Neural
   Netowrks (as the algorithm)
   - The drawing/dropping area and a panel to pick the objects to be
   dragged (objects as in, nodes, layers, links, etc)

This drag and drop page should replace the hyper-parameter page in the ML
UI. More precisely, In the Machine Learner wizard, when a user picks the
algorithm name as Neural Network, and proceed, this drag and drop page
should be prompted instead of the hyper-parameters page. You can create the
overall page as a jaggery page (.jag). It would be easier for you to get a
copy of an existing page, and modifying the content. That will preserve the
existing styles, session handling etc.

Please feel free to raise any question you come across during implementing.

Regards,
Supun

On Tue, May 24, 2016 at 8:09 PM, Lakini Senanayaka <
lakinisenanayak...@gmail.com> wrote:

> Hi,
>
> Thank you very much for the suggestions.I will be using JQueryUI.
>
> As my coding period started yesterday according to the GSoC Schedule  I
> would like to know the workload that should be completed
> before the midterm evaluation. Please advise me accordingly.
>
> Thank you.
>
>
> On Tue, May 24, 2016 at 10:34 AM, Supun Sethunga  wrote:
>
>> Hi Lakini,
>>
>> Yes you can use any of them, with open source licence. But I would prefer
>> JQueryUI, as its a well known library, and is already been used by some of
>> the wso2 products.
>>
>> Regards,
>> Supun
>>
>> On Tue, May 24, 2016 at 9:29 AM, Lakini Senanayaka <
>> lakinisenanayak...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I have found some libraries to build drag and drop UI for our front end
>>> .They are JQury UI[1],Dragula[2],Draggablily[3].
>>> I hope I can do the developments using these libraries.
>>>
>>> [1]jqueryui 
>>> [2]dragula 
>>> [3]draggabilly 
>>>
>>> Could you please tell me if you have any other suggestions?
>>>
>>> On Sat, May 21, 2016 at 11:05 PM, Lakini Senanayaka <
>>> lakinisenanayak...@gmail.com> wrote:
>>>
 Hi ,

 This is my weekly progress update of my project.

 I have solved all the problems I have mentioned  in the last email.I
 could find a class BaseDatasetIterator which is in DL4J where we can find
 inbuilt iterators for CurvesDataSetIterator, IrisDataSetIterator,
 MnistDataSetIterator, MovingWindowBaseDataSetIterator,
 RawMnistDataSetIterator .There is no iterator for CIFAR dataset yet.

 I have gone through the whole documentation except Deeplearning4j on
 Spark.The latest documentation is very understandable than the earlier
 one.I have studied neural networks-  Restricted Boltzmann Machines,
 Convolutional Nets (ConvNets),
 Long Short-Term Memory Units (LSTMs),
 Denoising Autoencoders,
 Recurrent Nets and LSTMs,
 Multilayer Neural Nets,
 Deep-Belief Network,
 Deep AutoEncoder,
 Stacked Denoising Autoencoders

 I have run the example codes[1] and I have understood the
 implementations.I have rerun the codes with modifying different parameter
 values like number and size of the hidden layers,  learning rate, momentum,
 weight distribution and various types of regularization and checked the
 performance.

 I have implemented a convolution net[3] and trained it using LFW
 dataset[2] and a Recurrent net[4].Still I have a problem in vectorizing
 CIFRA-10 data set.

 Currently  I am researching about  libraries to build drag & drop UI
 for front end.

 [1]dl4j-0.4-examples

 [2]LFW Face Dataset 
 [3]ConvolutionNetLFW

 [4]RecurrentNetworkExample

 Could you please guide me to do the next step of my project .

 Thank you.

 Sincerely,
 *Lakini Senanayaka.*

>>>
>>>
>>> --
>>> Thank you.
>>>
>>> Sincerely,
>>> *Lakini Senanayaka.*
>>>
>>>
>>
>>
>> --
>> *Supun Sethunga*
>> Software Engineer
>> WSO2, Inc.
>> http://wso2.com/
>> lean | enterprise | middleware
>> Mobile : +94 716546324
>>
>
>
>
>

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 5.1.0 RC1

2016-05-27 Thread Nipuni Perera

Hi all,

I have tested features below and no issues found.

   1. java.util.logging
   2. built carbon-jndi and tested a sample

[x] Stable - go ahead and release

Thanks,
Nipuni

On Fri, May 27, 2016 at 12:44 PM, Niranjan Karunanandham 
wrote:

> Hi Devs,
>
> This is the 1st Release Candidate of WSO2 Carbon Kernel 5.1.0
>
> This release fixed the following issues:
> https://wso2.org/jira/issues/?filter=13077
>
> Please download and test your products with Kernel 5.1.0 RC1 and vote.
>
> *Source and binary distribution files:*
>
> https://github.com/wso2/carbon-kernel/releases/download/v5.1.0-rc1/wso2carbon-kernel-5.1.0.zip
>
> *Maven Staging repository:*
> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1020/
>
> *The tag to be voted upon:*
> https://github.com/wso2/carbon-kernel/releases/tag/v5.1.0-rc1
>
> [ ] Broken - do not releaes (explain why)
> [ ] Stable - go ahead and release
>
> Thank you,
> Carbon Team
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



-- 
Nipuni Perera
Software Engineer; WSO2 Inc.; http://wso2.com
Email: nip...@wso2.com
Git hub profile: https://github.com/nipuni
Blog : http://nipunipererablog.blogspot.com/
Mobile: +94 (71) 5626680

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

Re: [Dev] Missing required capability in osgi component

2016-05-27 Thread Akila Ravihansa Perera

Hi Fathima,

The problem is with your service definition;





*/** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool"
* @scr.reference name="analytics.component"
interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" *
cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI"
unbind="unsetAnalyticsDataAPI" */*

Notice that @scr.reference interface is split into two lines? This is the
root cause. Happened to me once ;)

Thanks.

On Fri, May 27, 2016 at 1:45 PM, Fathima Dilhasha  wrote:

> Please find attached pom.xml.
>
> On Fri, May 27, 2016 at 1:02 PM, Sameera Jayasoma 
> wrote:
>
>> Can you attach the Pom.xml ?
>>
>>
>> On Friday, May 27, 2016, Fathima Dilhasha  wrote:
>>
>>> The service is available and I can actually use it without any problem.
>>> I'm calling some methods on it and they are working fine.
>>> On 27 May 2016 12:17, "Sameera Jayasoma"  wrote:
>>>
 Looks like this service is not available in your OSGi environment.

 *org.wso2.carbon.analytics.api.AnalyticsDataAPI*

 Can you double check on this?

 On Fri, May 27, 2016 at 12:08 PM, Anjana Fernando 
 wrote:

> Hi Sameera/Niranjan,
>
> You guys have any idea on to why this is happening? .. here, even
> though the OSGi is available and accessible to that bundle, it is still
> giving that message.
>
> Cheers,
> Anjana.
>
> On Fri, May 27, 2016 at 10:15 AM, Fathima Dilhasha 
> wrote:
>
>> Hi,
>>
>> I'm trying to build an osgi component which uses "
>> *org.wso2.carbon.analytics.api.AnalyticsDataAPI*". When I add the
>> bundle to carbon server, the bundle is working as expected. But in the 
>> osgi
>> console when I diagnose the bundle I get the following.
>>
>>
>>
>>
>> *Direct constraints which are unresolved:Missing required
>> capability Require-Capability: osgi.service;
>> filter="(objectClass=org.wso2.carbon.analytics.api.AnalyticsDataAPI)"*
>> Following are the imported packages in the written osgi component.
>>
>> 
>>
>> org.apache.commons.logging.*; version="${commons.logging.version}",
>> org.osgi.service.component; 
>> version="${imp.pkg.version.osgi.service.component}",
>> org.osgi.framework; version="${imp.pkg.version.osgi.framework}",
>> org.wso2.carbon.core; version="${wso2das.version}",
>> org.wso2.carbon.analytics.api.*; 
>> version=${wso2analytics.api.version},
>> org.wso2.carbon.analytics.datasource.commons.exception.*; 
>> resolution:=optional
>> 
>>
>>
>> Following are the scr tags specified in the component.
>>
>>
>>
>>
>>
>>
>>
>> */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" * 
>> @scr.reference name="analytics.component" 
>> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
>> cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
>> unbind="unsetAnalyticsDataAPI" */*
>>
>> I highly appreciate any help on understandng this issue.
>>
>> Thanks
>> Regards,
>> Dilhasha
>>
>>
>> --
>> Fathima Dilhasha
>> *Software Engineer*
>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>> <%2B94%20%280%29%20773%20451194>
>> dilha...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>



 --
 Sameera Jayasoma,
 Software Architect,

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://blog.sameera.org
 twitter: https://twitter.com/sameerajayasoma
 flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
 Mobile: 0094776364456

 Lean . Enterprise . Middleware


>>
>> --
>> Sameera Jayasoma,
>> Software Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://blog.sameera.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>> Lean . Enterprise . Middleware
>>
>>
>>
>
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

2016-05-27 Thread Dilshani Subasinghe

Hi Nuwan,

When I am going to test JMS parameters according to a given support issue,
it was not released BETA pack and used ALPHA pack. But I tested this
scenario again with BETA pack and still see the same issue.

Reported an jira[1] with the issue.

[1] https://wso2.org/jira/browse/ESBJAVA-4632

Regards,
Dilshani


On Fri, May 27, 2016 at 2:53 PM, Nuwan Wimalasekara  wrote:

> Hi Dilshani,
>
> Which ESB version are you using to test this scenario. Can you please
> check this on ESB 5.0.0-BETA pack?
> I could not observe such a behaviour in ESB 5.0.0-BETA.
>
> Thanks,
> Nuwanw
>
> On Thu, May 26, 2016 at 2:50 PM, Dilshani Subasinghe 
> wrote:
>
>> Hi Nuwan,
>>
>> Thank you for your response. I tried with both
>>
>>
>> *java.naming.provider.url=failover:tcp://localhost:61616, and *
>>
>>
>> *java.naming.provider.url=failover:(tcp://localhost:61616).*
>> But still missing messages.
>>
>> Regards,
>> Dilshani
>>
>>
>> On Thu, May 26, 2016 at 2:15 PM, Nuwan Wimalasekara 
>> wrote:
>>
>>> Hi Dilshani,
>>>
>>>
>>> On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe 
>>> wrote:
>>>
 Hi Nuwan,

 Yes I configured jms url with failover. Actually I used failover syntax
 as u asked me to change
 (java.naming.provider.url=failover:(tcp://localhost:61616) or
  java.naming.provider.url=failover:tcp://localhost:61616)

 Proxy config:

 >>> uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&
 *java.naming.provider.url=failover:tcp://localhost:61616*
 &transport.jms.DestinationType=queue&transport.jms.SessionTransacted=true&transport.Transactionality=local"/>

>>>
>>>

 I'm really sorry I didn't get your suggestion. Can you point out the
 error within my config?

>>> The problem in your config is , that there is no '*,*'  at the end of
>>> the url.
>>> It should be as bellow.
>>>
>>> *java.naming.provider.url=failover:tcp://localhost:61616,*
>>>
>>> New Config:
>>> >> uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&
>>> *java.naming.provider.url=failover:tcp://localhost:61616,*
>>> &transport.jms.DestinationType=queue&transport.jms.SessionTransacted=true&transport.Transactionality=local"/>
>>>
>>> Thanks,
>>> Nuwanw
>>>
>>>
>>>
 Regards,
 Dilshani


 On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara 
 wrote:

> Hi Dilshani,
>
>  In your proxy config, you have defined a jms url with failover. Can
> you please try the failover url syntax as one of bellow. I think it is due
> to invalid url definition of failover for ActiveMQ.
>
> Please refer[1] for failover url syntax in ActiveMQ
>
> java.naming.provider.url=failover:(tcp://localhost:61616) or
>  java.naming.provider.url=failover:tcp://localhost:61616,
>
> [1] http://activemq.apache.org/failover-transport-reference.html
>
> Thanks,
> Nuwanw
>
> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <
> dilsh...@wso2.com> wrote:
>
>> Hi ESB Team,
>>
>> I am testing JMS parameters and identified scenario of missing
>> messages when using "transport.Transactionality" parameter.
>>
>> Configured axis2.xml as follows;
>>
>>   > class="org.apache.axis2.transport.jms.JMSListener">
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > name="transport.jms.ConnectionFactoryJNDIName"
>> locked="false">TopicConnectionFactory
>> > locked="false">topic
>> > locked="false">topic
>>
>> * > locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>>
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > name="transport.jms.ConnectionFactoryJNDIName"
>> locked="false">QueueConnectionFactory
>> > locked="false">queue
>>
>> * > locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>>
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > name="transport.jms.ConnectionFactoryJNDIName"
>> locked="false">TopicConnectionFactory
>> > locked="false">topic
>> > locked="false">topic
>>
>> *  >>>

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

2016-05-27 Thread Nuwan Wimalasekara

Hi Dilshani,

Which ESB version are you using to test this scenario. Can you please check
this on ESB 5.0.0-BETA pack?
I could not observe such a behaviour in ESB 5.0.0-BETA.

Thanks,
Nuwanw

On Thu, May 26, 2016 at 2:50 PM, Dilshani Subasinghe 
wrote:

> Hi Nuwan,
>
> Thank you for your response. I tried with both
>
>
> *java.naming.provider.url=failover:tcp://localhost:61616, and *
>
>
> *java.naming.provider.url=failover:(tcp://localhost:61616).*
> But still missing messages.
>
> Regards,
> Dilshani
>
>
> On Thu, May 26, 2016 at 2:15 PM, Nuwan Wimalasekara 
> wrote:
>
>> Hi Dilshani,
>>
>>
>> On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> Yes I configured jms url with failover. Actually I used failover syntax
>>> as u asked me to change
>>> (java.naming.provider.url=failover:(tcp://localhost:61616) or
>>>  java.naming.provider.url=failover:tcp://localhost:61616)
>>>
>>> Proxy config:
>>>
>>> >> uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&
>>> *java.naming.provider.url=failover:tcp://localhost:61616*
>>> &transport.jms.DestinationType=queue&transport.jms.SessionTransacted=true&transport.Transactionality=local"/>
>>>
>>
>>
>>>
>>> I'm really sorry I didn't get your suggestion. Can you point out the
>>> error within my config?
>>>
>> The problem in your config is , that there is no '*,*'  at the end of
>> the url.
>> It should be as bellow.
>>
>> *java.naming.provider.url=failover:tcp://localhost:61616,*
>>
>> New Config:
>> > uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&
>> *java.naming.provider.url=failover:tcp://localhost:61616,*
>> &transport.jms.DestinationType=queue&transport.jms.SessionTransacted=true&transport.Transactionality=local"/>
>>
>> Thanks,
>> Nuwanw
>>
>>
>>
>>> Regards,
>>> Dilshani
>>>
>>>
>>> On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara 
>>> wrote:
>>>
 Hi Dilshani,

  In your proxy config, you have defined a jms url with failover. Can
 you please try the failover url syntax as one of bellow. I think it is due
 to invalid url definition of failover for ActiveMQ.

 Please refer[1] for failover url syntax in ActiveMQ

 java.naming.provider.url=failover:(tcp://localhost:61616) or
  java.naming.provider.url=failover:tcp://localhost:61616,

 [1] http://activemq.apache.org/failover-transport-reference.html

 Thanks,
 Nuwanw

 On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <
 dilsh...@wso2.com> wrote:

> Hi ESB Team,
>
> I am testing JMS parameters and identified scenario of missing
> messages when using "transport.Transactionality" parameter.
>
> Configured axis2.xml as follows;
>
>    class="org.apache.axis2.transport.jms.JMSListener">
> 
>  locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  locked="false">failover:tcp://localhost:61616
>  name="transport.jms.ConnectionFactoryJNDIName"
> locked="false">TopicConnectionFactory
>  locked="false">topic
>  locked="false">topic
>
> *  locked="false">local name="transport.jms.SessionTransacted" locked="false">true*
> 
>
> 
>  locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  locked="false">failover:tcp://localhost:61616
>  name="transport.jms.ConnectionFactoryJNDIName"
> locked="false">QueueConnectionFactory
>  locked="false">queue
>
> *  locked="false">local name="transport.jms.SessionTransacted" locked="false">true*
> 
>
> 
>  locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  locked="false">failover:tcp://localhost:61616
>  name="transport.jms.ConnectionFactoryJNDIName"
> locked="false">TopicConnectionFactory
>  locked="false">topic
>  locked="false">topic
>
> *   locked="false">local name="transport.jms.SessionTransacted" locked="false">true*
> 
> 
>
> And aslo added same parameters to JMS sender too.
>
>    class="org.apache.axis2.transport.jms.JMSSender">
>
>  locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  locked="false">failover:tcp://localhost:61616
>  name="transport.jms.ConnectionFactoryJNDIName"
> locked="false">To

Re: [Dev] Missing required capability in osgi component

2016-05-27 Thread Fathima Dilhasha

Please find attached pom.xml.

On Fri, May 27, 2016 at 1:02 PM, Sameera Jayasoma  wrote:

> Can you attach the Pom.xml ?
>
>
> On Friday, May 27, 2016, Fathima Dilhasha  wrote:
>
>> The service is available and I can actually use it without any problem.
>> I'm calling some methods on it and they are working fine.
>> On 27 May 2016 12:17, "Sameera Jayasoma"  wrote:
>>
>>> Looks like this service is not available in your OSGi environment.
>>>
>>> *org.wso2.carbon.analytics.api.AnalyticsDataAPI*
>>>
>>> Can you double check on this?
>>>
>>> On Fri, May 27, 2016 at 12:08 PM, Anjana Fernando 
>>> wrote:
>>>
 Hi Sameera/Niranjan,

 You guys have any idea on to why this is happening? .. here, even
 though the OSGi is available and accessible to that bundle, it is still
 giving that message.

 Cheers,
 Anjana.

 On Fri, May 27, 2016 at 10:15 AM, Fathima Dilhasha 
 wrote:

> Hi,
>
> I'm trying to build an osgi component which uses "
> *org.wso2.carbon.analytics.api.AnalyticsDataAPI*". When I add the
> bundle to carbon server, the bundle is working as expected. But in the 
> osgi
> console when I diagnose the bundle I get the following.
>
>
>
>
> *Direct constraints which are unresolved:Missing required
> capability Require-Capability: osgi.service;
> filter="(objectClass=org.wso2.carbon.analytics.api.AnalyticsDataAPI)"*
> Following are the imported packages in the written osgi component.
>
> 
>
> org.apache.commons.logging.*; version="${commons.logging.version}",
> org.osgi.service.component; 
> version="${imp.pkg.version.osgi.service.component}",
> org.osgi.framework; version="${imp.pkg.version.osgi.framework}",
> org.wso2.carbon.core; version="${wso2das.version}",
> org.wso2.carbon.analytics.api.*; version=${wso2analytics.api.version},
> org.wso2.carbon.analytics.datasource.commons.exception.*; 
> resolution:=optional
> 
>
>
> Following are the scr tags specified in the component.
>
>
>
>
>
>
>
> */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" * 
> @scr.reference name="analytics.component" 
> interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
> cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
> unbind="unsetAnalyticsDataAPI" */*
>
> I highly appreciate any help on understandng this issue.
>
> Thanks
> Regards,
> Dilhasha
>
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Anjana Fernando*
 Senior Technical Lead
 WSO2 Inc. | http://wso2.com
 lean . enterprise . middleware

>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Software Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://blog.sameera.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>
>


-- 
Fathima Dilhasha
*Software Engineer*
Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
<%2B94%20%280%29%20773%20451194>
dilha...@wso2.com 



http://maven.apache.org/POM/4.0.0";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";>

org.wso2.carbon.cloud
cloud-tools
1.0.0
../../pom.xml


4.0.0
org.wso2.carbon
org.wso2.carbon.cloud.das.datapurge.tool
1.0.0
bundle
Cloud - DAS DataPurge Tool
Tool to purge unnecessary data from DAS




org.apache.felix
maven-scr-plugin


generate-scr-scrdescriptor

scr





org.apache.felix
maven-bundle-plugin
true


${project.artifactId}
${project.artifactId}

org.wso2.carbon

Re: [Dev] Missing required capability in osgi component

2016-05-27 Thread Sameera Jayasoma

Can you attach the Pom.xml ?

On Friday, May 27, 2016, Fathima Dilhasha  wrote:

> The service is available and I can actually use it without any problem.
> I'm calling some methods on it and they are working fine.
> On 27 May 2016 12:17, "Sameera Jayasoma"  > wrote:
>
>> Looks like this service is not available in your OSGi environment.
>>
>> *org.wso2.carbon.analytics.api.AnalyticsDataAPI*
>>
>> Can you double check on this?
>>
>> On Fri, May 27, 2016 at 12:08 PM, Anjana Fernando > > wrote:
>>
>>> Hi Sameera/Niranjan,
>>>
>>> You guys have any idea on to why this is happening? .. here, even though
>>> the OSGi is available and accessible to that bundle, it is still giving
>>> that message.
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Fri, May 27, 2016 at 10:15 AM, Fathima Dilhasha >> > wrote:
>>>
 Hi,

 I'm trying to build an osgi component which uses "
 *org.wso2.carbon.analytics.api.AnalyticsDataAPI*". When I add the
 bundle to carbon server, the bundle is working as expected. But in the osgi
 console when I diagnose the bundle I get the following.

 *Direct constraints which are unresolved:Missing required
 capability Require-Capability: osgi.service;
 filter="(objectClass=org.wso2.carbon.analytics.api.AnalyticsDataAPI)"*
 Following are the imported packages in the written osgi component.

 org.apache.commons.logging.*; version="${commons.logging.version}",
 org.osgi.service.component; 
 version="${imp.pkg.version.osgi.service.component}",
 org.osgi.framework; version="${imp.pkg.version.osgi.framework}",
 org.wso2.carbon.core; version="${wso2das.version}",
 org.wso2.carbon.analytics.api.*; version=${wso2analytics.api.version},
 org.wso2.carbon.analytics.datasource.commons.exception.*; 
 resolution:=optional

 Following are the scr tags specified in the component.

 */** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool" * 
 @scr.reference name="analytics.component" 
 interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" * 
 cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI" 
 unbind="unsetAnalyticsDataAPI" */*

 I highly appreciate any help on understandng this issue.

 Thanks
 Regards,
 Dilhasha

 --
 Fathima Dilhasha
 *Software Engineer*
 Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
 <%2B94%20%280%29%20773%20451194>
 dilha...@wso2.com 

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

>>>
>>>
>>> --
>>> *Anjana Fernando*
>>> Senior Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Software Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> 
>> blog: http://blog.sameera.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>> Lean . Enterprise . Middleware
>>
>>

-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://blog.sameera.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

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

Re: [Dev] Fwd: GSOC2016: [ML][CEP] Predictive analytic with online data for WSO2 Machine Learner

2016-05-27 Thread Mahesh Dananjaya

Hi maheshkaya,
i have written some siddhi extension and trying to develop a one for my
one. In time series example in the [1], can you please explain me the input
format and query lines in that example for my understanding.

from baseballData#timeseries:regress(2, 1, 0.95, salary, rbi, walks,
strikeouts, errors)
select *
insert into regResults;

i just want to knwo how i give a set of data into this extension and what
is baseballData. Is it input stream as usual.or any data file?how can i
find that data set to create dummy input stream like baseballData?

thank you.
regards,
Mahesh.
[1]
https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+Extension

On Thu, May 26, 2016 at 2:58 PM, Mahesh Dananjaya  wrote:

> Hi Maheshakya,
> today i got the siddhi and debug the math extention. then did some changes
> and check. Now i am trying to write same kind of extension in my code base.
> so i add dependencies and it was built fine. Now i am trying to debug my
> extension and i did the same thing as i did in previous case. Cep is
> sending data, bu my extension is not firing in relevant break point.
> 1. So how can i debug the siddhi extension in my new extension.(you can
> see it in my example repoo)
>
> I think if i do it correctly we can built the extension for our purpose.
> And i will send the relevant timing report of SGD algorithms very soon as
> supun was asking me. thank you.
> regards,
> Mahesh.
>
> On Tue, May 24, 2016 at 11:07 AM, Maheshakya Wijewardena <
> mahesha...@wso2.com> wrote:
>
>> Also note that there is a calculation interval in the siddhi time series
>> regression function[1]. You maybe able get some insight for this from that
>> as well.
>>
>> [1] https://docs.wso2.com/display/CEP400/Regression
>>
>> On Tue, May 24, 2016 at 11:03 AM, Maheshakya Wijewardena <
>> mahesha...@wso2.com> wrote:
>>
>>> Hi Mahesh,
>>>
>>> As we discussed offline, we can use similar mechanism to train linear
>>> regression models, logistic regression models and k-means clustering models.
>>>
>>> It is very interesting that i have found that somethings that can make
 use of our work. In the cep 4.0 documentation there is a Custom Stream
 Processor Extention program [1]. There is a example of
 LinearRegressionStreamProcessor [1].

>>>
>>> As we have to train predictive models with Spark, you can write wrappers
>>> around regression/clustering models of Spark. Refer to Siddhi time series
>>> regression source codes[1][2]. You can write a streaming linear regression
>>> class for ML in a similar fashion by wrapping Spark mllib implementations.
>>> You can use the methods "addEvent", "removeEvent", etc. (may have to be
>>> changed according to requirements) for the similar purpose. You can
>>> introduce trainLinearRegression/LogisticRegression/Kmeans which does a
>>> similar thing as in createLinearRegression in those time series functions.
>>> In the processData method you can use Spark mllib classes to actually train
>>> models and return the model weights, evaluation metrics. So, converting
>>> streams into RDDs and retrieving information from the trained models shall
>>> happen in this method.
>>>
>>> In the stream processor extension example, you can retrieve those values
>>> then use them to train new models with new batches. Weights/cluster centers
>>> maybe passed as initialization parameters for the wrappers.
>>>
>>> Please note that we have to figure out the best siddhi extension type
>>> for this process. In the siddhi query, we define batch size, type of
>>> algorithm and number of features (there can be more). After batch size
>>> number of events received, train a model and save parameters, return
>>> evaluation metric. With the next batch, retrain the model initialized with
>>> previously learned parameters.
>>>
>>> We also may need to test the same scenario with a moving window, but I
>>> suspect that that approach may become so slow as a model is trained each
>>> time an event is received. So, we may have to change the number of slots
>>> the moving window moves at a time (eg: not one by one, but ten by ten).
>>>
>>> Once this is resolved, majority of the research part will be finished
>>> and all we will be left to do is implementing wrappers around the 3
>>> learning algorithms we consider.
>>>
>>> Best regards.
>>>
>>> [1]
>>> https://github.com/wso2/siddhi/blob/master/modules/siddhi-extensions/timeseries/src/main/java/org/wso2/siddhi/extension/timeseries/linreg/RegressionCalculator.java
>>> [2]
>>> https://github.com/wso2/siddhi/blob/master/modules/siddhi-extensions/timeseries/src/main/java/org/wso2/siddhi/extension/timeseries/linreg/SimpleLinearRegressionCalculator.java
>>>
>>>
>>> On Sat, May 21, 2016 at 2:55 PM, Mahesh Dananjaya <
>>> dananjayamah...@gmail.com> wrote:
>>>
 Hi Maheshkya,
 shall we use [1] for our work? i am checking the possibility.
 BR,
 Mahesh.
 [1]
 https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+E

[Dev] [Vote] Release WSO2 Carbon Kernel 5.1.0 RC1

2016-05-27 Thread Niranjan Karunanandham

Hi Devs,

This is the 1st Release Candidate of WSO2 Carbon Kernel 5.1.0

This release fixed the following issues:
https://wso2.org/jira/issues/?filter=13077

Please download and test your products with Kernel 5.1.0 RC1 and vote.

*Source and binary distribution files:*
https://github.com/wso2/carbon-kernel/releases/download/v5.1.0-rc1/wso2carbon-kernel-5.1.0.zip

*Maven Staging repository:*
https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1020/

*The tag to be voted upon:*
https://github.com/wso2/carbon-kernel/releases/tag/v5.1.0-rc1

[ ] Broken - do not releaes (explain why)
[ ] Stable - go ahead and release

Thank you,
Carbon Team

-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 5 Beta - Shared subscriber doesn't connect

Re: [Dev] [GSOC 16] Initial Project Progress

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] Invalid Query error in AnalyticsDataAPI

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Dev] [DEV] WSO2 Dashboard Server 2.1.0-M2 Released!

Re: [Dev] [GSOC 16] Initial Project Progress

[Dev] WSO2 App Manager 1.2.0-ALPHA Released!

[Dev] APIM 2.0.0-SNAPSHOT Nightly build - 27/05/2016

Re: [Dev] Invalid Query error in AnalyticsDataAPI

Re: [Dev] What is the Jira project for "carbon-gateway-framework"

Re: [Dev] Invalid Query error in AnalyticsDataAPI

Re: [Dev] Missing required capability in osgi component

[Dev] ESB 5 Beta - Shared subscriber doesn't connect

Re: [Dev] Missing required capability in osgi component

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 5.1.0 RC1

Re: [Dev] Missing required capability in osgi component

[Dev] Invalid Query error in AnalyticsDataAPI

Re: [Dev] [GSoC 2016]Proposal 03: [ML]Visual(Deep) Neural Network Builder -Project Progress

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 5.1.0 RC1

Re: [Dev] Missing required capability in osgi component

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

Re: [Dev] Missing required capability in osgi component

Re: [Dev] Missing required capability in osgi component

Re: [Dev] Fwd: GSOC2016: [ML][CEP] Predictive analytic with online data for WSO2 Machine Learner

[Dev] [Vote] Release WSO2 Carbon Kernel 5.1.0 RC1

28 matches

Site Navigation

Mail list logo

Footer information