[GLASSFISH-3100] LogManager has global scope Created: 31/May/07 Updated: 19/Sep/12
|Fix Version/s:||not determined|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Operating System: All
The java.util.logging.LogManager used within the AppServer appears to have
The simple test I performed was I used NetBeans to create a base Enterprise App.
Logger log = Logger.getLogger("SessionBean");
I also did a similar thing in a simple servlet. The simple servlet also called a
I also created a seperate, standalone test WAR that did a similar thing.
The servlets and session beans simply dump the contents of the LogManager:
LogManager lm = LogManager.getLogManager();
After running the various experiments, it was soon obvious that the LogManager
It was also obvious that many of the classes from the Appserver had Loggers
There is a concern with common libraries deployed into disparate applications
Also, there is a potential security threat in that an application can be
And far be it for me to fixate on mere passwords, but in the health care
As I see there seems to be movement to try and get Glassfish in to a public
|Comment by bertschultheiss [ 09/Sep/10 ]|
|Comment by Tom Mueller [ 06/Mar/12 ]|
Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.
|Comment by vindum [ 19/Sep/12 ]|
I agree. This is indeed a problem. I'm implementing log4j using slf4j, and this problem makes jul-to-slf4j send log messages through appenders from other applications than the ones they originated from. It makes tracking log messages very difficult.