Mysql Broken Pipe

Ruby JRuby
1

getting the following error with rails 2.2 and JNDI enabled inside
tomcat. Jruby 1.1.6, rails 2.2.2

ActiveRecord::StatementInvalid (ActiveRecord::ActiveRecordError:
Broken pipe: SELECT * FROM sessions WHERE (session_id =
‘1422264526c60217b1411ed5c2902582’) LIMIT 1):

Any ideas ?

Thanks
Adam

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
2

AD wrote:

getting the following error with rails 2.2 and JNDI enabled inside
tomcat. Jruby 1.1.6, rails 2.2.2

ActiveRecord::StatementInvalid (ActiveRecord::ActiveRecordError:
Broken pipe: SELECT * FROM sessions WHERE (session_id =
‘1422264526c60217b1411ed5c2902582’) LIMIT 1):

Any ideas ?

Hmm, perhaps the connection was closed before it was able to run the
select? Or the connection it gets is bad? Does it do this if you don’t
use JNDI connection pool?

  • Charlie

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
3

prior to JNDI i had a ton of the “mysql connection has gone away…”

That seems to be resolved but now I get the broken pipe error. So to
answer you question this error seems to go away but comes back with a
much worse one. I guess we could try dropping JNDI since Rails 2.2
now has a builtin connection pool now but not sure if it as fault
tolerant as DBCP or C3P0 to use “testonborrow” and other useful
features.

Any recommendations here ?

Thanks
Adam

On Tue, Jan 27, 2009 at 10:18 AM, Charles Oliver N.
[email protected] wrote:

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
4

I wonder if it’s some interaction between Rails 2.2 connection pooling
and the builtin ones. Maybe there’s a way to disable Rails’ pool when
you’re using JNDI, so it doesn’t try to hold on to connection the JNDI
pool may want to cull?

AD wrote:

Broken pipe: SELECT * FROM sessions WHERE (session_id =
To unsubscribe from this list, please visit:

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
5

i think Nick addressed this in another thread and if I remember you
have to use connection pools in both. He said you have to set the
rails connection pool to at least the size of the JNDI pool.

Nick any ideas here? Should we stick with strictly using Rails
connection pool instead of JNDI → Rails Pool → DB ?

Adam

On Tue, Jan 27, 2009 at 5:34 PM, Charles Oliver N.
[email protected] wrote:

answer you question this error seems to go away but comes back with a
On Tue, Jan 27, 2009 at 10:18 AM, Charles Oliver N.

To unsubscribe from this list, please visit:

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