[Dev] Why there are two places to set proxy ports, in catalina-server.xml and axis2.xml?
Hi, When clustering noticed there are two places to set proxy ports. What's the requirement behind this? When I set the proxy ports in catalina-server.xml file - can't directly access the AS instance via 9763, 9444 ports but, in axis2.xml - can access the 9763 and 9444 ports directly. *catalina-server.xml* Connector protocol=org.apache.coyote.http11.Http11NioProtocol port=9763 proxyPort=80 *axis2.xml* transportReceiver name=http class=org.wso2.carbon.core.transports.http.HttpTransportListener !-- Uncomment the following if you are deploying this within an application server. You need to specify the HTTP port of the application server -- parameter name=port9763/parameter !-- Uncomment the following to enable any proxy like Apache2 mod_proxy or any load balancer. The port on the proxy server like Apache is 80 in this case. -- !--parameter name=proxyPort80/parameter-- /transportReceiver Thanks Amalka Amalka Subasinghe WSO2 Inc. Mobile: +94 77 9401267 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why there are two places to set proxy ports, in catalina-server.xml and axis2.xml?
In axis2.xml you would define transports other than servlet transport like passthrough transport. In order to proxy those ports, you need proxy ports in axis2.xml. On Thu, Jun 12, 2014 at 12:22 PM, Amalka Subasinghe ama...@wso2.com wrote: Hi, When clustering noticed there are two places to set proxy ports. What's the requirement behind this? When I set the proxy ports in catalina-server.xml file - can't directly access the AS instance via 9763, 9444 ports but, in axis2.xml - can access the 9763 and 9444 ports directly. *catalina-server.xml* Connector protocol=org.apache.coyote.http11.Http11NioProtocol port=9763 proxyPort=80 *axis2.xml* transportReceiver name=http class=org.wso2.carbon.core.transports.http.HttpTransportListener !-- Uncomment the following if you are deploying this within an application server. You need to specify the HTTP port of the application server -- parameter name=port9763/parameter !-- Uncomment the following to enable any proxy like Apache2 mod_proxy or any load balancer. The port on the proxy server like Apache is 80 in this case. -- !--parameter name=proxyPort80/parameter-- /transportReceiver Thanks Amalka Amalka Subasinghe WSO2 Inc. Mobile: +94 77 9401267 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Student Introduction, GSoC-2014 project: UI Testing Framework for Developer Studio
Any updates? /Jasintha On Fri, Jun 6, 2014 at 6:48 AM, Jasintha Dasanayake jasin...@wso2.com wrote: HI Nila Hope you have already started coding , So can you please share your source repository location Thanks /Jasintha On Mon, Jun 2, 2014 at 6:14 PM, Nila tharshay...@gmail.com wrote: Hi, As you've asked my hierarchical Task Analysis for the midterm evaluation, I've attached that and also my proposal document. Lemme know the feedback. Regards, Tharshayene Loganathan Undergraduate, Dept. of Computer Science Engineering, IIT,Sri Lanka. On 31 May 2014 09:32, Nila tharshay...@gmail.com wrote: Hi, As we've already discussed over the phone, I'm preparing my hierarchical analysis design so far. And I would like to get an overall mid term evaluation criteria, bench marks,tasks (schedules),objectives (date by), Also I wish if I can get any reference/samples regarding the specified module. Regards, Tharshayene Loganathan Undergraduate, Dept. of Computer Science Engineering, IIT,Sri Lanka. On 23 May 2014 17:32, Nila tharshay...@gmail.com wrote: 1. Proposal 22: Android Display viewer for PDF, Doc, Excel files for WSO2 EMM 2. Proposal 9: Tooling support for Hive Queries in Developer Studio 3. Proposal 15: WS-Security Policy Editor for Developer Studio but I've no idea about these things Hi Jasintha, As we have talked earlier, I've cornered three proposals which are listed above. And my preference is on the first proposal. I’m reading enough sources to collect more details and information on it. Please make sure about my preference and suggest me so. Also make sure of my mentors whom I've to keep in touch. Regards, Tharshayene Loganathan Undergraduate, Dept. of Computer Science Engineering, IIT,Sri Lanka. On 21 May 2014 11:52, Jasintha Dasanayake jasin...@wso2.com wrote: Hi Nilla According to our off-line meeting, you agreed to change the original proposal and select a new project from the our project list , Did you able to find a project , if not, please do so as soon as possible, since GSOC codding already started therefore we have to do it at least before end of this week Thanks and Regards /Jasintha On Tue, May 6, 2014 at 2:08 PM, Nila tharshay...@gmail.com wrote: Hi, I apologize for the delayed response. Last few days and on, I'm under severe medication and cornered with my academic semester's final exams. Despite of that, I'm really glad and excited regarding my selection. I'm expecting to learn a lot via delivering my best and looking forward to work with you. The exams would be over by May 21st, but I try my best to involve in this 'community bonding' and gain guidance from you. Thanks in advance. Regards, Tharshayene Loganathan Undergraduate, Dept. of Computer Science Engineering, IIT,Sri Lanka. On 21 March 2014 23:27, Nila tharshay...@gmail.com wrote: The updated and corrected proposal has been submitted. The Google Document is attached below. Pardon me for requesting suggestions on the very last day. Please provide feedback regarding the proposal which would be very helpful for me the future programs. Did I got all wrong, I really wonder. :( This is my first ever GSoC attempt and a feedback really helps. Thanks in advance. GSoC Proposal 2014: UI Testing Framework for Developer Studio https://docs.google.com/document/d/1ffx6aDJNM0D5HUwgLoVk5jbT8mCi1uIpWGMzy9q14AQ/edit?usp=drive_web Regards, Tharshayene Loganathan Undergraduate, Dept. of Computer Science Engineering, IIT,Sri Lanka. On 21 March 2014 19:34, Nila tharshay...@gmail.com wrote: Hi all, I've shared my proposal with you (can comment). Please provide me your valuable suggestions and corrections so I could further improve and submit by tonight. Thanks in advance. GSoC Proposal 2014: UI Testing Framework for Developer Studio https://docs.google.com/document/d/1ffx6aDJNM0D5HUwgLoVk5jbT8mCi1uIpWGMzy9q14AQ/edit?usp=drive_web Regards, Tharshayene Loganathan Undergraduate, Dept. of Computer Science Engineering, IIT,Sri Lanka. On 21 March 2014 11:30, Nila tharshay...@gmail.com wrote: Krishantha, I've gone through the Robot Framework but I'm afraid that the comprehensive widget support for SWT and GMF is less and it's at its initial stages. As you have mentioned the Robot Framework provides and External Eclipse Library [1] [2], which is based on the SWTBot and it's seems to be a better framework in terms of less manual work once setup, compared to using the SWTBot directly. But under the 'Eclipse Library Limitations' section [3] it's been stated that only the simple and basic SWT widgets are supported for the time being. As the ESB plugin requires GMF Editor Testing, still I'm not completely sure on to what extent the SWTBot itself supports GMF. It seems to be supporting GEF and few popular blog articles state that via the extended GEF support
[Dev] Optimize the configurations in api-manager.xml
Hi All, Most of the time we deploy the AM as a distributed cluster and we can't use thrift for key validations. So our recommendation to use WSClient instead of thrift. Therefore it is better to keep the default configuration with WSClient and disable thrift, using that we can deduce the a configurations step. The advance is configuring the so many instances. KeyValidatorClientType*WSClient*/KeyValidatorClientType ThriftClientPort10397/ThriftClientPort ThriftClientConnectionTimeOut1/ThriftClientConnectionTimeOut ThriftServerPort10397/ThriftServerPort !--ThriftServerHostlocalhost/ThriftServerHost-- EnableThriftServer*false*/EnableThriftServer WDYT ? Thanks. Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Optimize the configurations in api-manager.xml
But normal practice is to have the best possible configuration as the default one. On Thu, Jun 12, 2014 at 7:51 PM, Ajith Vitharana aji...@wso2.com wrote: Hi All, Most of the time we deploy the AM as a distributed cluster and we can't use thrift for key validations. So our recommendation to use WSClient instead of thrift. Therefore it is better to keep the default configuration with WSClient and disable thrift, using that we can deduce the a configurations step. The advance is configuring the so many instances. KeyValidatorClientType*WSClient*/KeyValidatorClientType ThriftClientPort10397/ThriftClientPort ThriftClientConnectionTimeOut1/ThriftClientConnectionTimeOut ThriftServerPort10397/ThriftServerPort !--ThriftServerHostlocalhost/ThriftServerHost-- EnableThriftServer*false*/EnableThriftServer WDYT ? Thanks. Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- /sumedha m: +94 773017743 b : bit.ly/sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Optimize the configurations in api-manager.xml
Hi Sumedha, On Thu, Jun 12, 2014 at 7:53 PM, Sumedha Rubasinghe sume...@wso2.com wrote: But normal practice is to have the best possible configuration as the default one. Why WSClient is not best for default, even we recommended it for production ? Thanks Ajith. On Thu, Jun 12, 2014 at 7:51 PM, Ajith Vitharana aji...@wso2.com wrote: Hi All, Most of the time we deploy the AM as a distributed cluster and we can't use thrift for key validations. So our recommendation to use WSClient instead of thrift. Therefore it is better to keep the default configuration with WSClient and disable thrift, using that we can deduce the a configurations step. The advance is configuring the so many instances. KeyValidatorClientType*WSClient*/KeyValidatorClientType ThriftClientPort10397/ThriftClientPort ThriftClientConnectionTimeOut1/ThriftClientConnectionTimeOut ThriftServerPort10397/ThriftServerPort !--ThriftServerHostlocalhost/ThriftServerHost-- EnableThriftServer*false*/EnableThriftServer WDYT ? Thanks. Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- /sumedha m: +94 773017743 b : bit.ly/sumedha -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Optimize the configurations in api-manager.xml
Hi Ajith, We enabled thrift as default key validation type because it faster than WS client(its fast compare to web service call as data transfer happens on tcp level). Usually default configurations focused on performance and then first time experience(default product without config changes) would be nice. Thanks, sanjeewa. On Thu, Jun 12, 2014 at 7:51 PM, Ajith Vitharana aji...@wso2.com wrote: Hi All, Most of the time we deploy the AM as a distributed cluster and we can't use thrift for key validations. So our recommendation to use WSClient instead of thrift. Therefore it is better to keep the default configuration with WSClient and disable thrift, using that we can deduce the a configurations step. The advance is configuring the so many instances. KeyValidatorClientType*WSClient*/KeyValidatorClientType ThriftClientPort10397/ThriftClientPort ThriftClientConnectionTimeOut1/ThriftClientConnectionTimeOut ThriftServerPort10397/ThriftServerPort !--ThriftServerHostlocalhost/ThriftServerHost-- EnableThriftServer*false*/EnableThriftServer WDYT ? Thanks. Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/ http://sanjeewamalalgoda.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Optimize the configurations in api-manager.xml
We recommend it where network level restrictions are there for Thrift. WSClient only requires HTTP level access, where as for Thrift it's a new port. Thrift, if done correct can reach far more concurrency. On Thu, Jun 12, 2014 at 8:06 PM, Ajith Vitharana aji...@wso2.com wrote: Hi Sumedha, On Thu, Jun 12, 2014 at 7:53 PM, Sumedha Rubasinghe sume...@wso2.com wrote: But normal practice is to have the best possible configuration as the default one. Why WSClient is not best for default, even we recommended it for production ? Thanks Ajith. On Thu, Jun 12, 2014 at 7:51 PM, Ajith Vitharana aji...@wso2.com wrote: Hi All, Most of the time we deploy the AM as a distributed cluster and we can't use thrift for key validations. So our recommendation to use WSClient instead of thrift. Therefore it is better to keep the default configuration with WSClient and disable thrift, using that we can deduce the a configurations step. The advance is configuring the so many instances. KeyValidatorClientType*WSClient*/KeyValidatorClientType ThriftClientPort10397/ThriftClientPort ThriftClientConnectionTimeOut1/ThriftClientConnectionTimeOut ThriftServerPort10397/ThriftServerPort !--ThriftServerHostlocalhost/ThriftServerHost-- EnableThriftServer*false*/EnableThriftServer WDYT ? Thanks. Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- /sumedha m: +94 773017743 b : bit.ly/sumedha -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- /sumedha m: +94 773017743 b : bit.ly/sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] what is the best practise for installing a production instance of a WSO2 product, e.g. ESB?
As per the $subject, what is the best practise? I have seen instructions for extracting the binary [1] and running the startup script [2], but just these steps don't seem robust enough for a production environment. In a production environment, I would expect to see some additional steps: a) create a unix user account and unix group for running the service b) creating init.d scripts for starting the service automatically c) to security harden the service (e.g. replace self signed certificates - which certificates, change default passwords - which user accounts) d) configuring clustering (this seems to be documented [3]) e) configuring a production database credential store (this seems to be documented [4]), or f) configuring a production ldap credential store Have I missed some documentation in the wiki, or are these undocumented steps not normally performed in production environments? I've also seen some puppet scripts [5]. Are these scripts production ready? Many thanks, Chris --- [1] https://docs.wso2.org/display/ESB481/Installing+on+Linux [2] https://docs.wso2.org/display/ESB481/Running+the+Product [3] https://docs.wso2.org/display/ESB481/Clustered+Deployment [4] https://docs.wso2.org/display/ESB481/Working+with+Databases [5] https://github.com/wso2/Puppet/tree/master/modules/esb/4.8.0/esb ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Sohani Weerasinghe
Congrats!.. On Tue, Jun 10, 2014 at 9:49 PM, Susinda Perera susi...@wso2.com wrote: Congratulations On Mon, Jun 2, 2014 at 4:55 PM, Shameera Rathnayaka shame...@wso2.com wrote: On Mon, Jun 2, 2014 at 4:43 PM, Shameera Rathnayaka shame...@wso2.com wrote: Congratulation Shani !!! It should be Sohani, sorry for mistype :) On Mon, Jun 2, 2014 at 3:57 PM, Sohani Weerasinghe soh...@wso2.com wrote: Thank you everyone Thanks, Sohani Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Sun, Jun 1, 2014 at 3:10 PM, Dilini Muthumala dil...@wso2.com wrote: Congrats, Sohani! On Sun, Jun 1, 2014 at 9:31 AM, Rajith Vitharana raji...@wso2.com wrote: congrats!!! On Sat, May 31, 2014 at 8:58 AM, Tania Mahanama ta...@wso2.com wrote: Congrats!! On Sat, May 31, 2014 at 7:58 AM, Thanuja Jayasinghe than...@wso2.com wrote: Congratz!!! On 30 May 2014 17:00, Lali Devamanthri l...@wso2.com wrote: Congratulations On Fri, May 30, 2014 at 11:06 AM, Jasintha Dasanayake jasin...@wso2.com wrote: Hi All, It's my distinct pleasure to welcome Sohani as a WSO2 Committer. Sohani has been a valuable contributor for WSO2 Developer Studio since she joined WSO2. In recognition of her contributions to WSO2, she has been voted as a WSO2 Committer. Sohani, Congratulations and Keep up the good work! Thanks and Regards, /Jasintha -- *Jasintha Dasanayake * *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/ lean . enterprise . middleware* *mobile :- 0711368118 0711368118 * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lali Sudaththa Devamanthri* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 71 895 4922 http://www.wso2.com ___ 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 -- Tania Mahanama Senior Technical Writer Contact: Mob: +94 077 5129270 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dilini Muthumala* Software Engineer, WSO2 Inc. *E-mail :* dil...@wso2.com *Mobile: *+94713 400 029 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.org shame...@apache.org* *phone: +9471 922 1454 %2B9471%20922%201454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.org shame...@apache.org* *phone: +9471 922 1454 %2B9471%20922%201454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Lali Devamanthri
Congrats Lali! On Tue, Jun 10, 2014 at 9:49 PM, Susinda Perera susi...@wso2.com wrote: Congratulations On Sun, Jun 1, 2014 at 9:00 PM, Rajith Vitharana raji...@wso2.com wrote: Congrats..!!! On Sun, Jun 1, 2014 at 3:11 PM, Dilini Muthumala dil...@wso2.com wrote: Congrats!! On Sat, May 31, 2014 at 8:59 AM, Tania Mahanama ta...@wso2.com wrote: Congrats!! On Sat, May 31, 2014 at 8:04 AM, Thanuja Jayasinghe than...@wso2.com wrote: Congratz!!! On 30 May 2014 20:15, Isuruwan Herath isuru...@wso2.com wrote: Congrats Lali!!! On Fri, May 30, 2014 at 7:01 AM, Waruna Jayaweera waru...@wso2.com wrote: Congratzz...:D On Fri, May 30, 2014 at 12:11 PM, Dinesh Bandara dine...@wso2.com wrote: Congratulations ! On Fri, May 30, 2014 at 11:08 AM, Jasintha Dasanayake jasin...@wso2.com wrote: Hi All, It's my distinct pleasure to welcome Lali as a WSO2 Committer. Lali has been a valuable contributor for WSO2 Developer Studio since he joined WSO2. In recognition of his contributions to WSO2, he has been voted as a WSO2 Committer. Lali, Congratulations and Keep up the good work! Thanks and Regards, /Jasintha -- *Jasintha Dasanayake * *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/ lean . enterprise . middleware* *mobile :- 0711368118 0711368118 * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dinesh Bandara* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Waruna Lakshitha Jayaweera Software Engineer WSO2 Inc; http://wso2.com phone: +94713255198 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuruwan Herath Technical Lead Contact: +94 776 273 296 ___ 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 -- Tania Mahanama Senior Technical Writer Contact: Mob: +94 077 5129270 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dilini Muthumala* Software Engineer, WSO2 Inc. *E-mail :* dil...@wso2.com *Mobile: *+94713 400 029 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager 1.7 - Clustering Documentation
Hi, AFAIK you can. Since 1.7 also is under platform 4.2.0 as well this[1] is supposed be the correct doc. @Doc. team, have we updated the doc accordingly ?. thanks, On Wed, Jun 11, 2014 at 7:52 PM, Dakshika Jayathilaka daksh...@wso2.com wrote: Hi, AFAIK API manager 1.7 release under chunk 11(carbon 4.2.0 ). $subject [1] mentioned a note say this doc can applicable only for 1.5 1.6. Is that possible to use this same doc on API Manager 1.7 ? If its possible better to update this page as wel. [1] https://docs.wso2.org/display/CLUSTER420/Clustering+API+Manager Regards, *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Proper Guide on RESTful API designing
I think we really need to push this and get a guideline of best practices for REST APIs. Bunch of products have REST APIs built to the core and I think we had some discussions around focusing API Manger on API Designing as well. +1 to have a guideline of best practices for all our products. Cheers~ On Wed, Jun 11, 2014 at 8:45 PM, Dakshika Jayathilaka daksh...@wso2.com wrote: Hi, Do we have $subject. Are we following any specific set of guidance or Is that ok to go with general best practices. ex: [1 http://www.amazon.com/gp/product/1449310508/] [1] http://www.amazon.com/gp/product/1449310508/ Regards, *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [BAM] Optimizing BAM Mediator Data Publishing Logic
Hi Imesh,
While experiencing this problem, do you remember where the BAM Mediators
were in the mediation flow? Have you kept them after calling send or
before in the mediation flow?
Thanks,
-Ayash
On Thu, Feb 13, 2014 at 2:18 PM, Imesh Gunaratne im...@wso2.com wrote:
s/comapred/compared/g
s/millisecods/milliseconds/g
On Thu, Feb 13, 2014 at 10:21 AM, Imesh Gunaratne im...@wso2.com wrote:
Hi Sinthuja,
Thanks for your response. Absolutely the concern is not with the data
publisher but with the bam mediator logic being executed in the mediation
flow.
This is something I experienced during last couple of days while
configuring several BAM mediators in an ESB flow. When a load test was run
(with a set of concurrent users) and the ESB mediation latency was
monitored, the BAM mediators were taking considerable amount of time
comapred with the ESB latency without having the BAM mediators. It was like
90 ms with the BAM mediators and 35 ms without them.
What I wanted to highlight here is that, I could not see any reason for
executing the above logic in the mediation flow and adding several
millisecods to the ESB latency.
Thanks
On Thu, Feb 13, 2014 at 12:32 AM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi Imesh,
Publish() method in data publisher is not a blocking call, it's a
asynchronous call. Within data publisher the events are put into a queue
and a separate thread does the real publishing to BAM. Also in BAM
mediator, the AsyncDataPublisher is being used therefore the connection to
BAM is also made asynchronous. Hence IMHO it's not required to spawn a new
thread externally to publish the events and make it complicated.
Thanks,
Sinthuja.
On Thu, Feb 13, 2014 at 2:15 AM, Imesh Gunaratne im...@wso2.com wrote:
Hi,
This is regarding the BAM Mediator 4.2.0.
As it looks like currently the BAM Mediator is executing the data
publishing logic in the same thread which the current message mediation is
happening:
public class BamMediator:
public boolean mediate(MessageContext messageContext) {
...
try {
stream.sendEvents(messageContext);
} catch (BamMediatorException e) {
return true;
}
}
}
public class Stream {
...
public void sendEvents(MessageContext messageContext) throws
BamMediatorException {
ActivityIDSetter activityIDSetter = new ActivityIDSetter();
activityIDSetter.setActivityIdInTransportHeader(messageContext);
try {
if (!isPublisherCreated) {
initializeDataPublisher(this);
isPublisherCreated = true;
}
this.publishEvent(messageContext);
} catch (BamMediatorException e) {
String errorMsg = Problem occurred while logging events in
the BAM Mediator. + e.getMessage();
log.error(errorMsg, e);
throw new BamMediatorException(errorMsg, e);
}
}
...
}
I think if we move this logic to a new thread we could reduce the time
it takes to execute the data publishing logic from the main message flow.
WDYT?
Thanks
--
*Imesh Gunaratne*
Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Sinthuja Rajendran*
Software Engineer http://wso2.com/
WSO2, Inc.:http://wso2.com
Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
--
*Imesh Gunaratne*
Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
--
*Imesh Gunaratne*
Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ayashkantha Ramasinghe
Software Engineer WSO2, Inc.
email: ayashkan...@wso2.com sanj...@wso2.com;
TP: +94 77 7 487 669
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager 1.7 - Clustering Documentation
Updated the note in this topic which still listed only APIM 1.5 and 1.6. Thanks, Sam *Samuel Gnaniah* Senior Technical Writer WSO2 (pvt.) Ltd. Colombo, Sri Lanka (+94) 773131798 On Fri, Jun 13, 2014 at 1:58 AM, Supun Malinga sup...@wso2.com wrote: Hi, AFAIK you can. Since 1.7 also is under platform 4.2.0 as well this[1] is supposed be the correct doc. @Doc. team, have we updated the doc accordingly ?. thanks, On Wed, Jun 11, 2014 at 7:52 PM, Dakshika Jayathilaka daksh...@wso2.com wrote: Hi, AFAIK API manager 1.7 release under chunk 11(carbon 4.2.0 ). $subject [1] mentioned a note say this doc can applicable only for 1.5 1.6. Is that possible to use this same doc on API Manager 1.7 ? If its possible better to update this page as wel. [1] https://docs.wso2.org/display/CLUSTER420/Clustering+API+Manager Regards, *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] what is the best practise for installing a production instance of a WSO2 product, e.g. ESB?
Hi Chris, I have come across this blog for (b) [1] http://sumedhask.blogspot.com/2013/10/start-wso2-server-as-linux-service.html On Thu, Jun 12, 2014 at 10:37 PM, chris snow chsnow...@gmail.com wrote: As per the $subject, what is the best practise? I have seen instructions for extracting the binary [1] and running the startup script [2], but just these steps don't seem robust enough for a production environment. In a production environment, I would expect to see some additional steps: a) create a unix user account and unix group for running the service b) creating init.d scripts for starting the service automatically c) to security harden the service (e.g. replace self signed certificates - which certificates, change default passwords - which user accounts) d) configuring clustering (this seems to be documented [3]) e) configuring a production database credential store (this seems to be documented [4]), or f) configuring a production ldap credential store Have I missed some documentation in the wiki, or are these undocumented steps not normally performed in production environments? I've also seen some puppet scripts [5]. Are these scripts production ready? Many thanks, Chris --- [1] https://docs.wso2.org/display/ESB481/Installing+on+Linux [2] https://docs.wso2.org/display/ESB481/Running+the+Product [3] https://docs.wso2.org/display/ESB481/Clustered+Deployment [4] https://docs.wso2.org/display/ESB481/Working+with+Databases [5] https://github.com/wso2/Puppet/tree/master/modules/esb/4.8.0/esb ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How to handle SOAP faults in Jaggey
Hi, According to jaggery documentation http://jaggeryjs.org/documentation.jag?api=ws WSRequest has a error member; *when an asynchronous operation failed to complete successfully (including internal errors, or protocol errors such as SOAP faults)* I have tried accessing this member in a try catch block and got the following error. *org.jaggeryjs.scriptengine.exceptions.ScriptException: org.mozilla.javascript.EvaluatorException: Constructor for WebServiceError not found.* Can I use this to handle SOAP faults? if yes: how? or is there a better way to handle SOAP faults in jaggery? Regards, -- *Anuruddha Premalal* Software Eng. | WSO2 Inc. Mobile : +94710461070 Web site : www.regilandvalley.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Proper Guide on RESTful API designing
+1 to have proper guideline for all our products. On Fri, Jun 13, 2014 at 2:21 AM, Chan duli...@wso2.com wrote: I think we really need to push this and get a guideline of best practices for REST APIs. Bunch of products have REST APIs built to the core and I think we had some discussions around focusing API Manger on API Designing as well. +1 to have a guideline of best practices for all our products. Cheers~ On Wed, Jun 11, 2014 at 8:45 PM, Dakshika Jayathilaka daksh...@wso2.com wrote: Hi, Do we have $subject. Are we following any specific set of guidance or Is that ok to go with general best practices. ex: [1 http://www.amazon.com/gp/product/1449310508/] [1] http://www.amazon.com/gp/product/1449310508/ Regards, *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [BAM] Optimizing BAM Mediator Data Publishing Logic
HI Ayash,
Yes after doing the optimisations we placed the BAM mediator after the
send call in the out mediation flow.
Thanks
On Fri, Jun 13, 2014 at 2:33 AM, Ayash ayashkan...@wso2.com wrote:
Hi Imesh,
While experiencing this problem, do you remember where the BAM Mediators
were in the mediation flow? Have you kept them after calling send or
before in the mediation flow?
Thanks,
-Ayash
On Thu, Feb 13, 2014 at 2:18 PM, Imesh Gunaratne im...@wso2.com wrote:
s/comapred/compared/g
s/millisecods/milliseconds/g
On Thu, Feb 13, 2014 at 10:21 AM, Imesh Gunaratne im...@wso2.com wrote:
Hi Sinthuja,
Thanks for your response. Absolutely the concern is not with the data
publisher but with the bam mediator logic being executed in the mediation
flow.
This is something I experienced during last couple of days while
configuring several BAM mediators in an ESB flow. When a load test was run
(with a set of concurrent users) and the ESB mediation latency was
monitored, the BAM mediators were taking considerable amount of time
comapred with the ESB latency without having the BAM mediators. It was like
90 ms with the BAM mediators and 35 ms without them.
What I wanted to highlight here is that, I could not see any reason for
executing the above logic in the mediation flow and adding several
millisecods to the ESB latency.
Thanks
On Thu, Feb 13, 2014 at 12:32 AM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi Imesh,
Publish() method in data publisher is not a blocking call, it's a
asynchronous call. Within data publisher the events are put into a queue
and a separate thread does the real publishing to BAM. Also in BAM
mediator, the AsyncDataPublisher is being used therefore the connection to
BAM is also made asynchronous. Hence IMHO it's not required to spawn a new
thread externally to publish the events and make it complicated.
Thanks,
Sinthuja.
On Thu, Feb 13, 2014 at 2:15 AM, Imesh Gunaratne im...@wso2.com
wrote:
Hi,
This is regarding the BAM Mediator 4.2.0.
As it looks like currently the BAM Mediator is executing the data
publishing logic in the same thread which the current message mediation is
happening:
public class BamMediator:
public boolean mediate(MessageContext messageContext) {
...
try {
stream.sendEvents(messageContext);
} catch (BamMediatorException e) {
return true;
}
}
}
public class Stream {
...
public void sendEvents(MessageContext messageContext) throws
BamMediatorException {
ActivityIDSetter activityIDSetter = new ActivityIDSetter();
activityIDSetter.setActivityIdInTransportHeader(messageContext);
try {
if (!isPublisherCreated) {
initializeDataPublisher(this);
isPublisherCreated = true;
}
this.publishEvent(messageContext);
} catch (BamMediatorException e) {
String errorMsg = Problem occurred while logging events in
the BAM Mediator. + e.getMessage();
log.error(errorMsg, e);
throw new BamMediatorException(errorMsg, e);
}
}
...
}
I think if we move this logic to a new thread we could reduce the time
it takes to execute the data publishing logic from the main message flow.
WDYT?
Thanks
--
*Imesh Gunaratne*
Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Sinthuja Rajendran*
Software Engineer http://wso2.com/
WSO2, Inc.:http://wso2.com
Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
--
*Imesh Gunaratne*
Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
--
*Imesh Gunaratne*
Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ayashkantha Ramasinghe
Software Engineer WSO2, Inc.
email: ayashkan...@wso2.com sanj...@wso2.com;
TP: +94 77 7 487 669
--
*Imesh Gunaratne*
Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Sohani Weerasinghe
Congrats! On Fri, Jun 13, 2014 at 1:54 AM, Supun Malinga sup...@wso2.com wrote: Congrats!.. On Tue, Jun 10, 2014 at 9:49 PM, Susinda Perera susi...@wso2.com wrote: Congratulations On Mon, Jun 2, 2014 at 4:55 PM, Shameera Rathnayaka shame...@wso2.com wrote: On Mon, Jun 2, 2014 at 4:43 PM, Shameera Rathnayaka shame...@wso2.com wrote: Congratulation Shani !!! It should be Sohani, sorry for mistype :) On Mon, Jun 2, 2014 at 3:57 PM, Sohani Weerasinghe soh...@wso2.com wrote: Thank you everyone Thanks, Sohani Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Sun, Jun 1, 2014 at 3:10 PM, Dilini Muthumala dil...@wso2.com wrote: Congrats, Sohani! On Sun, Jun 1, 2014 at 9:31 AM, Rajith Vitharana raji...@wso2.com wrote: congrats!!! On Sat, May 31, 2014 at 8:58 AM, Tania Mahanama ta...@wso2.com wrote: Congrats!! On Sat, May 31, 2014 at 7:58 AM, Thanuja Jayasinghe than...@wso2.com wrote: Congratz!!! On 30 May 2014 17:00, Lali Devamanthri l...@wso2.com wrote: Congratulations On Fri, May 30, 2014 at 11:06 AM, Jasintha Dasanayake jasin...@wso2.com wrote: Hi All, It's my distinct pleasure to welcome Sohani as a WSO2 Committer. Sohani has been a valuable contributor for WSO2 Developer Studio since she joined WSO2. In recognition of her contributions to WSO2, she has been voted as a WSO2 Committer. Sohani, Congratulations and Keep up the good work! Thanks and Regards, /Jasintha -- *Jasintha Dasanayake * *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/ lean . enterprise . middleware* *mobile :- 0711368118 0711368118 * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lali Sudaththa Devamanthri* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 71 895 4922 http://www.wso2.com ___ 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 -- Tania Mahanama Senior Technical Writer Contact: Mob: +94 077 5129270 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dilini Muthumala* Software Engineer, WSO2 Inc. *E-mail :* dil...@wso2.com *Mobile: *+94713 400 029 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.org shame...@apache.org* *phone: +9471 922 1454 %2B9471%20922%201454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.org shame...@apache.org* *phone: +9471 922 1454 %2B9471%20922%201454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Best Regards, *Praneesha Chandrasiri* *Technical Writer* *WSO2 Inc. * *Mobile: +(94) 718156888* *E-mail: pranee...@wso2.com pranee...@wso2.com* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Lali Devamanthri
Congrats! On Fri, Jun 13, 2014 at 1:54 AM, Supun Malinga sup...@wso2.com wrote: Congrats Lali! On Tue, Jun 10, 2014 at 9:49 PM, Susinda Perera susi...@wso2.com wrote: Congratulations On Sun, Jun 1, 2014 at 9:00 PM, Rajith Vitharana raji...@wso2.com wrote: Congrats..!!! On Sun, Jun 1, 2014 at 3:11 PM, Dilini Muthumala dil...@wso2.com wrote: Congrats!! On Sat, May 31, 2014 at 8:59 AM, Tania Mahanama ta...@wso2.com wrote: Congrats!! On Sat, May 31, 2014 at 8:04 AM, Thanuja Jayasinghe than...@wso2.com wrote: Congratz!!! On 30 May 2014 20:15, Isuruwan Herath isuru...@wso2.com wrote: Congrats Lali!!! On Fri, May 30, 2014 at 7:01 AM, Waruna Jayaweera waru...@wso2.com wrote: Congratzz...:D On Fri, May 30, 2014 at 12:11 PM, Dinesh Bandara dine...@wso2.com wrote: Congratulations ! On Fri, May 30, 2014 at 11:08 AM, Jasintha Dasanayake jasin...@wso2.com wrote: Hi All, It's my distinct pleasure to welcome Lali as a WSO2 Committer. Lali has been a valuable contributor for WSO2 Developer Studio since he joined WSO2. In recognition of his contributions to WSO2, he has been voted as a WSO2 Committer. Lali, Congratulations and Keep up the good work! Thanks and Regards, /Jasintha -- *Jasintha Dasanayake * *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/ lean . enterprise . middleware* *mobile :- 0711368118 0711368118 * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dinesh Bandara* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Waruna Lakshitha Jayaweera Software Engineer WSO2 Inc; http://wso2.com phone: +94713255198 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuruwan Herath Technical Lead Contact: +94 776 273 296 ___ 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 -- Tania Mahanama Senior Technical Writer Contact: Mob: +94 077 5129270 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dilini Muthumala* Software Engineer, WSO2 Inc. *E-mail :* dil...@wso2.com *Mobile: *+94713 400 029 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Best Regards, *Praneesha Chandrasiri* *Technical Writer* *WSO2 Inc. * *Mobile: +(94) 718156888* *E-mail: pranee...@wso2.com pranee...@wso2.com* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue on WSRegistry Service Client on content reading concurrently on a single connection
Hi,
Here I am attaching the patch which does the check of the content size. And
if it is 1MB then we load it to memory and pass a ByteArray data source
for the data handler. And if 1MB we proceed as previously.
@Danushka,
Please use the following patch and verify your scenario.
On Tue, Jun 10, 2014 at 8:34 PM, Ajith Vitharana aji...@wso2.com wrote:
Please find the blog post [1].
[1]http://ajithvblogs.blogspot.de/2013/11/jmeter-java-request-to-test.html
Thanks.
Ajith
On Tue, Jun 10, 2014 at 8:28 PM, Subash Chaturanga sub...@wso2.com
wrote:
Hi ,
This is regarding issue on WS Registry Service Client in high
concurrency which seems blocks the AF release.
When reading the content with several threads in AF, i.e two resources
path = /foo/r1 content = 12345
path = /foo/r2 content = 67
For AF guys, when they retrieve r1 and r2 resources, i.e for
r1 - returns 12345
but r2 returns 67*45*
( r2 returns with some values from old resource content. )
When dig deep with Janaka, found that, in server side
org.wso2.carbon.registry.ws.api.WSRegistry maintains single tempFile per
instance. And it get used to maintain the content to pass to client side
inside the DataHolder.
Hence obviously we can expect this issue in a but high concurrency. So as
a solution when creating the data holder we create a copy of the
aforementioned file as follows. And then for multiple requests on the same
ws connection it deals with separate files and issue went away.
But this leads to grow the tmp files in the tmp directory but upon server
downtime those will get vanished.
With the following fix, since files are growing, one option is to do an
additional ws call inside ws-client to server side to clean up the
particular file. But it seems not a best solution.
*So @Senaka @Ajith, Any better solution you can see ? *
Index:
src/main/java/org/wso2/carbon/registry/ws/api/utils/CommonUtil.java
===
--- src/main/java/org/wso2/carbon/registry/ws/api/utils/CommonUtil.java
(revision 204294)
+++ src/main/java/org/wso2/carbon/registry/ws/api/utils/CommonUtil.java
(working copy)
@@ -193,6 +193,9 @@
}
public static DataHandler makeDataHandler(Resource resource, File
tempFile) throws IOException, RegistryException{
+tempFile = File.createTempFile(wsresource, .tmp);
+tempFile.deleteOnExit();
+
if (resource.getContent() == null) {
return null;
}
--
Thanks
/subash
*Subash Chaturanga*
Senior Software Engineer :Platform TG; WSO2 Inc. http://wso2.com
email: sub...@wso2.com
blog: http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email : aji...@wso2.com
Mobile : +94772217350
--
Thanks
/subash
*Subash Chaturanga*
Senior Software Engineer Lead WSO2 Governance Registry
Platform TG; WSO2 Inc. http://wso2.com
Contact:
email: sub...@wso2.com
blog: http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
Index: src/main/java/org/wso2/carbon/registry/ws/api/utils/CommonUtil.java
===
--- src/main/java/org/wso2/carbon/registry/ws/api/utils/CommonUtil.java (revision 191396)
+++ src/main/java/org/wso2/carbon/registry/ws/api/utils/CommonUtil.java (working copy)
@@ -46,9 +46,11 @@
import javax.activation.DataHandler;
import javax.activation.FileDataSource;
+import javax.mail.util.ByteArrayDataSource;
import javax.servlet.http.HttpServletRequest;
import org.apache.axis2.context.MessageContext;
+import org.apache.commons.io.IOUtils;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.wso2.carbon.registry.core.*;
@@ -192,32 +194,39 @@
return output.toByteArray();
}
-public static DataHandler makeDataHandler(Resource resource, File tempFile) throws IOException, RegistryException{
+public static DataHandler makeDataHandler(Resource resource, File tempFile) throws IOException, RegistryException {
if (resource.getContent() == null) {
return null;
}
InputStream is = null;
OutputStream os = null;
+
+
try {
-os = new FileOutputStream(tempFile);
if (resource.getContent() instanceof String[]) {
String[] strArray = (String[]) resource.getContent();
ObjectOutputStream oos = new ObjectOutputStream(os);
oos.writeObject(strArray);
} else {
-try {
-is = resource.getContentStream();
-//os = new FileOutputStream(tempFile);
+is = resource.getContentStream();
+if (isContentLarge(resource.getContentStream())) {
+try {
+
[Dev] How to submit an OT article?
Hi, Whats the procedure I should follow to submit an OT article? The submit link on [1] seems to be redirecting to the WSO2 home page. [1] http://wso2.com/library/submit/ Thanks, Supun -- *Supun Sethunga* Software Engineer WSO2, Inc. lean | enterprise | middleware Mobile : +94 716546324 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Tomcat Lifecycle listener how to.
adding Ruchira Sagara dev group
Did you try the Before start event?
Sorry, If I misunderstood the last email.
On Fri, Jun 13, 2014 at 11:13 AM, Mohamed Nasmin nasmin1...@gmail.com
wrote:
Thanks once again. I tried that by configuring context.xml. But I cannot
trigger the BEFORE_INIT_EVENT. Other events are triggering well. This is
the out put after configuring the listener with context.xml.
INFO: Deploying web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/docs
*this is before start eventthis is start eventthis is after start event*
Jun 13, 2014 11:03:27 AM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/docs has finished in 1,482
ms
Jun 13, 2014 11:03:27 AM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/manager
*this is before start eventthis is start eventthis is after start event*
Jun 13, 2014 11:03:28 AM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/manager has finished in
211 ms
Jun 13, 2014 11:03:28 AM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/host-manager
*this is before start event this is start eventthis is after start event*
Jun 13, 2014 11:03:28 AM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/host-manager has finished
in 208 ms
Jun 13, 2014 11:03:28 AM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/ROOT
*this is before start eventthis is start event this is after start event*
Jun 13, 2014 11:03:28 AM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/ROOT has finished in 105 ms
Jun 13, 2014 11:03:28 AM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/examples
*this is before start eventthis is start event this is after start event*
Jun 13, 2014 11:03:29 AM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory
/home/nasmin/tomcat/apache-tomcat-7.0.54/webapps/examples has finished in
1,136 ms
Jun 13, 2014 11:03:29 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-bio-8080]
Jun 13, 2014 11:03:29 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [ajp-bio-8009]
Jun 13, 2014 11:03:29 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 4090 ms
In the context.xml I put like below. But there is a WatchedResource
element. It already run and initialize the context. I googled it but could
not find a solution. Can we handle this issue? If we get triggered
BEFORE_INIT_EVENT here then my problem is solved. Please advice on this.
Thanks alot for your guidance ayye.
!-- Default set of monitored resources --
Listener className=org.jaggery.tomcat.listener.TomcatListener /
*WatchedResourceWEB-INF/web.xml/WatchedResource*
On Fri, Jun 13, 2014 at 10:52 AM, Chamil Jeewantha cha...@wso2.com
wrote:
Please try configuring your lifecycle listener on context.xml file. [1].
[1] http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
On Fri, Jun 13, 2014 at 12:29 AM, Mohamed Nasmin nasmin1...@gmail.com
wrote:
Thanks for the reply Ayye.
This is the code I checked.
public void lifecycleEvent(LifecycleEvent event) {
String type = event.getType();
if (Lifecycle.BEFORE_INIT_EVENT.equals(type)) {
System.out.println(this is before init event);
//Object source = event.getSource();
Lifecycle source = event.getLifecycle();
if (source instanceof StandardContext) {
System.out.println(it is a Context nested lifecycle event);
StandardContext standardContext = (StandardContext) source;
System.out.println(Context details : +
standardContext.toString());
}
else{
System.out.println(There is no app source available);
}
}
else if (Lifecycle.BEFORE_START_EVENT.equals(type)){
System.out.println(this is before start event);
}
else if (Lifecycle.AFTER_INIT_EVENT.equals(type)){
System.out.println(this is after init event);
}
else if (Lifecycle.AFTER_START_EVENT.equals(type)){
System.out.println(this is after start event);
}
