<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-5034237350667380624</atom:id><lastBuildDate>Sat, 04 Apr 2026 11:33:20 +0000</lastBuildDate><category>carbon</category><category>ESB</category><category>Java</category><category>OSGi</category><category>Linux</category><category>Architecture</category><category>Carbon 4.0</category><category>Identity</category><category>Operating Systems</category><category>Tomcat</category><category>YouTube</category><category>tutorials</category><category>ubuntu 9.04</category><category>webinar</category><category>wso2</category><category>Authorization</category><category>Axis2</category><category>BISSA</category><category>Blowing in the Wind</category><category>BoF</category><category>Broker</category><category>C/C++</category><category>Compile</category><category>Debian</category><category>Deployment Synchronizer</category><category>EIP</category><category>Eclipse</category><category>Fusesource</category><category>GCE10</category><category>GDB</category><category>IE</category><category>IEEE</category><category>JKS</category><category>JMX</category><category>Java Colombo</category><category>Johnny</category><category>Kernel</category><category>MPI</category><category>MQTT</category><category>Message Broker</category><category>NIO</category><category>OSGi console</category><category>OpenAM</category><category>OpenOffice</category><category>OpenSSO</category><category>P2</category><category>PKC</category><category>Pax</category><category>Presentation</category><category>PubSub</category><category>REST</category><category>Raspberry-pi</category><category>SAML2</category><category>SC10</category><category>SSO</category><category>UNIX</category><category>Ubuntu</category><category>WSO2 Carbon</category><category>WSO2Con</category><category>Web-apps</category><category>XACML</category><category>ack-grep</category><category>cartoon</category><category>cricket</category><category>drivers</category><category>equinox</category><category>flv to mp3</category><category>funny</category><category>git</category><category>gnuplot</category><category>jre</category><category>maven</category><category>memory</category><category>micro-architecture</category><category>notes</category><category>openjdk</category><category>patterns</category><category>performance</category><category>proBook 4410s</category><category>profiling</category><category>reactor pattern</category><category>security</category><category>server architecture</category><category>tools</category><category>vim</category><category>web services</category><category>white-board</category><category>windows XP</category><category>xml</category><title>AVAKASHA</title><description>Pradeep Fernando&#39;s blog space</description><link>http://pradeepfernando.blogspot.com/</link><managingEditor>noreply@blogger.com (pradeep fernando)</managingEditor><generator>Blogger</generator><openSearch:totalResults>42</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-4745398929176487847</guid><pubDate>Fri, 02 Dec 2016 17:40:00 +0000</pubDate><atom:updated>2016-12-02T23:10:09.688+05:30</atom:updated><title>Articles Worth Reading</title><atom:summary type="text">
Below is a reading list that i find interesting.



Working with native memory in managed languages.
- https://dzone.com/articles/understanding-sunmiscunsafe
</atom:summary><link>http://pradeepfernando.blogspot.com/2016/12/articles-worth-reading.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-8839474973986878934</guid><pubDate>Fri, 04 Sep 2015 17:12:00 +0000</pubDate><atom:updated>2016-01-07T23:30:31.218+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">GDB</category><category domain="http://www.blogger.com/atom/ns#">MPI</category><title>Debugging MPI applications with GDB</title><atom:summary type="text">
Basic GDB

&#39;sayHello&#39; being the program binary

&amp;gt; gdb sayHello

&amp;gt; b 10 &amp;nbsp;- set the breakpoint at line 10


&amp;gt; run &amp;nbsp; - run the program under debugger


&amp;gt; print &#39;variable_name&#39; &amp;nbsp;- print the variable name


Ctrl+x , a &amp;nbsp; &amp;nbsp;will enable the gui based debugging in the gdb.


MPI debugging,

running a program under gdb

&amp;gt; mpiexec -n 4 xterm -e gdb ./gtc

this will </atom:summary><link>http://pradeepfernando.blogspot.com/2015/09/command-line-debug.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-8776972973798212485</guid><pubDate>Mon, 04 May 2015 23:20:00 +0000</pubDate><atom:updated>2015-05-05T04:50:43.038+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Compile</category><category domain="http://www.blogger.com/atom/ns#">Kernel</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">Operating Systems</category><category domain="http://www.blogger.com/atom/ns#">Ubuntu</category><title>Compiling/Installing Mainline Linux Kernel on Ubuntu</title><atom:summary type="text">
Canonical provides Ubuntu flavors of mainline kernel. However I wanted to install the latest kernel, straight from the Linus&#39;s git repo . :)I used a virtual machine environment to compile and install the kernel. We can install the followingsoftware packages using Ubuntu&#39;s package manager (apt).
- Qemu   - virtualization platform- Virt-manager  - GUI for qemuI used 14.04 Ubuntu distribution  - </atom:summary><link>http://pradeepfernando.blogspot.com/2015/05/compilinginstalling-mainline-linux.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLLJR0dCuaeK57-DVu5ccE_gzn3VxOTLVGI4IS5UU0H2Gi7qlqfECv2wpAgAs7XCrLaEDjuXAvabCK4OFmR7887HjoO2WMGPQJp_J2EVwU_DIFXhCl-FeOF5Zdach_4xlwlo9WRUkc3Iy3/s72-c/select-1.jpg" height="72" width="72"/><thr:total>2</thr:total><georss:featurename>United States</georss:featurename><georss:point>35.173808317999587 -83.671875000000057</georss:point><georss:box>8.727644817999586 -124.98046900000006 61.619971817999584 -42.363281000000057</georss:box></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-6992757575321059195</guid><pubDate>Sun, 03 May 2015 18:59:00 +0000</pubDate><atom:updated>2015-05-04T00:31:52.323+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">micro-architecture</category><category domain="http://www.blogger.com/atom/ns#">Operating Systems</category><title>Intel Processor Micro-architecture Code  Names</title><atom:summary type="text">
It follows a tick-tock naming convention.

Tock - New micro-architecture while keeping the process technology the same.
Tick &amp;nbsp;- Improving on the previous micro-architecture using process technology. (45nm etc.)


Nehalem (tock) &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 45nm
Westmere (tick) &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;32nm

Sandy Bridge (tock) &amp;nbsp;32 nm
Ivy Bridge (tick) &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;22 nm
</atom:summary><link>http://pradeepfernando.blogspot.com/2015/05/intel-processor-micro-architecture-code.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-9216872354703904044</guid><pubDate>Tue, 16 Jul 2013 10:37:00 +0000</pubDate><atom:updated>2013-07-16T20:16:49.584+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">carbon</category><category domain="http://www.blogger.com/atom/ns#">webinar</category><title>[Webinar] Extending WSO2 Carbon for Your Middleware Needs</title><atom:summary type="text">
I am going to conduct a webinar on the $title. In this webinar we are going to cover the possible usages of the extension points provided by Carbon platform. Carbon is a very powerful&amp;nbsp;middle-ware&amp;nbsp;platform as it is... , however it provides enough flexibility to the developer if he/she wants to alter the default&amp;nbsp;behavior.




Carbon Runtime View - diagram by sameeraJayasoma.







</atom:summary><link>http://pradeepfernando.blogspot.com/2013/07/webinar-extending-wso2-carbon-for-your.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg3Xw8Jw7fyo8Dc7NLwdTPu1P-S3b65I0_6D_LlnxlVwpn_VXzIslXcS9mGNy5b9vja0Pl6aoRkq6YgtlXA5Kjyq6GD_1chUdD812_IPPiHiaim8LOEB3_RcC7sCT7rVlelpK1ksrRrDgcs/s72-c/CarbonArchitectureRuntimeviews1+(1).jpeg" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-3083564650073789849</guid><pubDate>Sat, 29 Jun 2013 09:23:00 +0000</pubDate><atom:updated>2013-06-29T15:04:25.262+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Identity</category><category domain="http://www.blogger.com/atom/ns#">JKS</category><category domain="http://www.blogger.com/atom/ns#">OpenAM</category><category domain="http://www.blogger.com/atom/ns#">OpenSSO</category><category domain="http://www.blogger.com/atom/ns#">SAML2</category><category domain="http://www.blogger.com/atom/ns#">SSO</category><title>Enabling SAML2 SSO for WSO2 Carbon Server, OpenSSO/OpenAM as the IDP</title><atom:summary type="text">

WSO2 Carbon products comes with in-built web-SSO authenticators. Within minutes, you can enable web-SSO for any WSO2 Carbon server using WSO2 Identity Server as the IDP. In this blog post we are using, OpenSSO/OpenAM as the IDP and do the configuration.



Pre-requisites

1. Download and install openAM/openSSO [download the war file from here]
2. Download the WSO2 product.




Setting up the </atom:summary><link>http://pradeepfernando.blogspot.com/2013/06/enabling-saml2-sso-for-wso2-carbon.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkWKQP-Mu8tUq7mv5urAhy-b6iqDYuR1PG0FPlWoD4S53BnyCoDjx4rKm0lQaVuAcijmBeSDmIO0HFE0DyPlDn9c1N6V6rJsZPA03wLP8PLphQYbJuMMCNjGFxzx2EvWVQTQR3pROg0XuD/s72-c/blog1.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-2864251775240776317</guid><pubDate>Fri, 26 Apr 2013 07:40:00 +0000</pubDate><atom:updated>2013-04-26T13:10:32.650+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Architecture</category><category domain="http://www.blogger.com/atom/ns#">Eclipse</category><category domain="http://www.blogger.com/atom/ns#">OSGi</category><category domain="http://www.blogger.com/atom/ns#">P2</category><category domain="http://www.blogger.com/atom/ns#">WSO2 Carbon</category><title>Multiple Profiles and Shared Bundles With Eclipse P2 : Case Study</title><atom:summary type="text">

WSO2 Carbon is an OSGi based server framework. Number of WSO2 middleware products use Carbon as their base platform. Carbon make use of Eclipse Equinox as its OSGi framework implementation and use Eclipse P2 as its provisioning framework.

Problem Description


Some of the Carbon products has their own deployment patterns during actual production deployments. However to give a smooth evaluation</atom:summary><link>http://pradeepfernando.blogspot.com/2013/04/multiple-profiles-and-shared-bundles.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhNws9KqEG_Klg9TQkFPxwegSgqQEG6o5xU0fWCeRzTC0Wgnam41zF_YjxaKBfwdcYusI6ApnnY_S65LrNihXxidYCDTgFpZBHBND3irl0MMO0impix-yoQxQHLjlvwZUrbX2bGfJqS-FHz/s72-c/bamarchitecture.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-7760763210591068895</guid><pubDate>Mon, 15 Apr 2013 04:13:00 +0000</pubDate><atom:updated>2013-04-15T09:46:42.721+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Broker</category><category domain="http://www.blogger.com/atom/ns#">ESB</category><category domain="http://www.blogger.com/atom/ns#">MQTT</category><category domain="http://www.blogger.com/atom/ns#">PubSub</category><title>MQTT Transport for Axis2/Synapse</title><atom:summary type="text">
MQTT is an application layer broker based pub/sub protocol built on top of TCP/IP. It is very lightweight and hence ideal for usage in network/memory/computing power constrained environments. If I quote the MQTT spec, the protocol features,

Pub/Sub message pattern
Small transport overhead, fixed length header being only 2 bytes
Supports three QOS for message delivery,&amp;nbsp;at-least&amp;nbsp;once, </atom:summary><link>http://pradeepfernando.blogspot.com/2013/04/mqtt-transport-for-axis2synapse.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjhwomsLv5Zhqu5CHtYeK5LLH1eBKPdPJ7N4xuDiePDYDufEntM0OVy3oo_E7labjaOwjJA8nwzg_h2hFc3TlbV7zUIUtj4vH5OFh_QKIqta7qCjLLH94_0cIygEh8OhM_AYHc82f7FpiQB/s72-c/Untitled+drawing+%25282%2529.jpg" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-1914843798766804884</guid><pubDate>Thu, 11 Apr 2013 12:06:00 +0000</pubDate><atom:updated>2013-04-11T17:36:00.151+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">EIP</category><category domain="http://www.blogger.com/atom/ns#">ESB</category><category domain="http://www.blogger.com/atom/ns#">Message Broker</category><title>Dealing with Occasional Message Bursts : Message Broker Use Case</title><atom:summary type="text">

Recently I came across the following requirement,



An organization has a message delivery network and an application that makes use of those messages (process them). The delivery network directly communicates with the message processing application. Things seems to be working fine on a regular day. However if the load(incurred by the delivery network) is high, some of the messages may get </atom:summary><link>http://pradeepfernando.blogspot.com/2013/04/dealing-with-occasional-message-bursts.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkXfJK941PYi1W-nJ_bHQ4whP-fO-sZRE2uDWdvB5weW0h05M3_PhfRE_I1ONGezZQu5LrToQWILSLrKnSuP4i5kWBIMCgjRbpt4e4jXbLfn1uQomRwAqmSWwwXVwW7FnD9H0ucSM-hZvG/s72-c/Untitled+drawing+(1).jpg" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-1867587339193898039</guid><pubDate>Thu, 11 Apr 2013 07:46:00 +0000</pubDate><atom:updated>2013-04-11T13:16:33.513+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Java</category><category domain="http://www.blogger.com/atom/ns#">memory</category><category domain="http://www.blogger.com/atom/ns#">performance</category><category domain="http://www.blogger.com/atom/ns#">profiling</category><title>Application Profiling for Memory and Performance</title><atom:summary type="text">
Inspired by the experiences gathered during recent application profiling sessions at WSO2, we did a webinar on memory and performance tuning. Below are the slides.

  

 Application Profiling for Memory and Performance  from pradeepfn 


</atom:summary><link>http://pradeepfernando.blogspot.com/2013/04/application-profiling-for-memory-and.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-6010551238762542790</guid><pubDate>Tue, 26 Feb 2013 12:06:00 +0000</pubDate><atom:updated>2013-04-11T13:17:19.804+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Java</category><category domain="http://www.blogger.com/atom/ns#">NIO</category><category domain="http://www.blogger.com/atom/ns#">reactor pattern</category><category domain="http://www.blogger.com/atom/ns#">server architecture</category><title>Understanding Java NIO : My Notes</title><atom:summary type="text">
Why this blog post?

Recently I was working with a team to improve the mediation performance of Apache Synapse ESB. Java NIO was new to me when i took up the challenge. I spent few days learning I/O concepts and NIO particularly. Soon after my background reading period, I was pulled out to optimize Carbon kernel. Tough luck!. Then again I learnt few things and thought of compiling a blog post </atom:summary><link>http://pradeepfernando.blogspot.com/2013/02/understanding-java-nio-my-notes.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiUK2z0mCk16GTCBDAX7oNr4ED_D4BKM66AsSKHlfEKU7ljgkkhtwzNuiAsj3-T_N423jE1oIXaXW7Ctr3MR1latY_nSfUse2jS0be1ySy3yVC8yNMIjhvIpoK0arDx0ZgkgEeNUIx8IJM6/s72-c/swAwiEyNB9ckvxWXN2u6bSw.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-3991208179764194221</guid><pubDate>Thu, 14 Feb 2013 09:53:00 +0000</pubDate><atom:updated>2013-02-14T15:25:00.139+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Authorization</category><category domain="http://www.blogger.com/atom/ns#">ESB</category><category domain="http://www.blogger.com/atom/ns#">Fusesource</category><category domain="http://www.blogger.com/atom/ns#">Identity</category><category domain="http://www.blogger.com/atom/ns#">XACML</category><title>Fine Grained XACML Based Authorization With FuseSource ESB and WSO2 IS</title><atom:summary type="text">
Authorization - The bad way

In a typical organization that makes use of Service Oriented Architecture (fully/partially) to drive their IT requirements, chances are more to find tens/hundreds&amp;nbsp;of services scattered across departments. If the legacy services are works fine for the organization, changing them is not a wise decision. However one always has to consider the&amp;nbsp;maintainability&amp;</atom:summary><link>http://pradeepfernando.blogspot.com/2013/02/fine-grained-xacml-based-authorization.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4xGA8QnGOaKh7yJfySJm1yuocEoG5umWqXA-yhS49SmOEbFIzBnDR-8gGVhgE4ysjzVjhyphenhyphennyVCSIn-HlsGgOowZOMZU1lH9-LaE4OGMm_2UplqFU_0qDF-oyM9gwNxs2b6AQtkvRw0pSA/s72-c/Untitled+drawing.png" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-3194292131358417429</guid><pubDate>Sun, 10 Feb 2013 10:59:00 +0000</pubDate><atom:updated>2013-02-10T16:33:03.211+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">OSGi</category><category domain="http://www.blogger.com/atom/ns#">patterns</category><category domain="http://www.blogger.com/atom/ns#">Pax</category><category domain="http://www.blogger.com/atom/ns#">white-board</category><title>Patterns in OSGi programming : White Board Pattern</title><atom:summary type="text">

A common solution for a recurring problem can be named as a pattern. Patterns are everywhere. More often than not, we adopt patterns for computer science from our day to day life experiences. White board pattern is one such common pattern. The pattern allows you to decouple two parties from each other (consumer/provider). I came across this pattern for the first time during my final year </atom:summary><link>http://pradeepfernando.blogspot.com/2013/02/patterns-in-osgi-programming-white.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>4</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-7934451694494214581</guid><pubDate>Thu, 07 Feb 2013 02:23:00 +0000</pubDate><atom:updated>2013-02-07T07:53:18.485+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">BoF</category><category domain="http://www.blogger.com/atom/ns#">carbon</category><category domain="http://www.blogger.com/atom/ns#">WSO2Con</category><title>BoF Session on Carbon at WSO2Con 2013</title><atom:summary type="text">
WSO2 has organized a Birds of a Feather(BoF) session targeting next major efforts on WSO2 Carbon platform. We all can discuss/brainstorm/etc and decide on the future of Carbon Server Framework. The session will be held in London Conference premises and I am going to lead the session.











Agenda can be found here
</atom:summary><link>http://pradeepfernando.blogspot.com/2013/02/bof-session-on-carbon-at-wso2con-2013.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-4858251682572101680</guid><pubDate>Sun, 03 Feb 2013 16:56:00 +0000</pubDate><atom:updated>2013-02-03T22:27:53.304+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Java Colombo</category><category domain="http://www.blogger.com/atom/ns#">OSGi</category><category domain="http://www.blogger.com/atom/ns#">Presentation</category><title>Demystifying OSGi : Java Colombo Meetup </title><atom:summary type="text">
Java Colombo is the largest Java developer group in Sri Lanka. Recently, we (me and my collegue Sameera) did a introductory session on OSGi during one of their meetups. It was very well received. Below are the presentation slides we used during the meetup.





Me presenting at the meetup. :) The photo credit for below photo goes to Isuru Perera.



</atom:summary><link>http://pradeepfernando.blogspot.com/2013/02/demystifying-osgi-java-colombo-meetup.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-6838890305426750962</guid><pubDate>Thu, 10 Jan 2013 08:56:00 +0000</pubDate><atom:updated>2013-01-10T14:26:54.009+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Debian</category><category domain="http://www.blogger.com/atom/ns#">Raspberry-pi</category><title>Raspberry-pi : my notes</title><atom:summary type="text">

Raspberry-pi is a general purpose computer, that comes in the size of a credit card. The type B has 512 MB of memory and it comes with a ARM processor. It also has general purpose I/O (GPIO) which enables you to drive external I/O interfaces by means of programming. This getting started notes are for my own reference.&amp;nbsp;































Download the OS image for Raspberry-pi </atom:summary><link>http://pradeepfernando.blogspot.com/2013/01/raspberry-pi-my-notes.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEge1lgQHe-a4Sord_FSM1QKK4y74fE6eZUxyx_vFJKNizNWcySvqdv6SSzKsQe6o6un0mm_88ry0SF4MUdM-QKZIN6dKT7-j5DUN-3Y7tLC2ANGBYL7z_FqhmWFvKsRjvfDgC__Qi-3Nipr/s72-c/DSC00352.JPG" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-6434637127551828831</guid><pubDate>Sat, 24 Nov 2012 13:52:00 +0000</pubDate><atom:updated>2012-11-25T18:23:49.851+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">carbon</category><category domain="http://www.blogger.com/atom/ns#">JMX</category><title>JMX client to monitor Carbon Servers</title><atom:summary type="text">
Recently we were doing some load testing against Carbon servers. Soon we realized that there was no easy way to get average memory usage and CPU utilization. (apart from taking jconsole screenshots). End of the day we automated the whole testing process. Below is the JMX client [1] that we used to get details out from the remote running Carbon Server.

It dumps the details to a CSV file. Later </atom:summary><link>http://pradeepfernando.blogspot.com/2012/11/jmx-client-to-monitor-carbon-servers.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-7783907028005260076</guid><pubDate>Fri, 09 Nov 2012 10:10:00 +0000</pubDate><atom:updated>2012-11-09T15:40:31.640+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">carbon</category><category domain="http://www.blogger.com/atom/ns#">Deployment Synchronizer</category><category domain="http://www.blogger.com/atom/ns#">webinar</category><title>Webinar: Artifact Synchronization Between Cluster Nodes</title><atom:summary type="text">
Recently I did a webinar on the topic of &quot;Deployment Sysnchronizer&quot; : the sync-up mechanism we use to synchronize artifacts and meta data in our Carbon product clusters.

  
  WSO2 Dep Sync for Artifact Synchronization of Cluster Nodes  from WSO2 

</atom:summary><link>http://pradeepfernando.blogspot.com/2012/11/webinar-artifact-synchronization.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-1845212933513003362</guid><pubDate>Sun, 16 Sep 2012 03:28:00 +0000</pubDate><atom:updated>2012-09-16T08:58:47.166+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Carbon 4.0</category><category domain="http://www.blogger.com/atom/ns#">Tomcat</category><category domain="http://www.blogger.com/atom/ns#">Web-apps</category><title>Running WSO2 Carbon as a web-app - Apache Tomcat </title><atom:summary type="text">
As I have explained in one of my previous posts, WSO2 Carbon has undergone some major architectural changes from its 3.x.x version to version 4. One of our main goals during those changes was to make Carbon running in a pure-OSGi container instead of running it in a bridged mode. At some point we were considering to drop off the web-app mode deployment, altogether from the C4 release&amp;nbsp;</atom:summary><link>http://pradeepfernando.blogspot.com/2012/09/running-wso2-carbon-as-web-app-apache.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>6</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-3000987120488338497</guid><pubDate>Sat, 11 Aug 2012 05:26:00 +0000</pubDate><atom:updated>2012-08-11T10:56:50.078+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Architecture</category><category domain="http://www.blogger.com/atom/ns#">carbon</category><category domain="http://www.blogger.com/atom/ns#">Carbon 4.0</category><category domain="http://www.blogger.com/atom/ns#">OSGi</category><category domain="http://www.blogger.com/atom/ns#">Tomcat</category><title>WSO2 Carbon 4.0 Architecture - My Notes</title><atom:summary type="text">
With the 4.0 release of WSO2 Carbon&amp;nbsp; we have changed the internal architecture of the platform in a significant way. In the pre Carbon 4 era, WSO2 carbon used to get deployed as a web-app on apache-tomcat servlet container under the hood. The hight level architecture looked like,






&amp;nbsp;As shown in the above diagram Carbon framework get deployed as just another web-app in Apache tomcat</atom:summary><link>http://pradeepfernando.blogspot.com/2012/08/wso2-carbon-40-architecture-my-notes.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRQkQxPN-Jdy03E7QbwlVC2gQu03DF_LZ9xhFqebVr0px8D4quOu1MgAPSpgXq-kqqnOKubNEZf3iIFSTRs0Z4yofivKicN_S5Zkdre0jakR2i84hn0kiEzE5d_7Lb9s2qfFrP5EFwVB5E/s72-c/old-arch.png" height="72" width="72"/><thr:total>0</thr:total><georss:featurename>Panadura, Sri Lanka</georss:featurename><georss:point>6.717595 79.9128269</georss:point><georss:box>6.4653170000000006 79.5969699 6.969873 80.2286839</georss:box></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-5464439182449421356</guid><pubDate>Thu, 06 Oct 2011 18:28:00 +0000</pubDate><atom:updated>2012-08-11T15:46:59.971+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">equinox</category><category domain="http://www.blogger.com/atom/ns#">OSGi console</category><title>Debugging your OSGi Application using OSGi console commands</title><atom:summary type="text">
This blog post is mainly targeted at the WSO2 Carbon developers who make
 use of OSGi console to debug their bundles/components during the 
runtime. I&#39;m here assuming that you have the basic shell which you would
 find in equinox environment.
You can start any of the WSO2 server products (that is based on Carbon) 
with OSGi console enabled, by passing the system property &#39;osgiConsole&#39; 
during </atom:summary><link>http://pradeepfernando.blogspot.com/2011/10/debugging-your-osgi-application-using.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>8</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-9122603509673411613</guid><pubDate>Wed, 17 Aug 2011 05:03:00 +0000</pubDate><atom:updated>2011-08-17T10:34:45.697+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">git</category><category domain="http://www.blogger.com/atom/ns#">notes</category><title>Revert not-commited local changes of a file in Git</title><atom:summary type="text">

git checkout&amp;nbsp; &#39;file-name&#39;

just a small note</atom:summary><link>http://pradeepfernando.blogspot.com/2011/08/revert-not-commited-local-changes-of.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-3494419133676278049</guid><pubDate>Mon, 30 May 2011 09:29:00 +0000</pubDate><atom:updated>2011-05-30T14:59:11.309+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ESB</category><category domain="http://www.blogger.com/atom/ns#">REST</category><category domain="http://www.blogger.com/atom/ns#">wso2</category><title>POST variables get dropped while going through the WSO2 ESB proxy ... ?</title><atom:summary type="text">This is more of a small note in case I forget what i did while trying things out. First of all I created a ESB proxy for a back-end service that accepts post request and does some manipulation on the received request.

Once you create a ESB proxy by giving the above REST service as the service endpoint , the InSequence element of the proxy.xml will look like this.

&amp;lt;inSequence&amp;gt;
&amp;nbsp;&amp;nbsp;</atom:summary><link>http://pradeepfernando.blogspot.com/2011/05/post-variables-get-dropped-while-going.html</link><author>noreply@blogger.com (pradeep fernando)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-1089470872630538709</guid><pubDate>Fri, 15 Apr 2011 11:23:00 +0000</pubDate><atom:updated>2011-04-15T17:07:39.506+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">vim</category><category domain="http://www.blogger.com/atom/ns#">xml</category><title>Delete a set of elements in a xml file</title><atom:summary type="text">Recently I wanted to delete a certain search pattern in an XML file. Within the XML file I had a XML snippet;























and i wanted to delete the commented out part. I was able to do it with this, search replace command in vim.

:%s/&amp;lt;!--moved to nexus\_.\{-}--&amp;gt;

I got this to working by looking at the mail[1]
[1] http://osdir.com/ml/editors.vim/2002-06/msg00468.html 
its a </atom:summary><link>http://pradeepfernando.blogspot.com/2011/04/delete-set-of-elements-in-xml-file.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxuiERYl4bosYCJpP-4QptYUvy4STnr3TomDT0zaMrP5ZyAmsAnKcCVGqbuHxDHsDr1b9N7W7Seoq2vEL5UnZxkTbWR_dc9626TW7iSUnQqL7YKe-wAcM1f8iQzyqtmK5ZCO0uRwv2N18t/s72-c/xml.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-5034237350667380624.post-8329675244188685515</guid><pubDate>Sun, 05 Dec 2010 16:26:00 +0000</pubDate><atom:updated>2013-04-11T12:42:48.830+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">gnuplot</category><category domain="http://www.blogger.com/atom/ns#">IEEE</category><category domain="http://www.blogger.com/atom/ns#">UNIX</category><title>Plotting graphs for scientific papers with gnuplot</title><atom:summary type="text">



I was writing our first IEEE grade paper few days back. It was first written using MS word as my text editor. Now that it got selected to be published on the IEEE explore, we thought of preparing a latex based paper for final publication.

One of the major proplem was the image quality of some of the figures. I tackled that using the popular open source vector grphics editor - &amp;gt; Inkscape. </atom:summary><link>http://pradeepfernando.blogspot.com/2010/12/plotting-graphs-for-scientific-papers.html</link><author>noreply@blogger.com (pradeep fernando)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEji8azb5eFSzt5IwpRVh5dBYTh-4uFsnQr2eeVgYQODqQDL2CKPL4DmN2kZA4_TO0cBgnS6HQrdXcjtog_bOSxHDDGvD9LGuTCGsZr035DA5zp2f5LufYh9VvawnK9nb8SWXNFO60WjZc5b/s72-c/Screenshot.png" height="72" width="72"/><thr:total>0</thr:total></item></channel></rss>