Double check the profile you're adding the configuration to and the profile you're launching.
James R. Perkins
Thanks for your reply James.
Yes this was one of the fiorst things I had verified by DEV OPS.
My bad, it turned to be an issue where I had a config locally that was different from the war in the upper envs.
JBOS-DEPLOYMENT-STRUCTURE.xml had an exclusion filter blocking log4j libraries from the classloader.