Bug 1078500
| Summary: | SEVERE error in Server.log file: JSF1051 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Mike Foley <mfoley> | ||||
| Component: | Core Server | Assignee: | Jay Shaughnessy <jshaughn> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | JON 3.2 | CC: | jshaughn, lzoubek, spinder | ||||
| Target Milestone: | ER04 | ||||||
| Target Release: | JON 3.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-12-11 14:01:18 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This is not a CP1 regression, message is present in 3.2.0.GA log as well As per comment 1, 3.2.0.GA issue. Resetting target version accordingly. I'll probably add this to the log filter, i don't think it's an actual problem, but I'll do a little investigation first. I think this may be a regression in EAP 6.3. We can see in Bug 899534 that this was fixed in EAP6.0 but now the same issue is what we are seeing. In RHQ 4.11 jboss packaged jsf-impl-1.2_15-jbossorg-2.jar for the 1.2 module. But in 4.12/EAP6.3 I now see jsf-impl-1.2_15-b01-redhat-8.jar. This is a different jar, smaller, definitely not the same thing. It may have other benefits but seems to have re-introduced the problem. Having said that, I'm not sure the SEVERE message actually indicates an issue for us, given that we don't use very much of the JSF app (portal-war) anymore. I don't exactly know what portal war has defined to trigger the issue. Actually, reading back I guess it's not a regression 6.3, because this was reported against 3.2.0 (see Comment 1) when we were layered on something else, I think AS7.2.1.Final-redhat-10. It was working back with RHQ 4.11 afaik, and that was layered on jboss-as-server-7.2.0.Alpha1-redhat-4.jar. Anyway, we have not really had any issues reported against portal war that I think relate back to this, so I think the solution for us is to just filter this message out of the log. I'll likely generate an EAP BZ for then to look at. Reported Bug 1141373 against EAP.
master commit 79551dd1c3df5749c6b9d1ba5155ea685e36dde7
Author: Jay Shaughnessy <jshaughn>
Date: Mon Sep 15 13:21:49 2014 -0400
This is generated due to, I think, EAP Bug 1141373. The error does not
seem to negatively affect rhq/jon, so at this point I'm just filtering
out the message from the server log.
release/jon3.3.x commit 9655ffe0c8594e49d5ba3f9010ea36db4fff8a96
Author: Jay Shaughnessy <jshaughn>
Date: Mon Sep 15 13:21:49 2014 -0400
(cherry picked from commit 79551dd1c3df5749c6b9d1ba5155ea685e36dde7)
Signed-off-by: Jay Shaughnessy <jshaughn>
Moving to ON_QA as available for test with build: https://brewweb.devel.redhat.com/buildinfo?buildID=388959 |
Created attachment 876571 [details] server log Description of problem: SEVERE message logged in server.log file 13:46:40,221 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 60) JSF1051: Service entry 'org.jboss.as.jsf.injection.JSFInjectionProvider' does not extend DiscoverableInjectionProvider. Entry will be ignored. Version-Release number of selected component (if applicable): JON 3.2.1 aka JON 3.2 CP How reproducible: 100% Steps to Reproduce: 1. install JON 3.2 GA 2. install CP 3. Actual results: 13:46:40,221 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 60) JSF1051: Service entry 'org.jboss.as.jsf.injection.JSFInject <mfoley> ionProvider' does not extend DiscoverableInjectionProvider. Entry will be ignored. Expected results: no SEVERE messages logged Additional info: