"7948"
=> Booting WEBrick...
=> Rails application started on http://0.0.0.0:3001
=> Ctrl-C to shutdown server; call with --help for options
[2007-11-25 12:46:49] INFO WEBrick 1.3.1
[2007-11-25 12:46:49] INFO ruby 1.8.6 (2007-06-07) [i486-linux]
[2007-11-25 12:46:49] WARN TCPServer Error: Address already in use - bind(2)
/usr/lib/ruby/1.8/webrick/utils.rb:73:in `initialize': Address already in use - bind(2) (Errno::EADDRINUSE)
from /usr/lib/ruby/1.8/webrick/utils.rb:73:in `new'
from /usr/lib/ruby/1.8/webrick/utils.rb:73:in `create_listeners'
from /usr/lib/ruby/1.8/webrick/utils.rb:70:in `each'
from /usr/lib/ruby/1.8/webrick/utils.rb:70:in `create_listeners'
from /usr/lib/ruby/1.8/webrick/server.rb:75:in `listen'
from /usr/lib/ruby/1.8/webrick/server.rb:63:in `initialize'
from /usr/lib/ruby/1.8/webrick/httpserver.rb:24:in `initialize'
from ./script/../config/../vendor/rails/railties/lib/webrick_server.rb:58:in `new'
... 8 levels...
from ./script/server:3:in `require'
from ./script/server:3
from -e:2:in `load'
from -e:2

Stopping and then attempting to start again produces the dialog with the text: "The server could not be started. The port is already in use."

One can kill the process from the command line and then start the server again within Aptana, but this is not a fluid way to work

Bug #4812 said this was fixed. But after the fix in that bug's history others have reported still having the issue, as am I. I was instructed to open a new bug by cwilliams in the forums.