This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Mongrel vs. WEBrick | ||
---|---|---|---|
Product: | ruby | Reporter: | lyhy <lyhy> |
Component: | Rails | Assignee: | Erno Mononen <emononen> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
lyhy
2007-12-22 16:11:46 UTC
> Minor bug (with minor complaint): I use Mongrel but noticed the Status Bar in the bottom right said "WEBrick for > MyServer on 3001". So there's the bug - it reports the wrong server. Erno could you take a look at this one? > Mongrel vs. WEBrick is a BIG DEAL and how to deal with it should be addressed as such in the documentation, i.e. make it > *easy to find*. You are right. This will be addressed in the one of future releases (hopefully next). Should be solved as the part of the issue 114138. You might CC yourself to the issue to track the progress. Are you sure it's really running Mongrel, not Webrick? You must have the Mongrel gem installed for the Ruby interpreter you're running with. If that interpreter is JRuby (which is the default, change it under Tools > Ruby > Platform in 6.0) then you're probably really running webrick since Mongrel doesn't run on JRuby (except with some hacks; this is being worked on). When I tested the mongrel stuff (see http://wiki.netbeans.org/wiki/attach/RubyOnRails/mongrel.png for my output window which has the right label) I switched to native/C Ruby where I had installed the mongrel gem. 1) In "Tools>Options>Ruby>Ruby Interpreter" I have "C:\Programs\ruby-1.8.6\bin\ruby.exe" 2) I have the Mongrel plugin installed. Copied and pasted from my explorer window: "C:\Programs\ruby-1.8.6\lib\ruby\gems\1.8\gems\mongrel-1.1.2-x86-mswin32" 3) The contents of the "Output" window when I start my server: => Booting Mongrel (use 'script/server webrick' to force WEBrick) => Rails application starting on http://0.0.0.0:3001 => Call with -d to detach => Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3001 ** Starting Rails with development environment... ******************************************************************* * config.breakpoint_server has been deprecated and has no effect. * ******************************************************************* ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. INT => stop (no restart). ** Mongrel 1.1.2 available at 0.0.0.0:3001 ** Use CTRL-C to stop. 4) The title bar of the "Output" window: "Output - WEBrick for stupidtuesday on 3001" 5) The bottom right status area of the IDE: " WEBrick for stupidtuesday on 3001 'Running' " Fixed in trunk by the fix for issue 125084, in this case the Mongrel process was not recognized properly (the version string confused the server recognizer) and WEBrick was assumed as the default. |