[
https://issues.jboss.org/browse/LOGMGR-135?page=com.atlassian.jira.plugin...
]
James Perkins commented on LOGMGR-135:
--------------------------------------
This can be tricky to get right is the main problem. Logging is configured before anything
else in the container. You can see in that example that it attempts to initialize from
JNDI and if the session can't be initialized nothing is logged. If a failure occurred
before the mail subsystem was up and running then the error would never be handled with
this handler. Nothing would be logged via this handler until both EJB, JNDI and mail
services are started.
I'm not 100% sure, but I think {{org.jboss.ejb.client.naming}} is for remote EJB JNDI
lookups. This means that both the EJB and mail subsystems would be required for the log
handler to work. Maybe that's not a huge deal.
Create an EmailHandler
----------------------
Key: LOGMGR-135
URL:
https://issues.jboss.org/browse/LOGMGR-135
Project: JBoss Log Manager
Issue Type: Feature Request
Components: core
Affects Versions: 2.0.3.Final
Reporter: Yann Le Tallec
Labels: task
It would be useful if there were a built-in EmailHandler that uses wildfly/jboss default
email service.
This thread:
https://developer.jboss.org/wiki/CreatingACustomLoggingHandlerInJBOSSAs71...
suggests an approach but having an "official" handler would certainly be more
robust.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)