ok, it took me a bit but i've learned more from creating a minimal example.
i now am not sure if this is actually an issue or not.
the problem occurs when you create a static logger within an EJB class, in
my case a Stateless EJB:
ex:
@Stateless
public class SillyBean {
static final Logger logger = LogManager.getLogger();
.
.
.
However, the problem goes away when you change this to not be static:
@Stateless
public class SillyBean {
final Logger logger = LogManager.getLogger();
.
.
.
I admit, I don't know whether you *SHOULD* be able to create a static logger
in an EJB... so I'm not sure if this is a problem or not. What do you think?
--
View this message in context:
http://openejb.979440.n4.nabble.com/log4j2-initialized-too-early-tp4668307p4668313.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
