![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
1.7.12 |
|
Assignee:
|
SLF4J developers list
|
|
Components:
|
Core API |
|
Created:
|
23/Apr/15 11:23 AM
|
|
Description:
|
When using SLF4J in a WebSphere Application Server with a security policy that forbids "createSecurityManager", startup of SLF4J fails with a java.security.AccessControlException. Since you can't override the Constructor of SecurityManager and disable this check (which would defeat the purpose of the SecurityManager), I think the best way to handle this is Lazy Initialisation of SECURITY_MANAGER in org.slf4j.helpers.Util.
I don't know how performance-critical this is, but since it's currently only used for a debugging feature that can be disabled in a production environment, I see no harm.
|
|
Environment:
|
WebSphere 8.0
|
|
Project:
|
SLF4J
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Tobias Gruetzmacher
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
_______________________________________________
slf4j-dev mailing list
slf4j-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-dev
