date:20160116

Re: [Dev] [DEV][VOTE] Release WSO2 Data Analytics Server 3.0.1 RC1

2016-01-16 Thread Sachith Withana

We called off the vote due to the reason mentioned by Gimantha.


Thanks,
Sachith.

On Thu, Jan 14, 2016 at 10:29 PM, Gimantha Bandara 
wrote:

> -1 Please do not release. There is a performance issue in Javascript APIs.
> It takes more than 1000 milliseconds to retrieve records, where it only
> takes 50 milliseconds to get the same records using REST APIs. I have
> created the jira [1] to track the progress.
>
> [1] https://wso2.org/jira/browse/DAS-355
>
> On Thu, Jan 14, 2016 at 6:24 PM, Gihan Anuruddha  wrote:
>
>> Tested below functionalities in a standalone pack.
>>
>>- Data Explorer
>>   - Index search
>>   - Primary key search
>>   - Facet search
>>   - Date range search
>>- Spark notification sending
>>
>> My vote is [x] Stable - Go ahead and release
>>
>> Regards,
>> Gihan
>>
>> On Thu, Jan 14, 2016 at 5:53 PM, Dunith Dhanushka 
>> wrote:
>>
>>> Tested below areas in a standalone pack.
>>>
>>> - Samples
>>>   - Smart home
>>>   - HTTPD Logs
>>>
>>> - CApp deployment
>>> - Stream persistence
>>> - Analytic Dashboard
>>> - Gadget generation
>>>
>>> So my vote is [x] Stable - Go ahead and release
>>>
>>>
>>> Thanks,
>>> Dunith
>>>
>>> On Thu, Jan 14, 2016 at 5:46 PM, Seshika Fernando 
>>> wrote:
>>>
 Hi,

 I've tested DAS 3.0.1 RC1 with complex execution plans that test event
 tables, indexing, patterns, windows, joins etc; I've also tested data
 persistence, event tracing, data explorer, event publisher, stream
 simulation.

 All works well.

 My vote - [x] Stable - Go ahead and release.

 seshi

 On Thu, Jan 14, 2016 at 4:15 PM, Sachith Withana 
 wrote:

> Hi all,
>
> This is the first release candidate of WSO2 DAS 3.0.1. Please
> download, test and vote.
>
> The vote will be open for 72 hours or as needed.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12622
>
> Binary distribution file:
> https://svn.wso2.org/repos/wso2/people/sachith/rc1/
>
> [ ] Broken - Do not release (explain why)
> [ ] Stable - Go ahead and release
>
>
> Thanks,
> WSO2 DAS Team.
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

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


>>>
>>>
>>> --
>>> Regards,
>>>
>>> Dunith Dhanushka,
>>> Senior Software Engineer
>>> WSO2 Inc,
>>>
>>> Mobile - +94 71 8615744
>>> Blog - dunithd.wordpress.com 
>>> Twitter - @dunithd 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> W.G. Gihan Anuruddha
>> Senior Software Engineer | WSO2, Inc.
>> M: +94772272595
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Gimantha Bandara
> Software Engineer
> WSO2. Inc : http://wso2.com
> Mobile : +94714961919
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: https://lk.linkedin.com/in/sachithwithana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] puppet modules - validating yaml files

2016-01-16 Thread Pubudu Fernando

Hi,

I make use of [1] in Atom for catching and fixing syntax errors in Puppet
modules. Works in the terminal too. Source code is available on Github.
Maybe this can be adapted for use, if incorporating validation to the
project itself?

[1] - https://atom.io/packages/linter-puppet-lint

*Pubudu Fernando*
Software Engineering Intern
WSO2 Inc.
mobile: +94 77 888 2543
blog: http://blog.pubudu.xyz


On Sun, Jan 17, 2016 at 2:26 AM, Sajith Kariyawasam  wrote:

> well, ideally we should validate all the puppet modules too (*.pp files)
> for syntax errors, at the time of packaging the modules.
>
> On Sun, Jan 17, 2016 at 2:24 AM, Sajith Kariyawasam 
> wrote:
>
>> Hi Devs,
>>
>> While implementing puppet modules in [1] I came across with syntax errors
>> (using tabs, missing semicolons etc) in yaml files and which was detected
>> only at the puppet runtime.
>> True that some editors do syntax validation, but there could be
>> situations developers use simple editors. IMO its good if we can provide
>> yaml validation into the project itself, which would
>> make sure there are no yaml syntax errors. For now, I wrote a simple ruby
>> script[2] to validate this and were able to find one issue in a yaml file
>> :)
>> May be we could incorporate this into the maven build file? WDYT?
>>
>> [1] https://github.com/wso2/puppet-modules
>> [2]
>> =
>> begin
>>   require 'yaml'
>>
>>   Dir.glob('**/*.yaml') do |rb_file|
>> YAML.load_file("#{rb_file}")
>>   end
>>
>> rescue => e
>>   puts "Error during processing: #{$!}"
>> end
>> =
>>
>> Thanks,
>> Sajith
>>
>> --
>> Sajith Kariyawasam
>> *Committer and PMC member, Apache Stratos, *
>> *WSO2 Inc.; http://wso2.com *
>> *Mobile: 0772269575*
>>
>
>
>
> --
> Sajith Kariyawasam
> *Committer and PMC member, Apache Stratos, *
> *WSO2 Inc.; http://wso2.com *
> *Mobile: 0772269575*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] puppet modules - validating yaml files

2016-01-16 Thread Sajith Kariyawasam

well, ideally we should validate all the puppet modules too (*.pp files)
for syntax errors, at the time of packaging the modules.

On Sun, Jan 17, 2016 at 2:24 AM, Sajith Kariyawasam  wrote:

> Hi Devs,
>
> While implementing puppet modules in [1] I came across with syntax errors
> (using tabs, missing semicolons etc) in yaml files and which was detected
> only at the puppet runtime.
> True that some editors do syntax validation, but there could be situations
> developers use simple editors. IMO its good if we can provide yaml
> validation into the project itself, which would
> make sure there are no yaml syntax errors. For now, I wrote a simple ruby
> script[2] to validate this and were able to find one issue in a yaml file
> :)
> May be we could incorporate this into the maven build file? WDYT?
>
> [1] https://github.com/wso2/puppet-modules
> [2]
> =
> begin
>   require 'yaml'
>
>   Dir.glob('**/*.yaml') do |rb_file|
> YAML.load_file("#{rb_file}")
>   end
>
> rescue => e
>   puts "Error during processing: #{$!}"
> end
> =
>
> Thanks,
> Sajith
>
> --
> Sajith Kariyawasam
> *Committer and PMC member, Apache Stratos, *
> *WSO2 Inc.; http://wso2.com *
> *Mobile: 0772269575*
>



-- 
Sajith Kariyawasam
*Committer and PMC member, Apache Stratos, *
*WSO2 Inc.; http://wso2.com *
*Mobile: 0772269575*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] puppet modules - validating yaml files

2016-01-16 Thread Sajith Kariyawasam

Hi Devs,

While implementing puppet modules in [1] I came across with syntax errors
(using tabs, missing semicolons etc) in yaml files and which was detected
only at the puppet runtime.
True that some editors do syntax validation, but there could be situations
developers use simple editors. IMO its good if we can provide yaml
validation into the project itself, which would
make sure there are no yaml syntax errors. For now, I wrote a simple ruby
script[2] to validate this and were able to find one issue in a yaml file
:)
May be we could incorporate this into the maven build file? WDYT?

[1] https://github.com/wso2/puppet-modules
[2]
=
begin
  require 'yaml'

  Dir.glob('**/*.yaml') do |rb_file|
YAML.load_file("#{rb_file}")
  end

rescue => e
  puts "Error during processing: #{$!}"
end
=

Thanks,
Sajith

-- 
Sajith Kariyawasam
*Committer and PMC member, Apache Stratos, *
*WSO2 Inc.; http://wso2.com *
*Mobile: 0772269575*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WebSphere MQ: IVTRun.bat -nojndi shows nothing

2016-01-16 Thread Indika Sampath

You have to enable only
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory. It
seems your PROVIDER_URL has issue. Please remove existing folder given for
provider url and create folder like C:/JNDI-Directory. After that change as
PROVIDER_URL=file:/C:/JNDI-Directory.

On Sat, Jan 16, 2016 at 3:08 PM, Indrajith Udayakumara 
wrote:

> Here I followed the same way as in your description
> Should I un-comment all the INITIAL_CONTEXT FACTORIES ?
> Here I did only the highlighted line.
>
>
> 
> After I save this and run *IVTSetup.bat* in administrator mode
> the following message comes, and the problem exists.
>
>
> 
> Thank you
> Indrajith
>
> On Sat, Jan 16, 2016 at 10:46 AM, Indika Sampath  wrote:
>
>> Hi Indrajith,
>>
>> Sometime ago I've configured WSMQ 7.x. Below steps followed up to
>> configure. Please cross check with you setup.
>>
>> 1. Start ‘IBM WebSphere MQ Explorer, create a new queue manager. Make
>> that queue manager as default by clicking the check-box "make this the
>> default queue manager". Leave default values for the other fields.
>> Queue Manager -> New -> Queue Manager
>> Queue manager name: MyQueueMgr
>>
>> 2. Select the created Queue manager and expand the list. Create a new
>> local queue. Leave default values for the other fields.
>> Queue -> New -> Local Queue…
>> Name: Queue1
>>
>> 3. Expand Advanced sub tree and add a server-connection channel. Leave
>> default values for the other fields.
>> Channel -> New -> Server-connection Channel…
>> Name: MyChannel
>>
>> LISTENER.TCP will added to the Listeners directory by default.
>>
>> 4. Navigate to [WebSphere MQ Home]\java\bin directory, open
>> 'JMSAdmin.config' file and edit the file as follows:
>> Uncomment the configuration for INITIAL_CONTEXT_FACTORY
>> Ex: INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
>> Point to an empty folder for PROVIDER_URL
>> Ex: PROVIDER_URL=file:/C:/JNDI-Directory
>>
>> 5. Navigate to [WebSphere MQ Home]\java\bin directory, create the default
>> set of JNDI bindings by running the following command in the command prompt.
>> IVTSetup.bat
>>
>> NOTE: Please execute above command in command prompt open by Run as
>> Administrator
>>
>> 6. We have now enabled and verified JNDI support. Let's use the JMSAdmin
>> tool to make some modifications in the JNDI bindings. Navigate to
>> [WebSphere MQ Home]\java\bin from the console and start jmsadmin by running
>> the following command:
>> JMSAdmin.bat
>>
>> Run the following commands:
>> ALTER QCF(ivtQCF) TRANSPORT(CLIENT)
>> ALTER QCF(ivtQCF) QMGR(MyQueueMgr)
>> DEFINE Q(MyQueue) QMGR(MyQueueMgr) QUEUE(Queue1)
>>
>> Run following command to verify configuration.
>> DISPLAY CTX
>>
>> Run following command to quit JMSAdmin.bat
>> END
>>
>> IBM MQ configuration complete.
>>
>> With regard to question you raised about IVTRun.bat (IVT stands for
>> Initial Verification Test as I remember), you cannot just run IVTRun.bat.
>> There are set of flags you have to pass depending on the configuration.
>> WSMQ offer this utility to verify your configuration works fine.
>>
>> You can run IVTRun.bat as below once you done with step 3.
>>
>> IVTRun.bat -nojndi -client -m MyQueueMgr -host localhost -channel
>> MyChannel
>>
>> Cheers!
>>
>> On Sat, Jan 16, 2016 at 10:17 AM, Indrajith Udayakumara <
>> aiukum...@gmail.com> wrote:
>>
>>> After configuring ESB 4.9 with WebSphere MQ  according to the steps here
>>>
>>> https://docs.wso2.com/display/ESB490/Configure+with+IBM+WebSphere+MQ
>>>
>>> the IVRun.bat shows nothing on the command prompt.
>>> (both WSMQ and CMD were run as Administrator)
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Indika Sampath
>> Senior Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Phone: +94 716 424 744
>> Blog: http://indikasampath.blogspot.com/
>>
>>
>


-- 
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WebSphere MQ: IVTRun.bat -nojndi shows nothing

2016-01-16 Thread Indrajith Udayakumara

Here I followed the same way as in your description
Should I un-comment all the INITIAL_CONTEXT FACTORIES ?
Here I did only the highlighted line.



After I save this and run *IVTSetup.bat* in administrator mode
the following message comes, and the problem exists.



Thank you
Indrajith

On Sat, Jan 16, 2016 at 10:46 AM, Indika Sampath  wrote:

> Hi Indrajith,
>
> Sometime ago I've configured WSMQ 7.x. Below steps followed up to
> configure. Please cross check with you setup.
>
> 1. Start ‘IBM WebSphere MQ Explorer, create a new queue manager. Make that
> queue manager as default by clicking the check-box "make this the default
> queue manager". Leave default values for the other fields.
> Queue Manager -> New -> Queue Manager
> Queue manager name: MyQueueMgr
>
> 2. Select the created Queue manager and expand the list. Create a new
> local queue. Leave default values for the other fields.
> Queue -> New -> Local Queue…
> Name: Queue1
>
> 3. Expand Advanced sub tree and add a server-connection channel. Leave
> default values for the other fields.
> Channel -> New -> Server-connection Channel…
> Name: MyChannel
>
> LISTENER.TCP will added to the Listeners directory by default.
>
> 4. Navigate to [WebSphere MQ Home]\java\bin directory, open
> 'JMSAdmin.config' file and edit the file as follows:
> Uncomment the configuration for INITIAL_CONTEXT_FACTORY
> Ex: INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
> Point to an empty folder for PROVIDER_URL
> Ex: PROVIDER_URL=file:/C:/JNDI-Directory
>
> 5. Navigate to [WebSphere MQ Home]\java\bin directory, create the default
> set of JNDI bindings by running the following command in the command prompt.
> IVTSetup.bat
>
> NOTE: Please execute above command in command prompt open by Run as
> Administrator
>
> 6. We have now enabled and verified JNDI support. Let's use the JMSAdmin
> tool to make some modifications in the JNDI bindings. Navigate to
> [WebSphere MQ Home]\java\bin from the console and start jmsadmin by running
> the following command:
> JMSAdmin.bat
>
> Run the following commands:
> ALTER QCF(ivtQCF) TRANSPORT(CLIENT)
> ALTER QCF(ivtQCF) QMGR(MyQueueMgr)
> DEFINE Q(MyQueue) QMGR(MyQueueMgr) QUEUE(Queue1)
>
> Run following command to verify configuration.
> DISPLAY CTX
>
> Run following command to quit JMSAdmin.bat
> END
>
> IBM MQ configuration complete.
>
> With regard to question you raised about IVTRun.bat (IVT stands for
> Initial Verification Test as I remember), you cannot just run IVTRun.bat.
> There are set of flags you have to pass depending on the configuration.
> WSMQ offer this utility to verify your configuration works fine.
>
> You can run IVTRun.bat as below once you done with step 3.
>
> IVTRun.bat -nojndi -client -m MyQueueMgr -host localhost -channel MyChannel
>
> Cheers!
>
> On Sat, Jan 16, 2016 at 10:17 AM, Indrajith Udayakumara <
> aiukum...@gmail.com> wrote:
>
>> After configuring ESB 4.9 with WebSphere MQ  according to the steps here
>>
>> https://docs.wso2.com/display/ESB490/Configure+with+IBM+WebSphere+MQ
>>
>> the IVRun.bat shows nothing on the command prompt.
>> (both WSMQ and CMD were run as Administrator)
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Indika Sampath
> Senior Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][VOTE] Release WSO2 Data Analytics Server 3.0.1 RC1

Re: [Dev] puppet modules - validating yaml files

Re: [Dev] puppet modules - validating yaml files

[Dev] puppet modules - validating yaml files

Re: [Dev] WebSphere MQ: IVTRun.bat -nojndi shows nothing

Re: [Dev] WebSphere MQ: IVTRun.bat -nojndi shows nothing

6 matches

Site Navigation

Mail list logo

Footer information