[jboss-jira] [JBoss JIRA] (JBRULES-3572) Logging is not working on JbossAS 7.1

[Geoffrey De Smet (JIRA)]

    [ https://issues.jboss.org/browse/JBRULES-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706804#comment-12706804 ] 

Geoffrey De Smet edited comment on JBRULES-3572 at 7/19/12 11:05 AM:
---------------------------------------------------------------------

1 and 2 could be done in the jboss AS specific assembly: https://github.com/droolsjbpm/guvnor/blob/master/guvnor-distribution-wars/src/main/assembly/assembly-guvnor-jboss-as-7_0.xml

But, personally, I don't know if I like "2- Remove log4j.xml from WEB-INF\classes"
Why? Because the guvnor war is an end-user application (unlike drools-core, drools-planner or jbpm-flow which are not end-user apps and should therefor have no logging configuration in them).
So, as an end-user, you expect the logging of guvnor to be sensible defaulted and happening.
This means A) it goes to a file (not /dev/null) and B) it's probably filtered by default on level WARN or maybe INFO (but not DEBUG or TRACE).
So C) it guarantees that a guvnor warn message shows up in a file somewhere, even if the user is using it out-of-the-box.

If jboss AS 7 logging does A), B) and C) automatically if we fulfill 1) and 2) in the AS specific assembly, then I am +1 for such changes (and I 'll merge a good pull request with such changes).

                
      was (Author: ge0ffrey):
    1 and 2 could be done in the jboss AS specific assembly: https://github.com/droolsjbpm/guvnor/blob/master/guvnor-distribution-wars/src/main/assembly/assembly-guvnor-jboss-as-7_0.xml

But, personally, I don't know if I like "2- Remove log4j.xml from WEB-INF\classes"
Why? Because the guvnor war is an end-user application (unlike drools-core, drools-planner or jbpm-flow which are not end-user apps and should therefor have no logging configuration in them).
So, as an end-user, you expect the logging of guvnor to be sensible defaulted and happening.
This means A) it goes to a file (not /dev/null) and B) it's probably filtered by default on level WARN or maybe INFO (but not DEBUG or TRACE).
So C) it guarantees that a guvnor warn message shows up in a file somewhere, even if the user is using it out-of-the-box.

If jboss AS 7 logging does A), B) and C) automatically if we fulfill 1) and 2) in the AS specific assembly, then I am +1 for such changes.

                  
> Logging is not working on JbossAS 7.1
> -------------------------------------
>
>                 Key: JBRULES-3572
>                 URL: https://issues.jboss.org/browse/JBRULES-3572
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-guvnor
>    Affects Versions: 5.4.0.Final
>         Environment: JbossAS 7.1.2
> guvnor-distribution-wars-5.4.0.Final-jboss-as-7.0.war
>            Reporter: Cristiano Nicolai
>            Assignee: Mark Proctor
>              Labels: jboss-as7, jboss-logging, log4j, logging, slf4j
>
> Hi,
> I'm trying to get the Guvnor logging to be managed by Jboss Logging (logging subsystem) on AS 7.1.2.
> I tried to play around with
> jboss-deployment-structure.xml to include and exclude the logging libraries
> from Jboss and also removing the logging jar's from WEB-INF/lib without
> success. Also tried to tweak the log4j.xml on WEB-INF/classes.
> Here are some documentation that I have tried:
> https://docs.jboss.org/author/display/AS71/How+To#HowTo-HowdoIuselog4j.propertiesorlog4j.xmlinsteadofusingtheloggingsubsystemconfiguration%3F
> https://docs.jboss.org/author/display/AS71/Logging+Configuration
> Thanks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira