[jruby-dev] [jira] Created: (JRUBY-3273) When isFoo and getFoo collide, isFoo wins when calling foo

2008-12-30 Thread Logan Barnett (JIRA)
When isFoo and getFoo collide, isFoo wins when calling foo -- Key: JRUBY-3273 URL: http://jira.codehaus.org/browse/JRUBY-3273 Project: JRuby Issue Type: Bug Reporter: Logan

[jruby-dev] Leaking JRuby instances due to MySQL timer thread?

2008-12-30 Thread Charles Oliver Nutter
Today I spent some time investigating why repeated deploys of a user's app ate progressively more and more memory on Tomcat on Sun Java 6. I managed to get from the user a heap dump of a server that had an app deployed and undeployed plus an explicit GC. The JRuby instance sticks around. It a

Re: [jruby-dev] Leaking JRuby instances due to MySQL timer thread?

2008-12-30 Thread Nick Sieger
FWIW, these are the kinds of flaky bugs I've seen w/ various versions of the MySQL driver. The version bundled with activerecord-jdbcmysql-adapter, 5.0.4, does not have the statement cancellation timer. If you can try version 5.0.4, see if it helps with the problem. http://github.com/nicksieger/a

Re: [jruby-dev] Leaking JRuby instances due to MySQL timer thread?

2008-12-30 Thread Charles Oliver Nutter
Nick Sieger wrote: FWIW, these are the kinds of flaky bugs I've seen w/ various versions of the MySQL driver. The version bundled with activerecord-jdbcmysql-adapter, 5.0.4, does not have the statement cancellation timer. If you can try version 5.0.4, see if it helps with the problem. http://gi

Re: [jruby-dev] Leaking JRuby instances due to MySQL timer thread?

2008-12-30 Thread Nick Sieger
On Tue, Dec 30, 2008 at 11:02 PM, Charles Oliver Nutter wrote: > Nick Sieger wrote: >> >> FWIW, these are the kinds of flaky bugs I've seen w/ various versions >> of the MySQL driver. The version bundled with >> activerecord-jdbcmysql-adapter, 5.0.4, does not have the statement >> cancellation tim