Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2013-01-10T17:00:06Z by bhdaniel
SystemAdmin
SystemAdmin
590 Posts
ACCEPTED ANSWER

Pinned topic WLP not able to load a JRuby/Rails/Warble app.

‏2013-01-09T03:23:26Z |
I've got a problem trying to run JRuby/Rails/Warble app on Websphere Liberty Profile

The war is able to be deployed on several other containers such as Winstone, Tomcat, Jetty without a problem. WLP is having issues trying to load the app though.

I've unzipped the war and it does indeed contain a WEB-INF/config/environment.rb file as expected, WLP seems to not be able to find it though.

What else could I do to debug this issue?

I'm all out of ideas.

org.jruby.exceptions.RaiseException: (LoadError) no such file to load -- /Users/panchisco/src/wlp/usr/servers/defaultServer/workarea/org.eclipse.osgi/bundles/33/data/cache/com.ibm.ws.app.manager_gen_210948ec-7941-4a5f-860e-54ca68f93a11/liberator.war!/WEB-INF/config/environment.rb
at org.jruby.RubyKernel.load(org/jruby/RubyKernel.java:1046)
at RUBY.load_environment(file:/Users/panchisco/src/wlp/usr/servers/defaultServer/workarea/org.eclipse.osgi/bundles/33/data/cache/com.ibm.ws.app.manager_gen_210948ec-7941-4a5f-860e-54ca68f93a11/.cache/WEB-INF/lib/jruby-rack-1.1.12.jar!/jruby/rack/rails/environment2.rb:23)
at RUBY.load_environment(file:/Users/panchisco/src/wlp/usr/servers/defaultServer/workarea/org.eclipse.osgi/bundles/33/data/cache/com.ibm.ws.app.manager_gen_210948ec-7941-4a5f-860e-54ca68f93a11/.cache/WEB-INF/lib/jruby-rack-1.1.12.jar!/jruby/rack/rails_booter.rb:66)
at RUBY.(root)(<script>:1)
  • bhdaniel
    bhdaniel
    2 Posts
    ACCEPTED ANSWER

    Re: WLP not able to load a JRuby/Rails/Warble app.

    ‏2013-01-10T17:00:06Z  in response to SystemAdmin
    Hi,
    I believe the problem is that the JRuby/Rails/Warble app expects the WAR file to be expanded on the file system. Liberty does not automatically expand WAR files when they are deployed (as some other app servers do.) You can work around this by expanding the application on the file system. For example, if your application is in a file myApp.war in the dropins directory, you would expand the WAR file into a directory named "myApp.war" so that you would have dropins/myApp.war, dropins/myApp.war/WEB-INF/web.xml, etc.