0 Replies Latest reply on Sep 29, 2015 3:03 AM by Marcial Atiénzar Navarro

    Understanding log.error on chainned EJB calls

    Marcial Atiénzar Navarro Newbie



      We've an appender to log errors to jira. But we've notice that when we ha've a chainned of ejb calls like this: EJB 1 --> EJB 2 --> EJB 3 --> EJB 4, we've 4 entries of log.error for every call, with this text:


      ERROR [org.jboss.as.ejb3.invocation] (default task-87) WFLYEJB0034: EJB Invocation failed on component


      And therefore, we've 4 issues created on jira.

      We've solved this by dissabling this logger to our custom appender:

      <logger category="org.jboss.as.ejb3.invocation">
           <level name="OFF"/>
                <handler name="KYRIAN"/>



      But we don't know if this is the best aproach. We've a ExceptionMapper to log rest errors to log.error


      Is this correct this approach? We're using wildfly 9.0.1, it's correct to have 4 log.error for an error on EJB 4?