Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1141373

Summary: SEVERE message "'org.jboss.as.jsf.injection.JSFInjectionProvider' does not extend DiscoverableInjectionProvider" in server.log file
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Jay Shaughnessy <jshaughn>
Component: JSFAssignee: Farah Juma <fjuma>
Status: CLOSED NOTABUG QA Contact: Ron Šmeral <rsmeral>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.3.0CC: amelicha, jshaughn, maschmid, ssilvert
Target Milestone: ---   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-03 15:54:54 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:
Description Flags
Clip of JON server.log showing error none

Description Jay Shaughnessy 2014-09-12 20:32:25 UTC 
Description of problem:

It seems that Bug 899534 may have resurfaced in more recent versions of EAP.  In JBossON we're seeing the same message as reported in the prior BZ, at startup, in our server log.  The JBossON BZ is Bug 1078500.

We are currently layered on EAP 6.3 although it was reported against a prior version, which was layered on jboss-as-server-7.2.1.Final-redhat-10.  Both of these problem versions look to have packaged jsf-impl-1.2_15-b01-redhat-11.jar.

We did not see this problem on a community release, layered against jboss-as-server-7.2.0.Alpha1-redhat-4.  That release packaged jsf-impl-1.2_15-jbossorg-2.jar, mentioned in Bug 1078500 as being "good".

The problem message in the log is:

14:19:56,773 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 138) JSF1051: Service entry 'org.jboss.as.jsf.injection.JSFInjectionProvider' does not extend DiscoverableInjectionProvider.  Entry will be ignored.


The log message does not seem to map to an actual runtime issue for us, so at the moment this is not a high priority issue for us.  But it seemed useful to report this.

How reproducible:
Always

Steps to Reproduce:
See Bug 899534 or install JBossON 3.2.0.GA and start it.

Actual results:
SEVERE message.

Expected results:
No message.
Comment 1 Farah Juma 2014-09-19 23:26:59 UTC 
Please attach the EAP 6.3 server.log file.
Comment 2 Jay Shaughnessy 2014-09-24 18:28:20 UTC 
Created attachment 940877 [details]
Clip of JON server.log showing error
Comment 3 Farah Juma 2014-10-03 15:54:54 UTC 
It turns out that this issue is different from Bug 899534, where the main issue was that JSF 1.2 could not bind any NamedObject inside of the application scope. In this case, the main issue is that the appropriate JSF injection module isn't getting added to rhq-portal.war due to some missing configuration in rhq.ear's jboss-deployment-structure.xml file. (Starting with AS 7.2.0.Final, JSF injection was moved out into its own module.) Jay, to fix this, please make the following configuration changes in rhq.ear's jboss-deployment-structure.xml file:

1) Add the following to the <exclusions> section for rhq-portal.war:

<module name="org.jboss.as.jsf-injection" slot="main"/>

2) Add the following to the <dependencies> section for rhq-portal.war:

<module name="org.jboss.as.jsf-injection" slot="1.2" services="import"/>

With these configuration changes, the SEVERE error message (i.e., "Service entry 'org.jboss.as.jsf.injection.JSFInjectionProvider' does not extend DiscoverableInjectionProvider.  Entry will be ignored") should no longer occur.