1.1.1 Log4j Setup

View: New views
6 Messages — Rating Filter:   Alert me  

1.1.1 Log4j Setup

by dwqnhuah :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,
 I'm trying to log all of my log4j INFO messages to stdout, but no success yet, below is a how I'm setting it up
----------------------------------------------------------------------------------------------------
//log4j configuration
log4j = {
    // Example of changing the log pattern for the default console
    // appender:
    //
    appenders{
        console name:'stdout', layout:pattern(conversionPattern: '%c{2} %m%n')
    }
   
    info   'grails.app' // Try 1: Overall app level
    info   'grails.app.controller.com.wwt.rvacommit.web.RvaCommitController' // Try 2: RvaCommit Controllers
    info   'com.wwt.rvacommit.web.RvaCommitController' // Try 3: Just the artifact

    error  'org.codehaus.groovy.grails.web.servlet',  //  controllers
               'org.codehaus.groovy.grails.web.pages', //  GSP
               'org.codehaus.groovy.grails.web.sitemesh', //  layouts
               'org.codehaus.groovy.grails.web.mapping.filter', // URL mapping
               'org.codehaus.groovy.grails.web.mapping', // URL mapping
               'org.codehaus.groovy.grails.commons', // core / classloading
               'org.codehaus.groovy.grails.plugins', // plugins
               'org.codehaus.groovy.grails.orm.hibernate', // hibernate integration
               'org.springframework',
               'org.hibernate'

    warn   'org.mortbay.log'
}


Any thoughts? Thanks
Shikhar Mishra
---------------------------
World Wide Technology, Inc.

Re: 1.1.1 Log4j Setup

by greggobridges :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Mine, which works, looks like this (it looks like yours does not have the root defined?):

log4j = {
            appenders {
                console name:'stdout', layout:pattern(conversionPattern: '%d [%t] %-5p (%F:%L) - %m%n')
                rollingFile name:'rollingFile', maxBackupIndex:25, maxFileSize:'512MB', file:"Foo.log", layout:pattern(conversionPattern: '%d [%t] (%F:%L) - %m%n')

                error   'org.codehaus.groovy.grails.compiler.injection.DefaultGrailsDomainClassInjector',
                       ... <lots>...
                        'net.sf.ehcache'

                warn 'org.mortbay.log'

                debug "grails.app"   //our stuff
            }
            root {
                debug 'stdout', 'rollingFile'
                additivity = true
            }
         }




----- Original Message ----
From: dwqnhuah <shikhar.mishra@...>
To: user@...
Sent: Wednesday, September 16, 2009 12:41:13 PM
Subject: [grails-user] 1.1.1 Log4j Setup


Hi,
I'm trying to log all of my log4j INFO messages to stdout, but no success
yet, below is a how I'm setting it up
----------------------------------------------------------------------------------------------------
//log4j configuration
log4j = {
    // Example of changing the log pattern for the default console
    // appender:
    //
    appenders{
        console name:'stdout', layout:pattern(conversionPattern: '%c{2}
%m%n')
    }
   
    info   'grails.app' // Try 1: Overall app level
    info   'grails.app.controller.com.wwt.rvacommit.web.RvaCommitController'
// Try 2: RvaCommit Controllers
    info   'com.wwt.rvacommit.web.RvaCommitController' // Try 3: Just the
artifact

    error  'org.codehaus.groovy.grails.web.servlet',  //  controllers
               'org.codehaus.groovy.grails.web.pages', //  GSP
               'org.codehaus.groovy.grails.web.sitemesh', //  layouts
               'org.codehaus.groovy.grails.web.mapping.filter', // URL
mapping
               'org.codehaus.groovy.grails.web.mapping', // URL mapping
               'org.codehaus.groovy.grails.commons', // core / classloading
               'org.codehaus.groovy.grails.plugins', // plugins
               'org.codehaus.groovy.grails.orm.hibernate', // hibernate
integration
               'org.springframework',
               'org.hibernate'

    warn   'org.mortbay.log'
}


Any thoughts? Thanks
--
View this message in context: http://www.nabble.com/1.1.1-Log4j-Setup-tp25477189p25477189.html
Sent from the grails - user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: 1.1.1 Log4j Setup

by dwqnhuah :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thats was it, thanks a lot.
greggobridges wrote:
Mine, which works, looks like this (it looks like yours does not have the root defined?):

log4j = {
            appenders {
                console name:'stdout', layout:pattern(conversionPattern: '%d [%t] %-5p (%F:%L) - %m%n')
                rollingFile name:'rollingFile', maxBackupIndex:25, maxFileSize:'512MB', file:"Foo.log", layout:pattern(conversionPattern: '%d [%t] (%F:%L) - %m%n')

                error   'org.codehaus.groovy.grails.compiler.injection.DefaultGrailsDomainClassInjector',
                       ... <lots>...
                        'net.sf.ehcache'

                warn 'org.mortbay.log'

                debug "grails.app"   //our stuff
            }
            root {
                debug 'stdout', 'rollingFile'
                additivity = true
            }
         }




----- Original Message ----
From: dwqnhuah <shikhar.mishra@wwt.com>
To: user@grails.codehaus.org
Sent: Wednesday, September 16, 2009 12:41:13 PM
Subject: [grails-user] 1.1.1 Log4j Setup


Hi,
I'm trying to log all of my log4j INFO messages to stdout, but no success
yet, below is a how I'm setting it up
----------------------------------------------------------------------------------------------------
//log4j configuration
log4j = {
    // Example of changing the log pattern for the default console
    // appender:
    //
    appenders{
        console name:'stdout', layout:pattern(conversionPattern: '%c{2}
%m%n')
    }
   
    info   'grails.app' // Try 1: Overall app level
    info   'grails.app.controller.com.wwt.rvacommit.web.RvaCommitController'
// Try 2: RvaCommit Controllers
    info   'com.wwt.rvacommit.web.RvaCommitController' // Try 3: Just the
artifact

    error  'org.codehaus.groovy.grails.web.servlet',  //  controllers
               'org.codehaus.groovy.grails.web.pages', //  GSP
               'org.codehaus.groovy.grails.web.sitemesh', //  layouts
               'org.codehaus.groovy.grails.web.mapping.filter', // URL
mapping
               'org.codehaus.groovy.grails.web.mapping', // URL mapping
               'org.codehaus.groovy.grails.commons', // core / classloading
               'org.codehaus.groovy.grails.plugins', // plugins
               'org.codehaus.groovy.grails.orm.hibernate', // hibernate
integration
               'org.springframework',
               'org.hibernate'

    warn   'org.mortbay.log'
}


Any thoughts? Thanks
--
View this message in context: http://www.nabble.com/1.1.1-Log4j-Setup-tp25477189p25477189.html
Sent from the grails - user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Shikhar Mishra
---------------------------
World Wide Technology, Inc.

Recommended Way for per Site Configuration

by John Cladmore :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi all,

I looking for suggestions to solve what seems like a simple requirement.

I am developing a Grails application which will be deployed at several
locations.  The application will be one build, the only difference is
that it must generate registration numbers reflecting the site where it
is deployed.

Since the build will be the same, I know that I can't put this 'site
info' in the application.  So where would you recommend this information
be placed?

The easiest solution I can think of is to simply modify a 'site file' in
WEB-INF after the app is exploded by the app-server, since this won't be
accessible by the users.

Thanks.

.v

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: Recommended Way for per Site Configuration

by Robert Fischer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

JNDI.

~~ Robert Fischer, Smokejumper IT Consulting.
Enfranchised Mind Blog http://EnfranchisedMind.com/blog

Grails Expert Retainer Services
http://smokejumperit.com/grails-retainer/


John Cladmore wrote:

> Hi all,
>
> I looking for suggestions to solve what seems like a simple requirement.
>
> I am developing a Grails application which will be deployed at several
> locations.  The application will be one build, the only difference is
> that it must generate registration numbers reflecting the site where it
> is deployed.
>
> Since the build will be the same, I know that I can't put this 'site
> info' in the application.  So where would you recommend this information
> be placed?
> The easiest solution I can think of is to simply modify a 'site file' in
> WEB-INF after the app is exploded by the app-server, since this won't be
> accessible by the users.
>
> Thanks.
>
> .v
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: Recommended Way for per Site Configuration

by tomas lin :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I would put this information in conf/config.groovy and use
externalized configurations to override war defaults.

I.e., you would define an external config.groovy file for each of your
locations with a different registration number.

http://www.grails.org/doc/1.0.x/guide/3.%20Configuration.html#3.4%20Externalized%20Configuration

On Tue, Nov 3, 2009 at 12:34 PM, John Cladmore <junk1@...> wrote:

> Hi all,
>
> I looking for suggestions to solve what seems like a simple requirement.
>
> I am developing a Grails application which will be deployed at several
> locations.  The application will be one build, the only difference is that
> it must generate registration numbers reflecting the site where it is
> deployed.
>
> Since the build will be the same, I know that I can't put this 'site info'
> in the application.  So where would you recommend this information be
> placed?
> The easiest solution I can think of is to simply modify a 'site file' in
> WEB-INF after the app is exploded by the app-server, since this won't be
> accessible by the users.
>
> Thanks.
>
> .v
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email