Logging issue w/ JRuby 1.1.2 on Glassfish

All of the apps that I’m working to transition from pack-of-mongrels to
JRuby on Glassfish (v2) have a context-root of / and in order to
continue that tradition, I’ve decided to set up a virtual server for
each one. This should also have the pleasant side-effect of having
separate log files for each application.

However, after creating a virtual server and listener for the new
application and specifying the separate log file, I can see the log file
get created (with a date suffix mysteriously added, though I can’t find
settings for log rotation), the only things written to it are the
startup notices of the virtual server itself. I’ve deliberately inserted
a bug into a SQL statement to generate an exception trace and still
nothing is written, either to the defined logfile or the one for the
default virtual server. If I deploy the same application to the default
virtual server and kick off the action with the bug, I get the
appropriate trace in the log file.

I’m using Glassfish v2 UR2 b04 on Mac OS X 10.5 and packaging the
application with Warbler 0.9.9

Any help would be appreciated.

-Joel

On Tue, Jul 15, 2008 at 9:41 AM, Joel E. Wilson [email protected] wrote:

the virtual server itself. I’ve deliberately inserted a bug into a SQL
statement to generate an exception trace and still nothing is written,
either to the defined logfile or the one for the default virtual server. If
I deploy the same application to the default virtual server and kick off the
action with the bug, I get the appropriate trace in the log file.

I’m using Glassfish v2 UR2 b04 on Mac OS X 10.5 and packaging the
application with Warbler 0.9.9

Any help would be appreciated.

Have you done anything to explicitly override the Rails logger?
Because JRuby-Rack sets it up by default to write to the servlet
context log, which usually goes to the Glassfish server.log file. I
haven’t experimented with GF virtual servers, so I don’t know if it’s
possible to send each server’s output to a separate log file. You
might try asking on one of the Glassfish lists for help.

Cheers,
/Nick


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Thank you. I haven’t touched the Rack configuration or overridden the
rails logger, but have thought about it as a last resort. The virtual
servers each have a log file setting that don’t seem to quite be working
in this case. I’ll try one of the glassfish lists.

-Joel

----- Original Message -----
From: “Nick S.” [email protected]
To: [email protected]
Sent: Tuesday, July 15, 2008 11:05:15 AM GMT -06:00 US/Canada Central
Subject: Re: [jruby-user] Logging issue w/ JRuby 1.1.2 on Glassfish

On Tue, Jul 15, 2008 at 9:41 AM, Joel E. Wilson [email protected] wrote:

the virtual server itself. I’ve deliberately inserted a bug into a SQL
statement to generate an exception trace and still nothing is written,
either to the defined logfile or the one for the default virtual server. If
I deploy the same application to the default virtual server and kick off the
action with the bug, I get the appropriate trace in the log file.

I’m using Glassfish v2 UR2 b04 on Mac OS X 10.5 and packaging the
application with Warbler 0.9.9

Any help would be appreciated.

Have you done anything to explicitly override the Rails logger?
Because JRuby-Rack sets it up by default to write to the servlet
context log, which usually goes to the Glassfish server.log file. I
haven’t experimented with GF virtual servers, so I don’t know if it’s
possible to send each server’s output to a separate log file. You
might try asking on one of the Glassfish lists for help.

Cheers,
/Nick


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

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs