jruby/warbler

same war file, two different behaviors

mengu opened this issue · 7 comments

mengu commented

hi everyone

i generate a war file with warble compiled executable war.

  • if i run the war file with java -jar x.war everything works perfectly. no errors, no problems, no warnings.
  • if i deploy it to tomcat, i get various *.class is not compiled Ruby; use java_import to load normal classes errors.

i also deployed a war -to test it out- that is generated with warble executable war and deployed it on tomcat. also no errors.

my jruby version is:
jruby 9.2.0.0 (2.5.0) 2018-05-24 81156a8 Java HotSpot(TM) 64-Bit Server VM 25.112-b16 on 1.8.0_112-b16 +jit [darwin-x86_64]

my warbler version is: 2.0.5

where should i look to fix this?

mengu commented

hi all, does anyone have any idea as to what might cause this issue?

kares commented

jruby-jars 9.2.0 seems to be having issues with Bundler, so likely this would be a duplicate of #432
message should confirm, also degrading jruby-jars to < 9.2 could confirm whether this is JRuby 9.2 specific

mengu commented

thank you @kares . i'll give it a try.

aschmied commented

@mengu did you find a workaround? I'm seeing this on both Windows and Linux using:

  • jruby 9.2.5.0 (2.5.0) 2018-12-06 6d5a228 Java HotSpot(TM) 64-Bit Server VM 25.144-b01 on 1.8.0_144-b01 +jit [mswin32-x86_64]
  • Warbler version 2.0.5
mengu commented

hi @aschmied, sorry i could not. i did not have the time to do so. i've just chosen to deploy an executable war rather than a compiled one. i'll give it another try later this month.

aschmied commented

OK, thanks for replying. This is the same symptom as JRuby Issue 5341, but that issue is fixed in 9.2.5.0

aschmied commented

@mengu on our project this failure seemed to be triggered by a .jrubyrc in the app root with "debug.fullTrace=true" in it. If you have debug.fullTrace enabled, try disabling it. I opened a JRuby issue for it

  • 👍1