Re: [Dev] [MySql5.7] Concern about MySql 5.7 scripts running with -Dsetup

[Nirmal Fernando]

Hi,

On Fri, Jul 22, 2016 at 2:19 PM, Kishanthan Thangarajah  wrote:

> "-Dsetup" is a development time option and in production it is not used
> mostly. Users manually populate the DB's using relevant scripts by
> executing them separately. Due to this fact only, we did not invest time in
> supporting mysql 5.7 with "-Dsetup" option. We have documented this also :
> https://docs.wso2.com/display/ADMIN447/Setting+up+MySQL
>

I don't see that we have explained this in the doc. Rather it says
following;

If you have installed MySQL version 5.7, execute the mysql5.7.sql as shown
below.

   1.

   Make a backup of the existing mysql.sql file and call it mysqlbackup.sql.
   2.

   Now, rename the existing mysql5.7.sql file to mysql.sql.
   3.

   Execute the product startup script using the -Dsetup parameter as
   follows:



>
> We cannot remove this option from 4.4.x kernel as we do only patch
> releases on top of it.
>
> On Wed, Jul 13, 2016 at 11:42 AM, Pubudu Priyashan 
> wrote:
>
>> +1 to Nuwan's suggestion.
>>
>> I too have experienced inconsistencies in the past while using the
>> -Dsetup when configuring the databases where we still have to manually
>> execute the scripts. Since we are not using this feature in production
>> environments I think it wouldn't hurt to get rid of this all together.
>> Since we can always run the relevant scripts manually, if there is no
>> significant advantage of keeping this feature I think it's a good idea to
>> remove it. Just my personal opinion.
>>
>> Cheers,
>> Pubudu.
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>> On Wed, Jul 13, 2016 at 11:35 AM, Nuwan Dias  wrote:
>>
>>> Practically the -Dsetup option is never used in production. All "real"
>>> users of our products have DB admins and all that who carefully evaluate
>>> and execute our DB scripts on their Database servers. They would never
>>> allow a product startup process to create tables and indexes at will on
>>> their database servers.
>>>
>>> So I think we should just remove this option all together. I know we've
>>> done that on C5 but it probably makes sense to remove this option in C4
>>> products as well. We sometimes even have to make design changes to our
>>> features to support this option (when two features have their own DB
>>> scripts). And I think its a complete waste because we're compromising the
>>> design of our products to support a feature thats never used in the real
>>> world.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Wed, Jul 13, 2016 at 11:05 AM, Pubudu Priyashan 
>>> wrote:
>>>

 Hi all,

 When we use MySql 5.7 as the DB and start the server with -Dsetup
 without manually executing the scripts at DB level, we have observed the
 issue logged at [1] while testing wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack.
 The reason behind this is, by default the pack is picking up mysql.sql
 script located at [$HOME]/dbscripts directory when started with -Dsetup. A
 solution was suggested in this comment [2] to rename the mysql5.7.sql
 scripts as mysql.sql when using MySql 5.7 db and we have verified that this
 suggestion fixed the issue. We have logged a doc JIRA to include that
 information at [3] for now.

 Our concern is since this is going to affect all the products when
 using MySql5.7 do we have a better solution to automatically select the
 mysql version without having to rename the script? Is it possible to add a
 property to define the db version somewhere and then point to the relevant
 script without renaming the script when starting with -Dsetup? Or any
 better solution if possible. Appreciate your feedback on this. Thanks!


 [1] https://wso2.org/jira/browse/ESBJAVA-4748
 [2]
 https://wso2.org/jira/browse/ESBJAVA-4748?focusedCommentId=123463=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-123463
 [3] https://wso2.org/jira/browse/DOCUMENTATION-3604


 Cheers,
 Pubudu D.P
 Senior Software Engineer - QA Team | WSO2 inc.
 Mobile : +94775464547

 Linkedin: https://uk.linkedin.com/in/pubududp
 Medium: https://medium.com/@pubududp


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


>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan 

Re: [Dev] Improve startup time in AS 6.0.0

[Lakshman Udayakantha]

[+dev]

On Sat, Jul 23, 2016 at 8:17 PM, Lakshman Udayakantha 
wrote:

> I copied all the jars in lib in AS 6.0.0 to a pure tomcat and I could see
> 40(s) startup time there also. According to the jprofiler also most of the
> time is going for jar scanning. So I added additional jars in AS than
> tomcat to the tomcat.util.scan.StandardJarScanFilter.jarsToSkip section in
> catalina.properties file because we don't want to scan them for
> configurations. After adding them I could reduce uptime to 2.5 seconds. I
> think we can go with this in next milestone. WDYT?
>
> Thanks
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0717429601*
>
>


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0717429601*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error with Secured/Encrypted VFS Transport Credentials on ESB500Beta2

[Chaminda Jayawardena]

Hi Rajith,

I used a new keystore with 2048 of key size. And other configurations are
as below. So then the problem is key size accoring to that.

--encrypted "user:pass" as a whole
--have provided decryption in axis2.xml

On Fri, Jul 22, 2016 at 8:11 PM, Rajith Vitharana  wrote:

> Hi Chaminda,
>
> Config level issues I can think of are as follows,
> Have you encrypted "username:password" as a whole and provided in [1] or
> separately encrypted them and added as colon separated value?
> Have you provided same configs for decryption in axis2.xml
> vfsTransportListner config? (For example if you use bouncycastle(BC) when
> encrypting, then need to provide that for decryption as well)
> Have you used a key with larger keystrength for encryption? (for example
> 2048 key strength). If so there was a issue with that and already fixed
> with [2]
>
>
> [1] - {wso2:vault-decrypt('encryptedValue')}
> [2] - https://wso2.org/jira/browse/ESBJAVA-4770
>
> Thanks,
>
> On Fri, Jul 22, 2016 at 2:59 PM, Chaminda Jayawardena 
> wrote:
>
>> Hi,
>>
>> I followed the steps in [1] and getting below exception[2] when proxy
>> service is invoked.
>> I manually encrypted the username:password using ciphertool.sh and used
>> encrypted value in the proxy service as below. And also I could success
>> when the same user:pass combination is not encrypted.
>> Anything missed here or just a bug ?
>>
>> *> name="transport.vfs.FileURI">smb://{wso2:vault-decrypt('encrypted_user:pass_from_ciphertool')}@localhost/share/test1*
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-4679
>> [2]
>> [2016-07-22 14:48:11,221] ERROR - VFSTransportListener Error checking for
>> existence and readability : smb://@localhost/share/test1
>> org.apache.commons.vfs2.FileSystemException: Could not determine the type
>> of file "smb://localhost/share/test1".
>> at
>> org.apache.commons.vfs2.provider.AbstractFileObject.attach(AbstractFileObject.java:1523)
>> at
>> org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:490)
>> at
>> org.apache.commons.vfs2.provider.AbstractFileObject.exists(AbstractFileObject.java:478)
>> at
>> org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:294)
>> at
>> org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:188)
>> at
>> org.apache.synapse.transport.vfs.VFSTransportListener.poll(VFSTransportListener.java:134)
>> at
>> org.apache.axis2.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:67)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: jcifs.smb.SmbAuthException: Logon failure: unknown user name
>> or bad password.
>> at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:406)
>> at jcifs.smb.SmbSession.send(SmbSession.java:218)
>> at jcifs.smb.SmbTree.treeConnect(SmbTree.java:176)
>> at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
>> at jcifs.smb.SmbFile.connect(SmbFile.java:954)
>> at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
>> at jcifs.smb.SmbFile.queryPath(SmbFile.java:1335)
>> at jcifs.smb.SmbFile.exists(SmbFile.java:1417)
>> at jcifs.smb.SmbFile.isDirectory(SmbFile.java:1490)
>> at
>> org.apache.commons.vfs2.provider.smb.SmbFileObject.createSmbFile(SmbFileObject.java:119)
>> at
>> org.apache.commons.vfs2.provider.smb.SmbFileObject.doAttach(SmbFileObject.java:71)
>> at
>> org.apache.commons.vfs2.provider.AbstractFileObject.attach(AbstractFileObject.java:1506)
>> ... 10 more
>>
>>
>>
>>
>> --
>> Thanks & Regards
>>
>> *Chaminda Jayawardena*
>> Senior Software Engineer - QA
>> WSO2 Inc. - http://wso2.com
>> +94-77-7725234
>>
>
>
>
> --
> Rajith Vitharana
>
> Senior Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94715883223
> Blog : http://lankavitharana.blogspot.com/
> 
>



-- 
Thanks & Regards

*Chaminda Jayawardena*
Senior Software Engineer - QA
WSO2 Inc. - http://wso2.com
+94-77-7725234
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC Project: HTTP Load Balancer On Top Of WSO2 Gateway Discussion

[Kasun Indrasiri]

Hi Venkat,

Scheduled a meeting on Monday.

On Sat, Jul 23, 2016 at 5:06 AM, Venkat Raman  wrote:

> I missed to mention about test environment.
>
> OS Ubuntu 16.04 64 bit - VM
> 4 GB RAM, 4 Cores
>
> Host Machine is Macbook Pro 16GB RAM
>
> Also kindly find the attached ApacheBench results too.
>
>
>
>
>
> *Venkat.*
>
> On Sat, Jul 23, 2016 at 5:06 PM, Venkat Raman 
> wrote:
>
>> Hi All,
>>
>> I've customized perf-benchmark scripts for our LB.  Kindly find it here.
>> 
>>
>> You can also find Nginx config that I used for this bench-marking here.
>> 
>>
>> I've also attached preliminary test results.  Kindly have a look at it.
>>
>> @IsuruR - We should have a discussion/code review ASAP.  You can see that
>> test results are good and promising, but it can be improvised.  Kindly note
>> that we have only few weeks left.  I understand that you are very busy, but
>> kindly do allocate little time for this also Isuru.
>>
>> Once we do our code review, with Samiyuru's guidance I'll do memory test
>> also. If you are free we can do it today or tomorrow.
>>
>> @Kasun - If you are free we can have demo today / tomorrow.
>>
>>
>> Will be looking forward to hear from you.
>>
>>
>>
>> *Thanks,*
>> *Venkat.*
>>
>> On Thu, Jul 21, 2016 at 11:13 AM, Venkat Raman 
>> wrote:
>>
>>> Hi IsuruP and Samiyuru,
>>>
>>> Good morning.  Kindly find the project here.
>>> 
>>>
>>> I also gave a demo to IsuruR and he is happy with the features
>>> implemented so far.
>>>
>>> Now we are in performance testing phase.  We need to do performance
>>> bench-marking similar to that of MSF4J.  For the project scope we have
>>> planned to compare with Nginx.
>>>
>>> Yesterday I tested Nginx and our LB with 1,000,000 requests and 10,000
>>> concurrency.  Performance was close.  Test was done with apache benchmark
>>> on Ubuntu 64 bit VM with 8 GB RAM and 3 CPU cores. I used VMware Fusion as
>>> Hypervisor. Host machine is MacBook pro 16GB.
>>>
>>> I also tried MSF4J bench-marking scripts.  We need to do a similar
>>> comparison between Nginx and our LB.  It would be great if you could help
>>> and guide me through it.
>>>
>>> Looking forward to hear from you.
>>>
>>>
>>>
>>> *Thanks,*
>>> *Venkat.*
>>>
>>> On Thu, Jul 21, 2016 at 9:43 AM, Venkat Raman 
>>> wrote:
>>>
 Hi Isuru,

 Good morning.  Yesterday I tested Nginx and our LB with 1,000,000
 requests and 10,000 concurrency.  Performance was close.

 As you suggested I tried MSF4J's perf benchmark.  I'm working
 customizing that script to test our LB.




 *Thanks,*
 *Venkat.*

 On Mon, Jul 18, 2016 at 9:16 AM, Venkat Raman 
 wrote:

> Hi Isuru,
>
> Good morning.  Please find 8th week's progress.
>
> 1) Removed SSL related config from LB as it is abstracted at
> gateway-framework level.
> 2) Added groups support as we discussed.  Now, LB will support
> multiple groups in a single .iflow file  (Designing and implementing this
> without   affecting any of the existing functionality took few days).
>
> *Thanks,*
> *Venkat.*
> Hi Isuru,
>
> Can we do review by 10 PM ..?
>
>
>
>
> *Thanks,*
> *Venkat.*
>
> On Mon, Jul 11, 2016 at 10:52 PM, Venkat Raman 
> wrote:
>
>> Hi Isuru,
>>
>> Thanks for your time.  From today's discussion :
>>
>> 1) Remove SSL related config from LB level, as it is completely
>> dependent on transports level (carbon-transports).  LB sees as Inbound 
>> and
>> Outbound endpoints.  It is abstracted at gateway-framework level.
>>
>> 2) Add endpoints parameter to LB so that we can load balance multiple
>> groups specified in a single .iflow file.
>>
>> 3) Do Performance benchmark similar to MSF4J.
>>
>> 4) Transports statistics can be added at LB level, if needed.
>>
>> Will be looking forward for tomorrow's demo with Kasun. :)
>>
>>
>> *Thanks,*
>> *Venkat.*
>>
>> On Mon, Jul 11, 2016 at 7:46 AM, Venkat Raman 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Good morning. Please find 7th week's progress.
>>>
>>> 1) Code Optimization - I've done some refactoring and optimization.
>>> 2) Though SSL support is not added in gateway-framework, I figured a
>>> work around and checked whether SSL offload and end to end encryption is
>>> working or not.. It is working fine. Once it is available in
>>> gateway-framework github, I'll take that.
>>> 3) Added statistics support and removed 

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Asantha Thilina]

Hi Tharindu,

here i added all the commitments to spread sheet[1] and also i updated my
blog with about java document api[2] and also i added findbug report[3] and
also i updated my blog with the code quality analysis process i have done[4]

[1]
https://docs.google.com/spreadsheets/d/1jwSR_qFV-LfOS7ZTZ8CpiFFTYPoudDQF7zQhvblivaE/edit?usp=sharing
[2]
http://asanthamax.blogspot.com/2016/07/mongodb-user-store-package-hierarchy.html
[3]https://googledrive.com/host/0B__ZE1ru1jkXZFdES3BOaHVyZ3M/
[4]
http://asanthamax.blogspot.com/2016/07/findbugs-in-mongodbuserstoremanager-in.html

Thanks,
Asantha

On Fri, Jul 22, 2016 at 8:45 AM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> I have created the API documentation and hosted in my google drive[1] i
> will be preparing code inspection report as well will share it as soon as
> well i also added github page also to the userstore script in here[2] as
> well
> [1] http://googledrive.com/host/0B__ZE1ru1jkXbDVoSDlveV9yNk0
> [2] https://asanthamax.github.io/mongodbuserstore/
>
> Thanks,
> Asantha
>
> On Tue, Jul 12, 2016 at 11:59 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>> sure we will arrange a hangout on next week and sure i will refer the
>> link and do the necessary inspect in my code for any security
>> vulnerabilities and update you sooner
>>
>> Thanks,
>> Asantha
>>
>> On Tue, Jul 12, 2016 at 9:56 AM, Tharindu Edirisinghe > > wrote:
>>
>>> Hi Asantha,
>>>
>>> Thanks for the update. I'm out of the country this week and won't be
>>> available. Let's have a hangout next week and discuss the final steps of
>>> the project.
>>>
>>> Along with find bugs, if you haven't enabled findsecuritybugs plugin,
>>> you can refer [1] and check if any security weaknesses are there in the
>>> code.
>>>
>>> [1]
>>> http://tharindue.blogspot.in/2016/06/static-code-analysis-for-java-using.html
>>>
>>> Thanks,
>>> TharinduE
>>>
>>> On Tue, Jul 12, 2016 at 5:32 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,
 I have clean up the code according to find bug plugin and also for
 rollback purposes since it only concern when modifying or adding new user
 or role to user store i have manually added rollback option where if error
 occured all the changes done to db in code segment will be discard from db
 i updated the my repository with recent changes[1] now i preparing the
 documentation and test scripts.

 [1] https://github.com/asanthamax/mongodbuserstore

 Thanks,
 Asantha

 On Mon, Jul 4, 2016 at 2:54 AM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> thanks for the reply ,sure i will try out that and update the progress
> as soon as possible
>
> Thanks,
> Asantha
>
> On Mon, Jul 4, 2016 at 1:38 AM, Tharindu Edirisinghe <
> tharin...@wso2.com> wrote:
>
>> Hi Asantha,
>>
>> While you are adding the roll back transaction capability, also look
>> into testing a high load and try to generate database level exceptions.
>> Once thing you can try out is writing a client for performing userstore
>> manager operations such as add user, add role, login, logout etc. and 
>> play
>> it with a high concurrency using Jmeter. Then we should be able to get a
>> better understanding of transaction management with respective to 
>> MongoDB.
>>
>> Regards,
>> TharinduE
>>
>> On Mon, Jul 4, 2016 at 10:57 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> i will be trying for implement roll back transactions capability in
>>> MongoDB to add to MongoDB User Store[2] i found that MongoDB use a 
>>> concept
>>> call two phase commit[1] i trying to implement that inside my code but 
>>> it
>>> seems to be little complex and i think it may arise performance issue 
>>> when
>>> adding high load of dataset at once is there any other better method i 
>>> can
>>> achieve this task? any advices would be grateful
>>>
>>> [1]
>>> https://docs.mongodb.com/manual/tutorial/perform-two-phase-commits/
>>> [2] https://github.com/asanthamax/mongodbuserstore
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Wed, Jun 29, 2016 at 2:55 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 I have finished and added delete functions also to users ,roles and
 user claim deletions to my repo[1]

 [1] https://github.com/asanthamax/mongodbuserstore

 Thanks,
 Asantha

 On Mon, Jun 27, 2016 at 4:18 AM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi aiya,
>
> i have small problem in my research, i will be developing
> convolution neural network using 

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Anuruddha Liyanarachchi]

Hi Akila,

Thanks for pointing out, I have fixed the mater branch pom versions with
commit [1].

[1]
https://github.com/wso2/dockerfiles/commit/0cd9b7ae445fdd5ce8754e28352e28b30106401f

On Sat, Jul 23, 2016 at 11:59 AM, Akila Ravihansa Perera  wrote:

> Hi Anuruddha,
>
> The pom version in master branch should always be a SNAPSHOT version [1].
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
>> release.
>>
>> *This release fixes the following issues:*
>>
>> https://wso2.org/jira/issues/?filter=13159
>>
>> *Tag to be voted upon:*
>>
>> https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1
>>
>> *Source and distribution packages:*
>>
>> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1
>>
>> Please download, test, and vote. The README file under the distribution
>> contains guide and instructions on how to try it out locally.
>>
>> [+] Stable - Go ahead and release
>>
>> [-] Broken - Do not release (explain why)
>>
>>
>>
>> This vote will be open for 72 hours or as needed.
>>
>> Regards,
>> WSO2 PaaS team
>>
>>
>> ___
>> 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
>



-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] DAS 3.0.1 - Empty Dashboard for Smart Home Sample

[Reza Ameri]

Here is my problem,
I have done what [1] said and the problem did not happen again on DAS
dashboard *BUT *when I want to connect to DAS from API Manager I got some
error on "admin-dashboard" in the "Configure Analytics" menu. I couldn't
save the config and I got an error like this on AM:

Error occurred while deploying artifacts (Cause:org.apache.axis2.AxisFault:
Connection has been shutdown: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target.

I have no error on DAS dashboard but I can not connect AM to DAS. Any Idea?

P.S.: I have asked this question on stackoverflow[2] too, feel free to
answer any where ;-)



[1].
http://udarakr.blogspot.com/2014/04/you-may-get-following-error-and-your.html
[2].
http://stackoverflow.com/questions/38540169/ssl-error-on-wso2-data-analytics-server

On Fri, May 13, 2016 at 10:28 AM, Gobinath Loganathan 
wrote:

> Hi all,
> Thank you for your support. Now it is working as expected after creating
> and importing a new certificate for my IP.
>
> Thanks a lot.
>
> On Fri, May 13, 2016 at 11:11 AM, Rukshani Weerasinha 
> wrote:
>
>> Hi all,
>>
>> I will update this thread as well as the Jira issue [1] once the DAS
>> Quick Start Guide is updated with the relevant information.
>>
>> [1] DOCUMENTATION-3344 
>>
>> Best Regards,
>> Rukshani.
>>
>> On Fri, May 13, 2016 at 10:59 AM, Nipuna Chandradasa 
>> wrote:
>>
>>> Hi All,
>>>
>>> Dashboard Server team have given few patches to solve gadget loading
>>> related issues happening in a real production environment where we don't
>>> use localhost. Those issues are mentioned in the mail thread i mentioned in
>>> the previous mail.
>>>
>>> Thank you,
>>>
>>> On Fri, May 13, 2016 at 10:54 AM, Iranga Muthuthanthri 
>>> wrote:
>>>
 Think we need to have a note on the above in the QSG

 On Fri, May 13, 2016 at 10:51 AM, Nipuna Chandradasa 
 wrote:

> Hi Gobinath,
>
> Here what you have to do is to create a new certificate for your IP
> and import it in to wso2carbon.jks and clienttruststore.jks.
> Refer to this blog[1] for more details.
>
> [1].
> http://udarakr.blogspot.com/2014/04/you-may-get-following-error-and-your.html
>
> Regards,
> Marcus
>
> On Fri, May 13, 2016 at 10:46 AM, Gobinath Loganathan <
> gobin...@wso2.com> wrote:
>
>> Hi Nipuna,
>> I got the same error. Thank you for your help, I will have a look.
>>
>> For reference, I have added my console error message here:
>> [2016-05-13 10:37:08,655] ERROR
>> {org.apache.shindig.gadgets.render.DefaultServiceFetcher} -  Services
>> methods from the https://10.100.7.87:9443/shindig/rpc endpoint could
>> not be fetched. The following error occurred: javax.net.ssl.SSLException:
>> hostname in certificate didn't match: <10.100.7.87> != .
>> [2016-05-13 10:37:09,026]  INFO
>> {org.apache.shindig.gadgets.http.BasicHttpFetcher} -  The following
>> exception occurred when fetching
>> https://10.100.7.87:9443/portal/store/carbon.super/gadget/Peak_Usage_Range_-_Seattle/index.xml:
>> 8 ms elapsed.
>> [2016-05-13 10:37:09,027]  INFO
>> {org.apache.shindig.gadgets.http.BasicHttpFetcher} -
>> javax.net.ssl.SSLException: hostname in certificate didn't match:
>> <10.100.7.87> != 
>> at
>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:238)
>> at
>> org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54)
>> ...
>>
>>
>> Thanks.
>>
>> On Fri, May 13, 2016 at 10:34 AM, Nipuna Chandradasa <
>> nipu...@wso2.com> wrote:
>>
>>> Hi Gobinath,
>>>
>>> Is there any error on the console or the debug tool of the browser
>>> saying IP !=  ?
>>> This is not because of you don't have data. Here gadgets are not
>>> even rendered. This can be because of a SSLException (Your certificate
>>> doesn't match your host) or if you have a LB in front your DAS with 
>>> proxy
>>> port configured, shindig uses server port to render not the proxy 
>>> port...
>>> so 404 error..
>>>
>>> Please have a look at mail tread mention here which is in support.
>>>
>>>  [DAS] Hostname issue while adding gadgets to dashboard when
>>> fronted by an LB
>>>
>>>  Regards,
>>>
>>>
>>> On Fri, May 13, 2016 at 10:15 AM, Gobinath Loganathan <
>>> gobin...@wso2.com> wrote:
>>>
 Hi Thanuja,
 I also think so. Even I executed the 'smart_home_script' manually,
 but no luck.

 Thanks.

 On Fri, May 13, 2016 at 10:13 AM, 

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.2.0 RC1

[Akila Ravihansa Perera]

Hi Anuruddha,

The pom version in master branch should always be a SNAPSHOT version [1].

Thanks.

On Fri, Jul 22, 2016 at 9:27 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Devs,
>
> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.2.0
> release.
>
> *This release fixes the following issues:*
>
> https://wso2.org/jira/issues/?filter=13159
>
> *Tag to be voted upon:*
>
> https://github.com/wso2/dockerfiles/tree/v1.2.0-rc1
>
> *Source and distribution packages:*
>
> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0-rc1
>
> Please download, test, and vote. The README file under the distribution
> contains guide and instructions on how to try it out locally.
>
> [+] Stable - Go ahead and release
>
> [-] Broken - Do not release (explain why)
>
>
>
> This vote will be open for 72 hours or as needed.
>
> Regards,
> WSO2 PaaS team
>
>
> ___
> 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] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC1

[Akila Ravihansa Perera]

Hi Pubudu,

The pom version in master branch should always be a SNAPSHOT version [1].

[1] https://github.com/wso2/puppet-modules/blob/master/pom.xml#L24

Thanks.

On Fri, Jul 22, 2016 at 10:04 PM, Pubudu Gunatilaka 
wrote:

> Hi Devs,
>
> This is the first release candidate (RC1) of WSO2 Puppet Modules 2.1.0
> release. Please download, verify, and vote. Voting will be open for 72
> hours or as needed.
>
> This release fixes following issues:
>
> https://wso2.org/jira/browse/PMODULES-16?filter=13155
>
> ​Source and binary distribution files:
>
> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1
>
> The tag to be voted upon:
>
> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1
>
> Release verification guide:
>
> https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment
>
> Refer modules README files for more details.
>
> Please vote as follows.
>
> [+] Stable - go ahead and release
>
> [-]  Broken - do not release (please explain why)
>
> Thank you,
> WSO2 PaaS Team.
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> 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