Skip to main content

How to revert patches applied to WSO2 Carbon server

WSO2 Carbon based products are released with a well defined strategy for applying fixes to the system. If any customer faces an issue in the server, patches will be provided until that issue is fixed in the next product release. Once the patches are applied in to the server, it will fix that respective issue. In the practical world, there can be situations where users might want to revert the patches and restore the system into original status in terms of Carbon product. This blog post will describe the correct way to revert a patch applied in to a Carbon server.

How to apply a patch?

(i)  Shutdown the server, if you have already started.

(ii) Copy the wso2carbon-version.txt file to <CARBON_SERVER>/bin.

(iii) Copy the patchXXXX folder to  <CARBON_SERVER>/repository/components/patches/

(iv) Restart the server with :
       Linux/Unix :  sh wso2server.sh -DapplyPatches
       Windows    :  wso2server.bat -DapplyPatches


How to revert a patch?

1.) patch0000 folder is created the first time you apply a patch to a clean product, so this directory will actually contain the original jars that came with the release.

2.) If you apply a new patch, for instance patch0100 with synapse-core-2.1.0-wso2v8.jar inside, this jar will be copied over to the plugins directory.

3.) If you apply another patch, for instance patch0200 which also contains synapse-core-2.1.0-wso2v8.jar, this new jar will be copied over to the plugins directory.

4.) Now if you want to remove the patch0200 from your server, just remove the folder patch0200 from
<CARBON_SERVER>/repository/components/patches/ folder and start the server with -DapplyPatches option. Here synapse-core-2.1.0-wso2v8.jar inside patch0100 will be copied over to the plugins directory. Likewise, if you remove patch0100, leaving patch0200, there will be no change (i.e. plugins directory will contain the synapse-core jar from patch0200).

So in this manner, we can actually revert patches all the way to the original jars.

As for the incorrectly named jar in patch folder, -DapplyPatches corrects the names before applying as it cross checks the file name with the bundle name and version from the Manifest file.
Labels:

Comments

Post a Comment

Popular posts from this blog

Understanding Threads created in WSO2 ESB

WSO2 ESB is an asynchronous high performing messaging engine which uses Java NIO technology for its internal implementations. You can find more information about the implementation details about the WSO2 ESB’s high performing http transport known as Pass-Through Transport (PTT) from the links given below. [1] http://soatutorials.blogspot.com/2015/05/understanding-wso2-esb-pass-through.html [2] http://wso2.com/library/articles/2013/12/demystifying-wso2-esb-pass-through-transport-part-i/ From this tutorial, I am going to discuss about various threads created when you start the ESB and start processing requests with that. This would help you to troubleshoot critical ESB server issues with the usage of a thread dump. You can monitor the threads created by using a monitoring tool like Jconsole or java mission control (java 1.7.40 upwards). Given below is a list of important threads and their stack traces from an active ESB server.  PassThroughHTTPSSender ( 1 Thread )
2 comments
Read more

WSO2 ESB tuning performance with threads

I have written several blog posts explaining the internal behavior of the ESB and the threads created inside ESB. With this post, I am talking about the effect of threads in the WSO2 ESB and how to tune up threads for optimal performance. You can refer [1] and [2] to understand the threads created within the ESB. [1] http://soatutorials.blogspot.com/2015/05/understanding-threads-created-in-wso2.html [2] http://wso2.com/library/articles/2012/03/importance-performance-wso2-esb-handles-nonobvious/ Within this blog post, I am discussing about the "worker threads" which are used for processing the data within the WSO2 ESB. There are 2 types of worker threads created when you start sending the requests to the server 1) Server Worker/Client Worker Threads 2) Mediator Worker (Synapse-Worker) Threads Server Worker/Client Worker Threads These set of threads will be used to process all the requests/responses coming to the ESB server. ServerWorker Threads will be used to pr
3 comments
Read more

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte
1 comment
Read more