Due to this behavior the changed files are getting caught or blocked by the security tool (BIT9 parity). It is because the new generated has code of the changed files are not recognized in the whitelist of the security tool.
Do you have any idea what causes the change of these cache files? We have not seen the change on these files and lately jboss internal logic start behaving differently,i.e. updates the files content.