Comment 2Enrique Gonzalez Martinez
2014-11-13 09:33:11 UTC
The patching tools is checking whenever the SHA1 hash of the current installation file matches the expected to be patched (this hash is included in the patch.xml in patch file).
This part of the procedure is done in the class AbstractPatchingTask::prepare()
The system tries to backup the file/subsystem and calculate the hash of the current file/subsystem installed. There are two different causes for this error:
1) This is not possible because the file is missing (the installer does not copy them). This happens for bin/client/jboss-cli-client.jar, bin/client/jboss-client.jar, bin/jconsole.sh
2) When the native libs are installed, it adds a new folder inside org.jboss.as.web:main (for including the dll in windows). This changes the hash calculation. The hash does not match the expected hash in the patch.xml. This happens for the org.jboss.as.web
In both cases the file installed does not match the expected to be replaced in the patch.xml. therefore the patch tool raises a conflict.
The error after the workaround is because it wasn't possible to backup the files (they were missing in first place) and when the system tries to recover them, they are not there.
From my point of view:
1) Files missing: this is an error in the base installation using the installer. It should match the same content as the zip install.
2) Optional packages (i.e: native libraries): in this case requires design solution. The installation of the natives libraries changes the hash to be checked by the patch tool.
Comment 6Dimitris Andreadis
2015-02-03 21:03:24 UTC