Hello,
When we set our jruby.min.runtimes, jruby.max.runtimes, and
jruby.runtimes to 1, glassfish starts and runs our app fine (not sure
if the last one is redundant?).
If we set them to 2, however, glassfish takes forever to start, and
sometimes doesn’t start up at all. It looks like it is continually
trying to restart the runtimes and thrashing somehow. One time we got
this exception:
[#|2009-10-29T20:49:24.025+0000|SEVERE|sun-glassfish|javax.enterprise.system.container.web|_ThreadID=25;_ThreadName=Thread-3;|WebModule[]Application
Error
org.jruby.rack.RackInitializationException: timeout: all listeners busy
at
org.jruby.rack.PoolingRackApplicationFactory.getApplication(PoolingRackApplicationFactory.java:83)
This is with Jruby 1.4.0RC1, Rails 2.2.2 app, Glassfish v3, JDK 1.6.
We thought it might be memory, but a single runtime works fine with 1G
heap and 256 Permsize, and we doubled these when we increased to 2
runtimes. Server CPU is pegged, but it is not swapping at all.
How can we debug this problem?
Thanks,
– Chad
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
I think we’re going to need to pull in GF guys for this one. Vivek?
You out there?
On Thu, Oct 29, 2009 at 5:00 PM, Chad W. [email protected]
wrote:
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Which Glassfish v3 version you are trying?
Looks like this is WAR deployment of Rails application, where it uses
JRuby-Rack/Warbler. Whats your -Xmx and -XX:MaxPermSize settings?
Have you give glassfish gem a try? http://glassfishgem.rubyforge.org/.
Or try out glasfish v3 latest promotion. Glassfish v3 is pretty close to
getting final and has many improvements for Ruby/Rack based
applications.
Also, you do not need to use warble to warup your app. Simply deploy it
using ‘asadmin deploy yourappDir/’. Check it out:
http://download.java.net/glassfish/v3/promoted/glassfish-v3-web-b70.zip
-vivek.
On Fri, Oct 30, 2009 at 1:50 PM, Charles Oliver N.
On Fri, Oct 30, 2009 at 2:00 PM, Vivek P. [email protected]
wrote:
Which Glassfish v3 version you are trying?
It is glassfish3-prelude build b28c
Looks like this is WAR deployment of Rails application, where it uses
JRuby-Rack/Warbler. Whats your -Xmx and -XX:MaxPermSize settings?
2g and 512m for 2 runtimes (double what we successfully used for 1
runtime)
Have you give glassfish gem a try? http://glassfishgem.rubyforge.org/.
The app runs under glassfish gem, but our goal is a running deployable
war file, so we are focusing on that. Should multiple runtimes behave
differently under the gem than the regular app server?
Or try out glasfish v3 latest promotion. Glassfish v3 is pretty close to
getting final and has many improvements for Ruby/Rack based applications.
OK, we can try that.
Also, you do not need to use warble to warup your app. Simply deploy it
using ‘asadmin deploy yourappDir/’. Check it out:
http://download.java.net/glassfish/v3/promoted/glassfish-v3-web-b70.zip
OK. Again, our goal is a deployable war, so we aren’t interested in
deploying from the filesystem unless it helps debug this issue.
Thanks for your help…
wrote:
heap and 256 Permsize, and we doubled these when we increased to 2
runtimes. Server CPU is pegged, but it is not swapping at all.
How can we debug this problem?
Thanks,
– Chad
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
On Fri, Oct 30, 2009 at 2:38 PM, Chad W.
[email protected]wrote:
On Fri, Oct 30, 2009 at 2:00 PM, Vivek P. [email protected]
wrote:
Which Glassfish v3 version you are trying?
It is glassfish3-prelude build b28c
ok. This is pretty old. you may like to try the latest v3 promotion.
Looks like this is WAR deployment of Rails application, where it uses
JRuby-Rack/Warbler. Whats your -Xmx and -XX:MaxPermSize settings?
2g and 512m for 2 runtimes (double what we successfully used for 1 runtime)
I think this looks reasonable. I suspect this is some bug either in
jruby-rack or glassfish web-container. Let us know how it behaves with
the
latest v3 promotion.
Have you give glassfish gem a try? http://glassfishgem.rubyforge.org/.
The app runs under glassfish gem, but our goal is a running deployable
war file, so we are focusing on that. Should multiple runtimes behave
differently under the gem than the regular app server?
Yes. glassfish gem and jruby-rack/warbler code base is completely
different,
they dont share anything.
On Fri, Oct 30, 2009 at 3:45 PM, Vivek P. [email protected]
wrote:
I think this looks reasonable. I suspect this is some bug either in
jruby-rack or glassfish web-container. Let us know how it behaves with the
latest v3 promotion.
It looks like multiple runtimes are working with the latest glassfish
release. Thanks for the prompt response!
– Chad
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
You can check out the Xmx and perm size settings in
glassfish-installation/domains/domain1/config/domain.xml.
-vivek.