tag:blogger.com,1999:blog-19439560409964223092024-10-05T09:20:43.465+05:30Blogs about Open Source and it's technologies I work on day-to-day life.Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.comBlogger66125tag:blogger.com,1999:blog-1943956040996422309.post-82234109044063958042016-02-20T07:00:00.000+05:302016-03-17T05:57:18.112+05:30

WSO2 has concluded another WSO2Con conference in grand style. The WSO2Con Asia 2016 has had special focus on the new WSO2 Microservices Framework for Java (WSO2 MSF4J in short) product. I have done a tutorial on how to write microservices with WSO2 MSF4J on the AppDev track. You can see the Agenda here - https://asia16.wso2con.com/agenda/ The WSO2 MSF4j is a lightweight, fast runtime with

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-24553856719200600412015-09-25T09:00:00.000+05:302016-03-17T05:55:04.525+05:30

WSO2 Application Server 5.3.0 has been released on top WSO2 Carbon Kernel 4.4.1. See the release note below to find out the cool and exciting features of this latest release.  The WSO2 Application Server is an enterprise-ready cloud-enabled application server, powered by Apache Tomcat, and Apache TomEE, it integrates Apache CXF framework. It provides first class support for standard

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-52457127963939919562014-12-17T03:02:00.000+05:302014-12-17T03:38:36.098+05:30

When viewing statistics of APIs in WSO2 API Manager 1.7.0 via WSO2 BAM, you may have come across the following issue. [1] As you might know, AM sends events about requests to APIs to WSO2 BAM. And, BAM stores these data in Cassandra storage which gets later by Hive analytics scripts. For AM, we have the am_stats_analyzer. After analyzing, the summarized information gets written to a RDBMS

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-79821028932289850262014-12-02T14:39:00.000+05:302014-12-02T14:39:25.002+05:30

Error: The error code 101505 means the HTTP connection initiated by the ESB has been terminated at the backend. According to the log you can determine whether message has been completely written to the backend prior to the connection close (See [Status SendingCompleted : true] in the log.) Users will usually get an error message such as the following. { fault: { code: "101505" type: "

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0Bloomington, IN, USA39.165325 -86.52638569999999239.066844 -86.68774719999999 39.263806 -86.3650242tag:blogger.com,1999:blog-1943956040996422309.post-26576917803868622962014-11-29T14:12:00.000+05:302014-12-17T03:38:27.705+05:30

The WSO2 Carbon products provides users with a browser based management console to administer the WSO2 products. All the WSO2 products comes with a management console to make the administration easier. When hosting the products ready for production, it's imperative to restrict the access to the mgt console from the external network. Following steps shows how to restrict the access to WSO2

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com2tag:blogger.com,1999:blog-1943956040996422309.post-40341114884375741162014-08-05T20:58:00.001+05:302014-08-08T07:43:40.882+05:30

JSF web applications can be fronted by a reverse proxy just like any other applications, except when the reverse proxy has a different context path compared to the application server that this JSF webapp is deployed to. Look at the following HTML content of a JSF Forms application. The 'action' URL of the form begins with a forward-slash '/'. This URL is actually a absolute url without the

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-76801641424619132632014-05-27T17:34:00.004+05:302014-05-27T19:01:00.372+05:30

Following guide describes how to invoke the STS Service in WSO2 Identity Server using a CXF STS client. The STS Client is configured via Spring. As I have noticed, CXF STS client fails to invoke the STS service if you use the wso2carbon-sts wsdl to generate the client. So, I have followed a different approach. Pre-requisites: WSO2 Identity Server 4.6.0 or latter Apache CXF 2.7.x

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-82415951906309062472014-05-02T19:58:00.000+05:302014-05-02T20:06:20.665+05:30

In GIT, there are different requirements to revert changes. This includes reverting local changes in your working copy, revert a commit already made, rewrite already pushed GIT history etc. I'll show you how to do these in this blog. The `git log` I have used can be found at the end of this article. To temporarily go back to a old revision, fool around, then come back to where you are,

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-78238342182214612332014-02-10T13:23:00.000+05:302014-02-10T13:25:00.681+05:30

When you were upgrading your WSO2 ESB pfrom 4.7.0 or older version to 4.8.0, you might notice the following issue.  Caused by: org.wso2.carbon.CarbonException: Axis Module not found for : activation-2.1.2 This error happens if you migrate the ESB_HOME/repository/deployment/server/servicemetafiles/ folder to the ESB 4.8.0 or a later version. The reason is that activation module is not

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-32011502472673985542014-02-01T20:47:00.000+05:302014-02-01T21:15:52.704+05:30

It's a common requirement for users of WSO2 to combine multiple WSO2 products together everything can be run within one JVM instance. Because of component architecture of WSO2 Carbon, you can combine features from several into one product which would help some deployments. Some of the common products that get merged together are AS + DSS + BPS, ESB + IS, BAM + CEP. The default way to install

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com3tag:blogger.com,1999:blog-1943956040996422309.post-47975375346835662312014-01-22T16:31:00.000+05:302014-02-10T13:24:45.660+05:30

There is sometimes a need to point WSO2 ESB to two separate ActiveMQ instances which are independent from each other. So, there will be different queues in these ActiveMQ instances. And, in the proxy configuration we can specify which ActiveMQ instance to use. Following samples explain how to do this. While this blog post focus on ActiveMQ, you follow quite the same steps for other message

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-37879693779184934142013-08-27T16:56:00.000+05:302013-08-27T16:56:04.768+05:30

As you know, we can't perform svn commands on a Subversion 1.6 working copy using a Subversion 1.7 client. But in Ubuntu 13.04, the default Subversion package is 1.7. 1.7 is certainly far superior in comparison to 1.6 in terms of speed. But I need to be able to do svn operations on 1.6 working copies. So, I needed two versions of subversion client. The only way I found for this is the following

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com3tag:blogger.com,1999:blog-1943956040996422309.post-2621129342105134632013-07-18T11:20:00.002+05:302014-02-10T13:25:38.408+05:30

Apache CXF has added out-of-the-box support for WS-Discovery for CXF based JAX-WS and JAX-RS services starting from CXF 2.7.x versions. This post describes how to add this support to WSO2 Application Server with WSO2 Governance Registry (GReg) acting as the DiscoveryProxy receiver. All the WSO2 Carbon-based service hosting products like WSO2 Application Server supported WS-Discovery for

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com1tag:blogger.com,1999:blog-1943956040996422309.post-92205090414992811102013-04-29T22:25:00.000+05:302013-04-29T22:26:24.215+05:30

Recently, I've been getting some queries on how to change the height of the docbook webhelp html output. This has been straight forward in the previous releases where, where you just change the CSS height property of #header, #content, and #leftnavigation. But starting from Docbook xsl release of 1.78.0, you need to do an additional change to get it working because of the introduction

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com2tag:blogger.com,1999:blog-1943956040996422309.post-42684164050847713182013-04-26T19:08:00.001+05:302013-04-26T22:19:04.561+05:30

With WSO2 ESB 4.6.0 release, we have seen lot of improvements in several areas including the Passthru transport which provides far better performance compared to the NIO transport. The comparison include the latest ESBs of Talend, Mule and WSO2 ESB 4.5.1 vs WSO2 ESB 4.6.0. We have chosen to do the benchmark on two different WSO2 ESB versions to show the performance gain we have received. You can

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com1Palo Alto, CA, USA37.413254967914419 -122.1288299560546937.36281946791442 -122.20951095605469 37.463690467914418 -122.04814895605469tag:blogger.com,1999:blog-1943956040996422309.post-56314124095423139382013-04-25T02:57:00.002+05:302013-04-26T19:11:35.584+05:30

I always wanted to run soapui load tests via command line because then I could run it on a remote machine that I SSH to. I don't want to run it on my machine because it slows down the machine considerably, so I can't do my day-to-day work with it. That will also affect the result of soapui. Recently, I wanted to re-produce a OOM issue in WSO2 ESB. So, the setup was, the ESB instance was

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com4tag:blogger.com,1999:blog-1943956040996422309.post-32829376398299522892013-04-23T02:28:00.000+05:302013-05-01T19:54:01.876+05:30

Here, I'm going to discuss how to generate a p2-repo for custom, user-written WSO2 components, and features. This can be easily achieved using the maven plugin, carbon-p2-plugin, that WSO2 have written.First, you may have a look at Creating-your-own-wso2-carbon-components webinar to know how to write carbon components, and a feature for those components. It covers quite a lot of

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com2tag:blogger.com,1999:blog-1943956040996422309.post-60042257555823993252013-03-28T01:35:00.001+05:302013-05-01T20:45:08.650+05:30

WSO2 Application Server 5.1.0 has introduced a major changes to the Webapp classloading mechanism with a new concept called configurable Runtime Environments. This provides solutions to classloading issues that was present is previous releases. Now, the users will be able to manipulate the webapp dependencies in a fine-grained manner. The current webapps will work just fine with this release,

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com3Palo Alto, CA, USA37.4418834 -122.1430194999999837.239989900000005 -122.46574299999997 37.6437769 -121.82029599999998tag:blogger.com,1999:blog-1943956040996422309.post-52182538185528756002013-03-23T18:45:00.000+05:302013-03-29T19:19:57.706+05:30

With the release of WSO2 Application Server (AS) 5.1.0 which is based on Carbon kernel 4.1.0, we have done major upgrades to the dependent jars used by WSO2 AS. Major upgrades include some long waited things like Servlet 3.0, JSP 2.2. Following is a list of upgraded versions of built-in jars inside WSO2 AS. table.tableizer-table { border: 1px solid #CCC; font-family: Arial, Helvetica,

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-8893509813708226852013-02-12T17:33:00.000+05:302013-03-29T17:33:24.317+05:30

Are you getting the NativeWorkerPool uncaught exception, and is unable to determine why this happens in WSO2 Enterprise Service Bus (ESB). If so, read on. There can be several issues that could lead to NativeWorkerPool exception. So, to determine the actual cause for this, you should read the remaining stack trace.  For example, you may see an exception like the following. [1] There, if

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com1tag:blogger.com,1999:blog-1943956040996422309.post-50716178421862299352013-01-20T17:22:00.000+05:302013-03-29T17:23:52.476+05:30

Just wanted to point out that there is a difference in API of removing a child between Axiom and DOM. The API of removing a child from a xml tree is different between Axiom and DOM. In DOM, we do following to remove a child. childNode.getParentNode().removeChild(parentNode); where childNode is an org.w3c.dom.Node instance. Basically, what the above does is, when you want to remove

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-85637072374716112212012-10-31T11:47:00.000+05:302012-10-31T12:19:32.025+05:30

I and Pradeep did a webinar on Deployment Synchronizer feature of WSO2 products with focus on practical aspects with a demonstration on setting up a minimal wso2 cluster setup w/ Deployment Synchronizer enabled. This covers most of the details that are needed to know on this subject. I did the Demonstration while Pradeep Fernando covered the technical aspects. You can view the slides

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com0tag:blogger.com,1999:blog-1943956040996422309.post-34595803280056025952012-10-08T17:09:00.001+05:302013-03-29T18:56:15.658+05:30

This tutorial shows how to clear the JMS queues of Cassandra. It should be noted that this method clear all the queues; you can't clear queue of your selection. This is useful where you have sent a message, and while it's in the queue something went wrong. There could be errors in processing the message due to incorrect settings etc. Since the queues are accessed FIFO (First-In-First-Out), if

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com2tag:blogger.com,1999:blog-1943956040996422309.post-16531810057740357792012-10-04T16:52:00.000+05:302012-10-31T11:48:35.226+05:30

This applies when you are using WSO2 ESB 4.5.0+ and WSO2 MB 2.0+. In WSO2 Message Broker 2.0, we use Andes as the message broker, an extended version of QPid. The format to use when defining a JMS endpoint is like follows. Remember The configuration will be different if you are not using Andes. jms:/MaterialMasterProxy1?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com1tag:blogger.com,1999:blog-1943956040996422309.post-52986974319826568642012-10-02T11:51:00.000+05:302012-10-31T12:17:14.194+05:30

Every Linux user is familiar with file copy command, cp (copy). As an user who uses this frequently in a day, I can't help but wonder about possible alternatives to cp. CP is terrible when copying large number of files that are small in size. So, after digging in the internet, I found the following command to be a little more faster than cp command when it comes to copying smaller files.

Anonymoushttp://www.blogger.com/profile/06660275787369025626noreply@blogger.com2