We can not answer this question without knowing what you're "really" looking for.
In general, for Ruby-ists used to MRI the "main" difference is GIL-free multi-threading (Ruby code can actually run in parallel utilizing your CPU cores).
It's similar to Rubinius (also GIL-free) and is probably something that from time-to-time confuses Ruby developers if they have little experience with concurrency.
This is usually not something you need to worry about (as popular gems
are thread-safe), but you might hit it eventually e.g. with web
applications in your own user code.
Unlike Rubinius however, JRuby does not support MRI style C-extension gems, luckily most popular ones have alternatives or versions using Java-extension.
The most notable difference you'll notice when trying JRuby out is that it's slower to start, however with a few tricks (jruby --dev) it's not that bad once you're using it for a while.
... all that being said JRuby is just Ruby and you can use it just like MRI.