Rack logging, log level changes over time

chiefgeek · May 29, 2009, 5:56pm

I’m using Jruby Rack + Tomcat and Rails 2.2.2 in threadsafe mode. I’m
seeing
an issue where when the server starts up Rails is logging in debug but
within the first minute or two of running rails switches to error level
logging only. Looking at the Rack source code I noticed it overrides the
default ruby logging, is there any chance it doesn’t have the original
rails
config settings?

Jruby 1.2
Rack 0.9.3
Tomcat 5.5 (Coolstack)
Solaris 10
Rails 2.2.2 (Threadsafe mode)

~Matt

chiefgeek · May 30, 2009, 6:05am

On Fri, May 29, 2009 at 10:53 AM, Matthew K. [email protected]
wrote:

Solaris 10
Rails 2.2.2 (Threadsafe mode)

It’s certainly possible, but I haven’t noticed this behavior before.

The code that overrides the Rails logger is here:

github.com

nicksieger/jruby-rack/blob/bb21bd148433c77a3ccd4e5d99b4d0b3a89e4917/src/main/ruby/jruby/rack/rails.rb#L84-101


      
                session_options[:database_manager] = CGI::Session::JavaServletStore
              end
          
          
    # Turn off default cookies when using Java sessions
              if java_sessions?
                session_options[:no_cookies] = true
              end
            end
          end
          
          
def setup_logger
            if defined?(::RAILS_DEFAULT_LOGGER)
              class << ::RAILS_DEFAULT_LOGGER # Make these accessible to wire in the log device
                public :instance_variable_get, :instance_variable_set
              end
          
          
    # use config.logger?
              if defined?(ActiveSupport::BufferedLogger) # Rails 2.x
                old_device = ::RAILS_DEFAULT_LOGGER.instance_variable_get "@log"
                old_device.close rescue nil
                ::RAILS_DEFAULT_LOGGER.instance_variable_set "@log", logdev

Seems like that shouldn’t affect the logging level, but maybe you
could do a little more sleuthing to see what happens? If necessary,
you could monkey-patch the
JRuby::Rack::RailsServletHelper#setup_logger to be a no-op early in
your boot.rb or environment.rb and see if that changes the behavior.

/Nick

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email