The important thing is that, for JRuby support, you’re going to need a modern version of Java. Wikipedia has a good page that describes it well. Basically JRuby is an implementation of Ruby, written mostly in Java. We will use a wonderful technology called Jruby:Īs it self-describes itself at, with JRuby you get the best of the JVM, but at the same time it is ‘just Ruby’. Or cheat, and download my WAR archive to be found at the end of this post and deploy it directly to your SAP JVM (and then go and hack the WAR archive)! So, follow along with all the steps and do it yourself. And this blog details how, with a simple example for an “Hello World” Sinatra/Rack application. It may be caused by a Ruby bug.You did know that you can write Ruby scripts, even those that use popular frameworks like Ruby on Rails or Sinatra and deploy them to the Java Application Server’s JVM of your portal environment? Right? See the kubernetes section of the documentation for more details.įor MRI versions 2.2.7, 2.2.8, 2.2.9, 2.2.10, 2.3.4 and 2.4.1, you may see stream closed in another thread (IOError).

Kubernetes: The way Kubernetes handles pod shutdowns interacts poorly with server processes implementing graceful shutdown, like Puma.

Windows: Cluster mode is not supported due to a lack of fork(2).

Also, cluster mode is not supported due to a lack of fork(2). These platforms have no way to pass descriptors into a new process that is exposed to Ruby.

JRuby, Windows: server sockets are not seamless on restart, they must be closed and reopened.

Some platforms do not support all Puma features. A detailed guide to using UNIX signals with Puma can be found in the Signals documentation.

This makes sure that no pending requests are dropped while the restart is taking place.įor more, see the Restart documentation.

This is the same functionality available in Unicorn and NGINX which keep the server sockets open between restarts. When available (MRI, Rubinius, JRuby), Puma performs a 'hot restart'. Puma includes the ability to restart itself. You can see all config default values in Puma::Configuration#puma_default_options or configuration.rb.Ĭheck out Puma::DSL or dsl.rb to see all available options.

The default puma RACK_ENV value is development. The other side-effects of setting the environment are whether to show stack traces (in development or test), and setting RACK_ENV may potentially affect middleware looking for this value to change their behavior.

Rack app server