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

Web interface not loading: java.lang.IllegalArgumentException: URI is not hierarchical #1924

lennartkoopmann opened this issue Mar 13, 2016 · 0 comments · Fixed by #1930


Copy link

Problem description

Compiled a fresh graylog-server from current master. Opening the web interface in Chrome on OSX returns an empty/white page and the JS console shows that GET for vendor.js and app.5eed8f45f4bee35f56f5.js failed with an HTTP 500.

Note that the comments in this commit show someone else having the same problem: 515c3a2

Steps to reproduce the problem

See description.


  • Graylog Version: master / d45f72d
  • Elasticsearch Version: 2.2.0
  • MongoDB Version: 3.0.0
  • Operating System: OSX 10.11.2
  • Browser version: Chrome 48.0.2564.116 (64-bit)
@lennartkoopmann lennartkoopmann added this to the 2.0.0 milestone Mar 13, 2016
@kroepke kroepke self-assigned this Mar 14, 2016
kroepke added a commit that referenced this issue Mar 15, 2016
After assembly we cannot use File objects to access individual asset files. Instead we need to use a JarFileSystem to access the file metadata.

We could also cache the etag and modification dates in case of jars, but this change currently does not do that. We may want to revisit this in the future.
The patch uses a LoadingCache as a simple "lock" when creating the filesystem (uris will overlap and reference mostly the shaded jar, the cache makes sure only one thread is creating the filesystem).

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

Successfully merging a pull request may close this issue.

2 participants