Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

__UNKNOWN_CONSTANT__ error on Windows on 1.7.16 (and 1.7.16.1) #2166

Closed
jeremybmerrill opened this issue Nov 10, 2014 · 2 comments
Closed

__UNKNOWN_CONSTANT__ error on Windows on 1.7.16 (and 1.7.16.1) #2166

jeremybmerrill opened this issue Nov 10, 2014 · 2 comments

Comments

@jeremybmerrill
Copy link

In short, I don't have much more detailed information than that, other than that, on Windows, the project functions correctly with JRuby 1.7.15, but not with .16 or .16.1. I don't have a minimal example, unfortunately.

In longer terms: Tabula is a locally-run Rack app for liberating data tables from PDFs. It's all Ruby, with some calls to some Java libraries. The app starts itself, then opens a browser pointing at localhost, where the app's index page should appear. Instead, on Windows, with 1.7.16/1.7.16.1, we get an error.

The error comes back as (SystemCallError) Unknown Error (206) - UNKNOWN_CONSTANT.
Since this is a Ruby app packaged by Warbler, the JRuby version is being set via jruby-jars. The error occurs on all the Windows 7 and Windows 8 machines we've tested this on -- but none of the Mac/Linux machines.

Here's our bug report thread.

Please let me know what I can do to help y'all track this down; I'm happy to help.

@jeremybmerrill
Copy link
Author

One piece of info: I think the issue is related to the process of building for Windows (which tends to take place on Linux/Mac, not Windows). Here's why:

  1. jruby-jars is specified in the development group of our Gemfile. When it's moved to the default group, the size of the built app grows by 20 MB, suggesting that jruby-jars was added to the built app and suggesting that, ordinarily, jruby-jars is used in the build process, but not included in the built app.
  2. the issue only arises when running the built app (an exe and a jar) on Windows. Running the app from source using rackup works as expected.

@kares
Copy link
Member

kares commented Jun 22, 2017

this one somehow got left, on the other hand it wasn't easy to reproduce.
noticed tabula is now using jruby-9.1.7.0 ... and since 1.7.x has EOL-ed we're closing.
let us know if there's any issues with 9K (in a new bug report), thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants