Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: JRuby 1.6.6
-
Fix Version/s: JRuby 1.6.7
-
Component/s: None
-
Labels:
-
Environment:Windows Server 2008 R2 x64, JRuby 1.6.6
-
Number of attachments :
Description
Trying to install certain gems (e.g. rails) with JRuby 1.6.6 on Windows Server 2008 x64 fails:
jruby -S gem install rails
ERROR: While executing gem ... <ArgumentError>
marshal data too short
Trying to install the gem with Bundler throws the same error, but with a stack trace:
jruby -S bundle install
ArgumentError: marshal data too short
load at org/jruby/RubyMarshal.java:150
At the moment I can only reproduce this on a Windows 2008 R2 x64 machine. On a similar 32-bit installation it works flawlessly. Don't know if that could be a reason.
Activity
Charles Oliver Nutter
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Assignee | Thomas E Enebo [ enebo ] | Charles Oliver Nutter [ headius ] |
| Fix Version/s | JRuby 1.6.7 [ 18315 ] | |
| Resolution | Fixed [ 1 ] |
Charles Oliver Nutter
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Hmm, I would not expect 32 vs 64-bit to cause a problem, but stranger things have happened.
Would it be possible for you to run this again, passing the flag -Xbacktrace.style=raw to JRuby (or -J-Djruby.backtrace.style=raw to java) so we can get a more complete trace? You should also be able to get a longer trace from rubygems by passing --trace or --debug (I forget which).
Without being able to reproduce this we will have to depend on you to investigate. Sorry this got missed...we're doing JRuby 1.6.7 this week, so there's a time crunch now.