When launching my Ruby on Rails project using a pre-existing JRuby 1.2.0 install and Glassfish V3 prelude, the
application fails to start and generates multiple Out Of Memory exceptions prior to accessing the application code. 
This was not the case in 200903310200 or before.



Apr 1, 2009 9:29:18 PM com.sun.grizzly.pool.DynamicPool logDynamicStatus
INFO: Pool started without dynamic resizing enabled. Pool will not attempt to determine the upper and lower bounds that
it should be using, and will stay at 1
Apr 1, 2009 9:29:19 PM com.sun.grizzly.jruby.RailsAdapter <init>
INFO: Jruby version is: 1.2.0
Apr 1, 2009 9:29:19 PM com.sun.grizzly.jruby.RailsAdapter startRubyRuntimePool
INFO: Starting Rails instances
Fast Debugger (ruby-debug-ide 0.4.5) listens on localhost:57613
/home/esmith/Apps/jruby-1.2.0/lib/ruby/gems/1.8/gems/actionpack-2.3.2/lib/action_controller/middleware_stack.rb:84
warning: given block not used
Apr 1, 2009 9:29:45 PM com.sun.grizzly.pool.DynamicPool$1 run
INFO: New instance created in 25,802 milliseconds
Apr 1, 2009 9:29:46 PM com.sun.grizzly.http.SelectorThread displayConfiguration
INFO: 
 Grizzly configuration for port 3000
         maxThreads: 5
         minThreads: 5
         ByteBuffer size: 8192
         maxHttpHeaderSize: 8192
         maxKeepAliveRequests: 256
         keepAliveTimeoutInSeconds: -1
         Static File Cache enabled: true
         Static resources directory: /home/esmith/Development/ResNet-V3.21/public
         Adapter : com.sun.grizzly.jruby.RailsAdapter
         Thread Pool (Pipeline): com.sun.grizzly.http.LinkedListPipeline
         Asynchronous Request Processing enabled: true
Exception in thread "httpWorkerThread-3000-0" java.lang.OutOfMemoryError: Java heap space
        at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:39)
        at java.nio.ByteBuffer.allocate(ByteBuffer.java:312)
        at com.sun.grizzly.util.ByteBufferFactory.allocateView(ByteBufferFactory.java:105)
        at com.sun.grizzly.util.ByteBufferFactory.allocate(ByteBufferFactory.java:137)
        at com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:171)
Exception in thread "httpWorkerThread-3000-2" java.lang.OutOfMemoryError: Java heap space
        at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:39)
        at java.nio.ByteBuffer.allocate(ByteBuffer.java:312)
        at com.sun.grizzly.util.ByteBufferFactory.allocateView(ByteBufferFactory.java:105)
        at com.sun.grizzly.util.ByteBufferFactory.allocate(ByteBufferFactory.java:137)
        at com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:171)
Exception in thread "httpWorkerThread-3000-4" java.lang.OutOfMemoryError: Java heap space
        at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:39)
        at java.nio.ByteBuffer.allocate(ByteBuffer.java:312)
        at com.sun.grizzly.util.ByteBufferFactory.allocateView(ByteBufferFactory.java:105)
        at com.sun.grizzly.util.ByteBufferFactory.allocate(ByteBufferFactory.java:137)
        at com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:171)
Exception in thread "httpWorkerThread-3000-3" java.lang.OutOfMemoryError: Java heap space
        at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:39)
        at java.nio.ByteBuffer.allocate(ByteBuffer.java:312)
        at com.sun.grizzly.util.ByteBufferFactory.allocateView(ByteBufferFactory.java:105)
        at com.sun.grizzly.util.ByteBufferFactory.allocate(ByteBufferFactory.java:137)
        at com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:171)
Exception in thread "httpWorkerThread-3000-1" java.lang.OutOfMemoryError: Java heap space


Looking at the IDE log file, it appears that the Platform manager is having problems with platform identification where
a space is in the platform name and since it cannot find it, it reverts to the built-in version.