I can confirm that it's working on master (JRuby 9000) with 2.x mode.
guess this will be fixed once its out.

One liner that reproduces this on 1.7:

jruby -rnet/http -ropenssl -e "p Net::HTTP.get 'bundler.rubygems.org', '/api/v1/dependencies?gems=railties,actionmailer,sprockets-rails,sprockets,puma,foreman,jruby-openssl,rsolr,activesupport,rake,rspec,guard-rspec,nokogiri,tidy_ffi,fakefs,pry-byebug'"

I needed to add --2.0:

jruby --2.0 -rnet/http -ropenssl -e "p Net::HTTP.get 'bundler.rubygems.org', '/api/v1/dependencies?gems=railties,actionmailer,sprockets-rails,sprockets,puma,foreman,jruby-openssl,rsolr,activesupport,rake,rspec,guard-rspec,nokogiri,tidy_ffi,fakefs,pry-byebug'"

Oh, right, you need that too :-)

Does this work properly on older JRuby 1.7 versions?

This is the only one I tried. I wanted to test one request in my app without the GVL in MRI, that is how I found out this issue...

This issue also prevents rbenv from installing JRuby if you have compat.version=2.0 in your ~/.jrubyrc, which is my case:

rbenv/ruby-build#718

This works properly in JRuby 1.7.13

Weird... I just checked that one-liner with 1.7.19 and it worked... Maybe the guys in bundler.rubygems.org changed something that affected this somehow... Not sure how to proceed from here... Should we close this ticket and re-open if it happens again? I suspect there's still some hidden bug but now it's no longer reproducible...

This is occurring with 1.7.21

In fact, no remote gems are directly installable with 2.0 enabled either.

closing since this was a JRuby 1.7.x issue ... seems fine by now (on JRuby 1.7.25+ using Bundler 1.13)