Hello! I know this is a well documented topic so apologies in advance if my understanding here is fundamentally flawed or if the answer is obvious (this knowledge base is for sure outside of my wheel house), I did some research but was unable to find information on the particular configuration I'm looking to achieve (if possible). Some context, all the output from every WAR in a given deployment directory of a node is currently written to the same server.log which appears defined in the standalone-full.xml. In any given deployment directory there may be several different wars being deployed e.g: a.war, b.war and c.war. The desired change is to create log4j.properties (or .xml) for each war e.g.: a-log4j.properties, b-log4j.properties, c-log4j.properties that would result in, for example, a-server.log, b-server.log, and c-server.log. I've tested my log4j.properties file and know that it is correct. Currently, all of these wars have, as I understand it, an implicit dependency on the JBoss org.apache.log4j module. I can confirm as much by adding an exclusion for that module to my jboss-deployment-structure.xml and watch the deployment fail because it cannot initialize log4j.
The change I'm hoping to achieve is to continue to use the JBoss log4j module but to provide external (re: outside the war) log4j.properties or log4j.xml in the hope of eventually doing run time log-level changes on the fly, though whether or not that is possible I'm not sure yet.
Is it possible to use the provided JBoss org.apache.log4j module as well as an external log4j.properties or .xml (external in the sense that it lives outside of my WARs)? For example, I've seen many examples (and I have been able to successfully reproduce) that solve this exact issue by performing the following:
1) Breaking the implicit dependency of the log4j module provided by JBoss via a jboss-deployment-structure.xml such as:
<?xml version="1.0" encoding="UTF-8"?>
2) Adding the log4j.1.x.jar to my WEB-INF/lib/
3) Configuring my code so that each war will reference the specific external log4j.properties via run-time parameters.
I'm working inside a legacy code base where I'm trying to avoid adding any new dependencies to these existing wars so I'm basically trying to avoid the above second step. As it stands currently, if I remove the above first and second step (that is to say, I continue to use the jboss log4j module) then the wars will not write to my log file. When I do perform the first two steps, the wars write correctly to their specific log files.
I had to summarize my particular query in a few questions it'd be:
1) Is it possible to use both the JBoss org.apache.log4j module (thus not having to add log4j to the class path of my war) and an external log4j properties config per war?
2) If so, what would that configuration look like?
3) If not, why is that not possible?
Thanks again for taking a look at this post, and do forgive my ignorance if I've gotten anything wrong