I've just upgraded to rails 3. Beside some problems on the page I experience as well a strange latency after running the test environment for a while... The speed is normal but after a few clicks on the page, it suddenly "freezes" and needs about a minute to load the page. Unfortunately it doesn't matter where I click though. Just after the test environment was running for a while it shows up to suddenly have this problem. Even when I want to stop the server it needs a minute to do so. Restarting the server let it working for a while
Thanks for any help
Markus
If you are on Mac or Linux, try installing RVM and installing Ruby Enterprise Edition .
Related
I just installed the version 1.21 of pestphp/pest for a small php library.
Installations works until I try running ./vendor/bin/pest
I keep getting this error: Exclusive locks are not supported for this stream
Research on this error has proven unsuccessful as I could not find a similar case.
Please let me know if you've experienced this before and how you fixed it.
Thanks!
I have figured out the issue.
I was running the application from the htdocs of the vm version of xampp running on my laptop.
Taking the project out of here into another directory solved this issue.
Hope this saves someone else some time.
I am using the OS Ubuntu 12.04 and I have installed Netbeans 7.0.1 on it, my laptop's configuration is pretty good but still Netbeans runs really really slow on it and it hangs completely after using it only for a few mins. On doing some research I found that many people suggested to add the following line in the netbeans.conf file "netbeans_jdkhome="/usr/lib/jvm/java-1.7.0-openjdk-amd64"
which I did but nothing has changed. It still lags a lot.
I can think of a couple of things I would try. Firstly, upgrade to NetBeans 7.4 as recent versions of NetBeans do more work in background threads, improving the general responsiveness of the application.
Secondly, in the etc directory of the NetBeans install (on Windows) there's a netbeans.conf. Try editing the netbeans_default_options property to set -J-Xmx to something large, maybe 256m or 512m. That should give NB a bit more space to play with.
I have been trying to install IonCube for the past 2 days on my localhost, and it just won't show up. Today I tried changing the PHP versions to force some sort of hard refresh, and MAMP is not changing versions.
By the looks of this, in my opinion, Apache is not restarting at all, how can I force it to stop with a Terminal command or something?
Thanks in advance.
The short and sweet is to restart your machine entirely, fine for if you're just a local developer.
I am using Ruby on Rails under windows, installed with railsinstaller. Everything works fine, except that any command such as rails console or bundle exec rake db:migrate takes on average 8 seconds before executing. (rails s and rails -v are exceptions and take about 1 to 2 sec to launch, which is still abnormally high). I am not talking about the time of the entire command, just the time between when I hit enter and when I see the first output.
During this time, one core of my processor is working at 100%, and there is no load on the hard drive. I really feel like that I am waiting for some kind of timeout to expire, because I don't see why rails console should take that much processing power (I have a Core 2 Duo processor).
Do you have experienced this kind of problem ? What can it be ? How can I investigate this ?
It is spinning up your Rails environment, not just loading an executable. It is not Windows specific. It takes about 10 seconds on my Core2 Duo iMac. I've seen similar delays on Linux boxes. Here is an article that gives some hints that may help.
rails-3-osx-speed-up-console-loading-time
Newbie here. I created a rails project in rubymine to run the default index.html from public folder I pressed 'shift' + F10 key. This is same as rails server from the terminal. This is what I get:
/home/bubble/.rvm/rubies/ruby-1.9.2-p180/bin/ruby -e $stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift) /home/bubble/Desktop/Hard Boiled Bubble/bubbles/script/rails server -b 0.0.0.0 -p 3334 -e development
=> Booting Mongrel
=> Rails 3.1.0.rc1 application starting in development on http://0.0.0.0:3334
=> Call with -d to detach
=> Ctrl-C to shutdown server
Nice clean. But now I cannot shutdown the server. It simply doesn't work. Neither from terminal nor rubymine. I have to kill the process from the system monitor everytime.
Any clues, of what can be wrong in my set up? Is is because of rails 3.1.0.rc --pre ??
Got similar issue with Rubymine 3.1 (it do not seems to be a Rubymine issue) and rails 3.0.9 (it also do not seems to be a Rails issue). Om my computer I have the same problem by running the erver from the console.
Try running rails s in the console from your application directory, and stop the process (server) by pressing Ctrl+C.
On my Ubuntu 11.4 + Rails 1.9.2 (via RVM) it doesn't work as well, proving the issue do not come from Rubymine.
Looking around the web, it is quite common that ruby server "stale", but it is the very first time I see it, and didn't get the solution for now (sorry for that).
Last but not least ! Process stale with all ruby server I tried : Webrick, Mongrel & Thin. Making me think, it is a ruby issue, it seems that the stop signal does not arrive to the server...
I'll also be glad, if somebody has some more clues to fix this.
This is actually quite a common that myself and other developers see. It's nothing to do with the rails version. It happens in all versions. It's just that the server becomes a detached process and can be hard to find.
However I've learned to cope with it pretty well thanks to things I learned:-
Always use the red square to stop the server, not the red X.
If the server hangs, rather than rebooting you can just use the menu option for run... and change the port number, say from 3334 to 3335 (and so on). It sounds bad but it really doesn't hurt and only take 3 seconds...
If necessary you can also keep a terminal window open and run the server from that and just use rubyMine for editing, but then you are missing out on a lot of rubyMine features and also you have to keep both environments working ok.
It may be specific to Ubuntu as that is where I have seen it too.