Project

General

Profile

Actions

Defect #2476

closed

JRuby: Cannot start redmine

Added by Marc Cooper over 15 years ago. Updated over 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2009-01-09
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

No problems starting and using redmine (HEAD) on MRI, but I get the following on JRuby:

\redmine>jruby script/server e production
=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
=> Rails 2.1.2 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Exiting
d:/jruby/bin/../lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require': no such file to load -
win32/service (MissingSourceFile)
from
d:/jruby/bin/../lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require' from D:/jruby/lib/ruby/gems/1.8/gems/activesupport-
2.1.2/lib/active_support/dependencies.rb: 510:in `require'
from D:/jruby/lib/ruby/gems/1.8/gems/activesupport-
2.1.2/lib/active_support/dependencies.rb: 355:in `new_constants_in'
from D:/jruby/lib/ruby/gems/1.8/gems/activesupport-
2.1.2/lib/active_support/dependencies.rb: 510:in `require'
from D:/jruby/lib/ruby/gems/1.8/gems/mongrel_service-
0.1/lib/mongrel_service/init.rb:5
from D:/jruby/lib/ruby/gems/1.8/gems/mongrel_service-
0.1/lib/mongrel_service/init.rb:31:in `require' from
d:/jruby/bin/../lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from D:/jruby/lib/ruby/gems/1.8/gems/activesupport-
2.1.2/lib/active_support/dependencies.rb: 510:in `require'
... 18 levels...
from D:/jruby/lib/ruby/gems/1.8/gems/rails-
2.1.2/lib/commands/server.rb:31:in `require' from
d:/jruby/bin/../lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require' from script/server:3

JRuby guru, Charlie said:

If RedMine has added a dependency on win32, they should be thoroughly slapped around. It appears that they have. Complain to RedMine :)

\redmine>ruby script/about
About your application's environment
Ruby version 1.8.6 (i386-mswin32)
RubyGems version 1.3.1
Rails version 2.1.2
Active Record version 2.1.2
Action Pack version 2.1.2
Active Resource version 2.1.2
Action Mailer version 2.1.2
Active Support version 2.1.2
Application root C:/Documents and Settings/marc/My Documents/NetBeansProjects/redmine
Environment development
Database adapter mysql

\redmine>jruby script/about
About your application's environment
Ruby version 1.8.6 (java)
RubyGems version 1.3.1
Rails version 2.1.2
Active Record version 2.1.2
Action Pack version 2.1.2
Active Resource version 2.1.2
Action Mailer version 2.1.2
Active Support version 2.1.2
Application root C:/Documents and Settings/marc/My Documents/NetBeansProjects/redmine
Environment development
Database adapter mysql

Actions #1

Updated by Jean-Philippe Lang over 15 years ago

Redmine guru, JP says:

Man, there's no dependency on win32. redmine.org is running on linux... Complain to JRuby :-)

And I don't see any Redmine code involved in your stack trace.
I can't help since I don't use JRuby. Maybe someone else?

Actions #2

Updated by Jean-Philippe Lang over 15 years ago

I made a quick test, Redmine starts with JRuby 1.1.4.
But it doesn't start with JRuby 1.1.5. I get the same error as the one described here: http://jira.codehaus.org/browse/JRUBY-3115.

It looks like mongrel tries to start Redmine as a Win32 service in your case.
Can you try to run it with webrick:

jruby script/server webrick -e production
Actions #3

Updated by Jean-Philippe Lang over 15 years ago

Redmine also starts with JRuby 1.1.6 RC1.

Actions #4

Updated by Marc Cooper over 15 years ago

First, redmine starts with webrick under jruby.

Second, I should mention that I run JRuby HEAD - not that this changes the objective.

Third, I'm planning to deploy on glassfish later today. Will feedback if any issues.

Actions #5

Updated by Marc Cooper over 15 years ago

All works okay on Glassfish. So, I guess this points to a mongrel issue.

Actions #6

Updated by Jean-Philippe Lang over 15 years ago

  • Status changed from New to Closed
  • Affected version (unused) deleted (devel)
  • Resolution set to Invalid

OK, thanks for the feedback.

Actions

Also available in: Atom PDF