Bug 1040270

Summary: 20 % of log startup messages are warnings
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Jiri Pechanec <jpechane>
Component: ConfigurationAssignee: Julian Coleman <jcoleman>
Status: ON_QA --- QA Contact: Matej Melko <mmelko>
Severity: high Docs Contact:
Priority: low    
Version: 6.1.0CC: aileenc, atangrin, ganandan, ldimaggi, mweiler, soa-p-jira
Target Milestone: ER2   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Up to twenty percent of the messages in the error log are warnings, stemming from multiple parts of the product. As a result, the log is very cluttered and of limited use to users.
 Story Points: ---
Clone Of: Environment:
Linux, Java 7, ER7
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Server log file - 15% of lines contain WARN none

Description Jiri Pechanec 2013-12-11 05:04:07 UTC 
When ER7 starts in genertas a lot of warn messages - 20 % of total of messages printed.

They belongs to multiple groups
 - switchyard-bpel-console.war, deployment.overlord-rtgov.war, "deployment.s-ramp-server.war and s-ramp-ui.war are using private or unsupported modules
 - org.picketlink.identity.federation about non-persisted token
 - few single lines
05:52:59,937 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
05:53:03,744 WARN  [org.hibernate.internal.SessionFactoryImpl] (ServerService Thread Pool -- 54) HHH000008: JTASessionContext being used with JDBCTransactionFactory; auto-flush will not operate correctly with getCurrentSession()
 - potential bug in DTGov
05:53:09,989 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-6) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @Inject @ApplicationScoped private org.overlord.dtgov.taskapi.TaskApi.processEngineService
05:53:09,990 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-6) WELD-001440 Scope type @javax.enterprise.context.ApplicationScoped() used on injection point [field] @Inject @ApplicationScoped private org.overlord.dtgov.jbpm.ejb.ProcessBean.processEngineService
 It seems that the code depends on injection of dependency form a specific scope - which is not allowed

The startup log is now thus very cluttered and of a limited use.
Comment 1 Julian Coleman 2013-12-16 16:07:43 UTC 
To fix all of these, we'd have to classify them by project and check them there.
Note, that we can't fix those from:
  https://bugzilla.redhat.com/show_bug.cgi?id=1036225
until we pick up a fixed EAP (6.2?).
Comment 2 Len DiMaggio 2014-07-15 20:01:08 UTC 
Just looked at the GA bits - see attached log file. The log has 782 lines of which 115 include "WARN." 

This works out to be just under 15% - still pretty high for an OOTB server install. Can we improve this for FSW 6.1?
Comment 3 Len DiMaggio 2014-07-15 20:02:01 UTC 
Created attachment 918245 [details]
Server log file - 15% of lines contain WARN
Comment 4 Len DiMaggio 2015-03-02 16:51:15 UTC 
QE should retest with 6.2.ER1 - are the number of WARN messges reduced?