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

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...
1 comment
Read more

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...
Post a Comment
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...
6 comments
Read more