We’re attempting to upgrade our apps from Jruby-1.2.0/Rails-2.1.0 to
Jruby-1.3.0/Rails-2.3.2 with multithreading on. We use Warbler and
deploy into Tomcat-6(BTW initial tests showed significant reduction in
memory and boost in speed).
I’m not sure what version of warbler the notes at
http://kenai.com/projects/jruby/pages/Rails_2_3_2
are relevant to, but here are some additional observations/questions.
The main issues so far:
-
In production mode, with cofing.!threadsafe = true and
cache_classes = true, automatic dependency loading after boot is
disabled. (see
Rails::Configuration)
. This results in a slew of ‘uninitialized constant’ errors that were
only popping up in production mode/WAR. Now that I know the cause, it
all makes sense, but it tripped me up for a bit.
-
Session::MemoryStore and PStore have been removed from Rails-2.3.
We typically develop our apps using Webrick or Mongrel and only WAR
them up for deployment. Where JavaServletStore was being used in
‘production’, we had been substituting PStore or MemoryStore during
‘development’(only in a couple specialized apps where the sessions
were too large for cookies). This is obviously a problem now. I’m
currenlty looking into hacking a custom session store together just
for development. Our apps are mostly new web-2.0ish interfaces on top
of pre-existing Java/Spring/Hibernate code so we don’t use
ActiveRecord and can’t just substitute ActiveRecordStore.
-
One of the changes in Warbler-0.9.13(as promised) has been to not
replace the default rails session store automatically. The Wiki page
above references having to tweak the settings in order to use
ActiveRecordStore. Does anyone know off the top of thier head what
needs to be put in to explicitly specify JavaServletStore?
Thanks,
-lenny
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
On Jun 11, 2009, at 12:11 PM, Lenny M. wrote:
‘production’, we had been substituting PStore or MemoryStore during
ActiveRecordStore. Does anyone know off the top of thier head what
needs to be put in to explicitly specify JavaServletStore?
Actually, looking at this closer, it looks like JavaServletStore at
least as of the current HEAD of jruby-rack wouldn’t work at all
because it isn’t rack compliant. I’m naively thinking that it wouldn’t
be too difficult to adapt it. Has anyone already started work on that
somewhere? I’ll give it a stab otherwise. If anyone has any thoughts,
let me know.
Thanks,
-lenny
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
On Thu, Jun 11, 2009 at 11:11 AM, Lenny M.[email protected] wrote:
The main issues so far:
for deployment. Where JavaServletStore was being used in ‘production’, we
had been substituting PStore or MemoryStore during ‘development’(only in a
couple specialized apps where the sessions were too large for cookies). This
is obviously a problem now. I’m currenlty looking into hacking a custom
session store together just for development. Our apps are mostly new
web-2.0ish interfaces on top of pre-existing Java/Spring/Hibernate code so
we don’t use ActiveRecord and can’t just substitute ActiveRecordStore.
Can you use Rails’ default, the cookie store?
/Nick
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
On Thu, Jun 11, 2009 at 2:28 PM, Lenny M.[email protected] wrote:
http://kenai.com/projects/jruby/pages/Rails_2_3_2 are relevant to, but here
- One of the changes in Warbler-0.9.13(as promised) has been to not
otherwise. If anyone has any thoughts, let me know.
Correct, I haven’t started on it yet but would like to have it soon.
Ryan B. started work on one, but it may or may not be worth
continuing with his code vs. starting fresh.
/Nick
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email