Forums | Admin

Discussion Forums: open-discussion

Start New Thread Start New Thread

 

By: Brandon Hauff
RE: Log Issue [ reply ]  
2009-12-11 15:36
Issue created.

By: Vivek Pandey
RE: Log Issue [ reply ]  
2009-12-10 17:15
Looks like its a silly bug in there which we did not catch in our testing.

Can you open an issue? I should rollout a new gem release soon.

-vivek.

By: Brandon Hauff
RE: Log Issue [ reply ]  
2009-12-10 16:25
I noticed that if I restart glassfish the production log is recreated, trashing the old one. Is this intended functionality? I thought the idea was to append to the log?

By: Vivek Pandey
RE: Log Issue [ reply ]  
2009-12-08 17:55
With the upcoming gem release: http://hudson.glassfish.org/job/glassfish-gem-build/161/, the log level you supply thru gem is applied to the rails log level as well. Also, glassfish does not try to rotate the log by itself. So you can pretty much use logrotate or other mechanism for log rotation.

I will be releasing new version of gem in couple of days. Please try http://hudson.glassfish.org/job/glassfish-gem-build/161/ and let me know if it works for you and let me know soon so that if there is anything is broken so that I can try fixing it.

-vivek.

By: Brandon Hauff
RE: Log Issue [ reply ]  
2009-12-08 17:35
My logs quickly get to 2mb and then glassfish rotates out the logfile, but does not create another to keep logging. I have to restart glassfish to get the logging to start again.

By: Ken D
RE: Log Issue [ reply ]  
2009-10-08 20:04
I see this too with Sinatra. The log-level in glassfish.yml becomes the log level of all request messages. E.G.,

Oct 8, 2009 3:53:09 PM sun.reflect.NativeMethodAccessorImpl invoke0
WARNING: - [08/Oct/2009 15:53:09] "GET /images/icons/bullet.png " 304 - 0.0310

These logs get huge fast, btw. I'd love to have more control over what requests get logged (like > 400).


By: Vivek Pandey
RE: Log Issue [ reply ]  
2009-09-25 03:48
Whats happening is that the log levels currently coded in such a way that it applies to the messages produced by glassfish.

What it should be doing is to modify the Rails log level automatically. I am not sure if Rails can let us do this automatically. I will look in to it. Can you report an issue?

By: Andrew Ullmann
Log Issue [ reply ]  
2009-09-18 15:20
After changing the log level in my glassfish.yml from it’s default of INFO to SEVERE, and now messages that were formerly INFO messages are now considered SEVERE.

log-level: 1

Sep 18, 2009 10:09:38 AM sun.reflect.GeneratedMethodAccessor4 invoke SEVERE: - [18/Sep/2009 10:09:38] "GET /images/icons/add.png " 304 - 0.1090

Is this the way it is supposed to work? I thought this was a log suppression (quantity of data) method.

-Andrew