If you're seeing this exception in the Oozie Spark action launcher log, please ignore it as it may be expected in a secure environment. If your launcher/action is truly failing, then the real exception will lie in the logs that follow/other parts of the log - the log4j permission error can be treated as a red herring as you investigate.
The easiest workaround for this is to copy the log4j.propeties file to oozie.sharelib.path. You can even add all the extra files and jars which are required in the yarn container when scheduling via oozie.
