Results 1 to 4 of 4

Thread: Debugging logs changed after dependency update?

  1. #1
    Join Date
    Jul 2012
    Posts
    8

    Default Debugging logs changed after dependency update?

    Hey All,

    I made a couple smallish changes to BuildConfig.groovy. I added these lines to their respective sections:

    mavenRepo "http://xuggle.googlecode.com/svn/trunk/repo/share/java/"
    //...
    build "xuggle:xuggle-xuggler:5.2"

    Thereafter, logging in the console has gone to debug level, with lots of logging on every grails command,
    like so:

    17:20:37.792 [http-bio-8080-exec-11] DEBUG g.a.t.o.g.p.resource.ResourceTagLib - Removing outstanding request disposition: defer
    17:20:37.793 [http-bio-8080-exec-11] DEBUG o.c.g.g.c.s.ReloadAwareAutowireCapableBeanFactory - Returning cached instance of singleton bean 'org.grails.internal.SESSION_FACTORY_HOLDER'
    17:20:37.793 [http-bio-8080-exec-11] DEBUG o.c.g.g.o.h.s.HibernatePersistenceContextIntercept or - Closing single Hibernate session in GrailsDispatcherServlet
    17:20:37.793 [http-bio-8080-exec-11] DEBUG o.s.o.hibernate3.SessionFactoryUtils - Closing Hibernate Session
    17:20:37.794 [http-bio-8080-exec-11] DEBUG o.c.g.g.w.s.m.GrailsWebRequestFilter - Cleared Grails thread-bound request context: org.apache.catalina.connector.RequestFacade@56f5ed 6e

    Any ideas?

  2. #2
    Join Date
    Aug 2008
    Location
    Vancouver, BC
    Posts
    747

    Default

    Moving this to the grails forum as you will be more likely to get a proper response there.
    Andrew Eisenberg, Ph.D.
    SpringSource, a division of VMware
    SpringSource Tools Team
    More about AJDT, Groovy-Eclipse, and Grails tooling

  3. #3
    Join Date
    Jan 2010
    Posts
    2

    Default

    Did you get this resolved? I'm using Spring LDAP and I'm getting the same messages even though there is no log4j.properties that I can find.

  4. #4
    Join Date
    Jul 2012
    Posts
    8

    Default No solution yet

    Quote Originally Posted by rjkoop View Post
    Did you get this resolved? I'm using Spring LDAP and I'm getting the same messages even though there is no log4j.properties that I can find.
    No, I haven't figured it out yet. I'm struggling a bit with grails logging in general. I can't seem to get a logging statement out of a controller either.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •