Having more than one jar with the same classes in the same classloader is always going to cause problems. There's no "priority" that you can assign. Since it's production, it's much more important that only the right jar (containing) the patch is placed in the application's classloader scope.
I set the following property:
Patch URL is shown on the console while server startup, but still the patch changes are not getting applied.
Here is the how the app is deployed:
/home/qa/Myapp/build/deploy/app.war/WEB-INF/lib (contains all jar files including application jar file)
/home/qa/Myapp/build/deploy/app.war/jars (contains patch jar)
Is there anything wrong