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.

Bug 124390 - Mongrel vs. WEBrick
Summary: Mongrel vs. WEBrick
Status: RESOLVED FIXED
Alias: None
Product: ruby
Classification: Unclassified
Component: Rails (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-22 16:11 UTC by lyhy
Modified: 2008-01-17 15:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lyhy 2007-12-22 16:11:46 UTC
First of all: LOVE THE IDE! I was a RadRails/Aptana guy for months, but your efforts blow them away.

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.

Here's the complaint: I started looking for how to change from WEBrick to Mongrel, and you know what - ain't easy! I
couldn't find anything in the online doc and had to hunt and peck through several pages of your website before I found
out how to use Mongrel over WEBrick. (Install the plugin and restart the server.)

This is not a minor issue that maybe a dozen or so people will look into. 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*.
Comment 1 Martin Krauskopf 2008-01-06 20:16:18 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.
Comment 2 Torbjorn Norbye 2008-01-06 22:29:17 UTC
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.
Comment 3 lyhy 2008-01-07 12:37:22 UTC
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' "

Comment 4 Erno Mononen 2008-01-17 15:47:28 UTC
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.