Instance stop method called for pid '8382'
Starting jetty with these values:
jetty_home: /Users/atz/repos/argo/jetty
jetty_command: java -Djetty.port=8983 -Dsolr.solr.home=/Users/atz/repos/argo/jetty/solr -XX:MaxPermSize=256m -Xmx256m -jar start.jar
rake aborted!
Port 8983 is already in use.
/Users/atz/.rvm/gems/ruby-1.9.3-p547/gems/jettywrapper-1.8.2/lib/jettywrapper.rb:358:in `start'
/Users/atz/.rvm/gems/ruby-1.9.3-p547/gems/jettywrapper-1.8.2/lib/jettywrapper.rb:233:in `start'
/Users/atz/.rvm/gems/ruby-1.9.3-p547/gems/jettywrapper-1.8.2/lib/tasks/jettywrapper.rake:43:in `block (2 levels) in <top (required)>'
/Users/atz/.rvm/gems/ruby-1.9.3-p547/bin/ruby_executable_hooks:15:in `eval'
/Users/atz/.rvm/gems/ruby-1.9.3-p547/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => jetty:restart
(See full trace by running task with --trace)
The old process isn't fully shut down when the new one tries to spin up. It needs to wait a few seconds between stop and start (preferably checking to see if the port actually becomes available).
The old process isn't fully shut down when the new one tries to spin up. It needs to wait a few seconds between stop and start (preferably checking to see if the port actually becomes available).