On Tue, May 10, 2011 at 10:43 AM, Alex Katebi <alex.kat...@gmail.com> wrote:
> > > On Tue, May 10, 2011 at 11:01 AM, David Kahn > <d...@structuralartistry.com>wrote: > >> >> >> On Tue, May 10, 2011 at 9:56 AM, David Kahn >> <d...@structuralartistry.com>wrote: >> >>> >>> >>> On Tue, May 10, 2011 at 9:45 AM, Alex Katebi <alex.kat...@gmail.com>wrote: >>> >>>> I have restarted the server but not the computer. I am doing something >>>> abnormal. Off of a request I start some external program as sub processes. >>>> It takes about one second to start those sub processes. >>> >>> >>> Maybe you could post your code. One thing you might want to look at is if >>> you can start it using another thread -- >>> >> I avoided using Threads since I wanted my operations to be atomic. > So what does the 'desktop' app or code do? It is it something that your users depend on, and if so for what? What is the process? Of course first do what Colin asked and see if bypassing this process gets you back working so you at least know where to focus. > especially if you have something which is apparently volatile. I call >>> terminal commands all the time from my code, so itself should not be a >>> problem. One way to do this could be delayed_job but you can probably do it >>> much more simply using a new thread. See: >>> http://www.ruby-doc.org/core/classes/Thread.html >>> >> >> this looks pretty good as an intro to threading, if it turns out that this >> is the correct route to go: >> http://rubylearning.com/satishtalim/ruby_threads.html >> >> I guess though if your process is important you will have to add some >> handling in the case of failure if it were to happen. >> >> >>> >>> >>>> How long are we allowed to delay the sending of a respond? Is there a >>>> better way do this in Rails way? This problem is intermittent. >>>> >>>> On Tue, May 10, 2011 at 10:29 AM, David Kahn <d...@structuralartistry.com >>>> > wrote: >>>> >>>>> >>>>> >>>>> On Tue, May 10, 2011 at 9:25 AM, Alex Katebi <alex.kat...@gmail.com>wrote: >>>>> >>>>>> >>>>>> I see nothing any where. >>>>>> >>>>> >>>>> To clarify, on your server terminal window, you see no output when you >>>>> try to access a page? And of course the page does not load, I assume. It >>>>> is >>>>> probably not this if you are seeing nothing at all on the terminal, but >>>>> sometimes if I forget to remove a debugger line and still am running the >>>>> server in --debugger mode then of course it hangs. >>>>> >>>>> Otherwise, other obvious quations: have you restarted the server? As >>>>> well, restarted your computer? >>>>> >>>>> >>>>>> >>>>>> On Mon, May 9, 2011 at 4:58 PM, Colin Law <clan...@googlemail.com>wrote: >>>>>> >>>>>>> On 9 May 2011 21:54, Alex Katebi <alex.kat...@gmail.com> wrote: >>>>>>> > If my Rails server has been sitting idle for a while, it does not >>>>>>> respond to >>>>>>> > new requests. >>>>>>> > What is the best way to troubleshoot something like that. >>>>>>> > I am using Rails 3.0.7 in development. >>>>>>> >>>>>>> Is there anything in development.log when you submit the request (or >>>>>>> already there indicating a problem before the request)? What about >>>>>>> in >>>>>>> the server terminal window? >>>>>>> >>>>>>> Colin >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Ruby on Rails: Talk" group. >>>>>>> To post to this group, send email to >>>>>>> rubyonrails-talk@googlegroups.com. >>>>>>> To unsubscribe from this group, send email to >>>>>>> rubyonrails-talk+unsubscr...@googlegroups.com. >>>>>>> For more options, visit this group at >>>>>>> http://groups.google.com/group/rubyonrails-talk?hl=en. >>>>>>> >>>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Ruby on Rails: Talk" group. >>>>>> To post to this group, send email to >>>>>> rubyonrails-talk@googlegroups.com. >>>>>> To unsubscribe from this group, send email to >>>>>> rubyonrails-talk+unsubscr...@googlegroups.com. >>>>>> For more options, visit this group at >>>>>> http://groups.google.com/group/rubyonrails-talk?hl=en. >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Ruby on Rails: Talk" group. >>>>> To post to this group, send email to rubyonrails-talk@googlegroups.com >>>>> . >>>>> To unsubscribe from this group, send email to >>>>> rubyonrails-talk+unsubscr...@googlegroups.com. >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/rubyonrails-talk?hl=en. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Ruby on Rails: Talk" group. >>>> To post to this group, send email to rubyonrails-talk@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> rubyonrails-talk+unsubscr...@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/rubyonrails-talk?hl=en. >>>> >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Talk" group. >> To post to this group, send email to rubyonrails-talk@googlegroups.com. >> To unsubscribe from this group, send email to >> rubyonrails-talk+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/rubyonrails-talk?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-talk@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
