Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-16332

JSF application undeploy generates SEVERE log entries

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 26.1.0.Final
    • JSF
    • Hide
      • Deploy both greeter and tasks-jsf quickstarts from EAP quickstarts.
      • From the JBoss CLI, redeploy tasks-jsf.war and observe the SEVERE log entries. 
        [standalone@localhost:9990 /] /deployment=tasks-jsf.war:redeploy
{"outcome" => "success"}
      • The SEVERE logs will also appear sometimes when stopping EAP, probably depending on the order the applications get undeployed.

      NOTE: there is also a WARNING that appears but that is a separate issue (JBEAP-20561).

      Show
      Deploy both greeter and  tasks-jsf quickstarts from EAP quickstarts . From the JBoss CLI, redeploy  tasks-jsf.war and observe the SEVERE log entries. [standalone@localhost:9990 /] /deployment=tasks-jsf.war:redeploy {"outcome" => "success"} The SEVERE logs will also appear sometimes when stopping EAP, probably depending on the order the applications get undeployed. NOTE: there is also a WARNING that appears but that is a separate issue ( JBEAP-20561 ).
    • ---
    • ---

      When JBoss EAP is stopped after deploying multiple JSF applications, the following SEVERE logs appear sometimes.

      2022-04-25 09:50:00,397 SEVERE [javax.faces] (ServerService Thread Pool -- 5) Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI?
2022-04-25 09:50:00,398 SEVERE [javax.faces] (ServerService Thread Pool -- 5) Unable to call @PreDestroy annotated methods because no InjectionProvider can be found. Does this container implement the Mojarra Injection SPI?

      These logs seem to be related to WFLY-2594, which according to WFLY-3243 should have been included in pre-EAP 7.0 "2.2.6-jbossorg-4 version of jsf-impl". However, it looks like it was reverted (WFLY-3277) due to a memory leak.

      If it's not possible to fix the cause of the log entries, perhaps lowering the priority from SEVERE would be good.

              rhn-support-ivassile Ilia Vassilev
              rhn-support-ivassile Ilia Vassilev
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: