db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cdwillie76 <chris.d.willi...@gmail.com>
Subject Derby issues (Windows vs Linux) with a Rails 2.0.2 and 1.1RC2
Date Tue, 04 Mar 2008 03:04:57 GMT

I have a pretty basic Rails 2.0.2 using embedded derby that I am deploying
with warbler and goldspike 1.5.  If I deploy the war and run the application
under tomcat on linux, it runs fine.  If I deploy that same war on windows
with tomcat, I get periodic "can't connect to the database errors".  I
thought that Derby in the embedded mode was ok as long as it was in the same
VM.

I have a requirement to only deploy wars in a app server for my application
so I can't run the network version.  Is there a way to run derby as it's own
war so it acts as a network server?

So the question I am asking is anyone using Derby much on Windows in a
application server environment?  I am trying to narrow it down on if it is a
derby, jruby, tomcat, and/or rails issue.  Any suggestions would be great. 
I know it is a pretty open ended question but I had to ask...

Thanks!
CW

Below are the errors I am getting...
Here is the stack trace I get...

The driver encountered an error:
org.apache.derby.impl.jdbc.EmbedSQLException: Failed to start database
'c:/projects/derby_databases/maadn_production', see the next exception for
details.

RAILS_ROOT: c:/projects/apache-tomcat-5.5.26/webapps/maadn/WEB-INF
Application Trace | Framework Trace | Full Trace

gems/gems/activerecord-jdbc-adapter-0.7.1/lib/active_record/connection_adapters/jdbc_adapter.rb:303:in
`initialize'
gems/gems/activerecord-jdbc-adapter-0.7.1/lib/active_record/connection_adapters/jdbc_adapter.rb:46:in
`new'
gems/gems/activerecord-jdbc-adapter-0.7.1/lib/active_record/connection_adapters/jdbc_adapter.rb:46:in
`jdbc_connection'
gems/gems/activerecord-jdbc-adapter-0.7.1/lib/active_record/connection_adapters/jdbc_adapter.rb:54:in
`embedded_driver'
gems/gems/activerecord-jdbc-adapter-0.7.1/lib/jdbc_adapter/jdbc_derby.rb:8:in
`derby_connection'
gems/gems/activerecord-2.0.2/lib/active_record/connection_adapters/abstract/connection_specification.rb:291:in
`connection='
gems/gems/activerecord-2.0.2/lib/active_record/connection_adapters/abstract/connection_specification.rb:259:in
`retrieve_connection'
gems/gems/activerecord-2.0.2/lib/active_record/connection_adapters/abstract/connection_specification.rb:78:in
`connection'
gems/gems/activerecord-2.0.2/lib/active_record/query_cache.rb:8:in `cache'
gems/gems/actionpack-2.0.2/lib/action_controller/caching.rb:677:in
`perform_action_with_caching'
gems/gems/actionpack-2.0.2/lib/action_controller/caching.rb:677:in `process'
gems/gems/actionpack-2.0.2/lib/action_controller/filters.rb:685:in
`process_with_filters'
gems/gems/actionpack-2.0.2/lib/action_controller/session_management.rb:123:in
`process_with_session_management_support'
gems/gems/actionpack-2.0.2/lib/action_controller/base.rb:388:in `process' 
-- 
View this message in context: http://www.nabble.com/Derby-issues-%28Windows-vs-Linux%29-with-a-Rails-2.0.2-and-1.1RC2-tp15819402p15819402.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.


Mime
View raw message