Hello Robert,

 Thanks a tonn for all your replies.
 I have checked the front end code last time it failed using the other
versions and it works just fine. So the client code is surely OK.

 I had also cheked for packet loss and the connection also seemed to be
good.

 And Yes I am using a custom Domain Name. But why would it not redirect to
the application ? If this is the issue, are there any possible solutions you
could guide me through .

Thanks and Regards,
Anupam M.

On Sat, May 1, 2010 at 11:57 PM, Robert Kluin <[email protected]>wrote:

> Hi Anupam,
>  I would say if you are not even seeing the requests show up in your
> apps request log, it is never hitting your app.
>
>  Can you use the same front end code to access one of the other
> versions?  If that works consistently at least you can be more
> confident the front end is OK.
>
>  I would say your next steps are going to be debugging their network
> connection.  Next time it is not working correctly, I would probably
> check your packet loss rate.  If that is high you'll know you got
> network issues. I would then check to be sure the name is being
> resolved correctly.  Are you directly accessing the app at
> appname.appspot.com or are you using a custom domain name?  If you are
> using a custom name I would be sure it is getting redirected
> correctly.
>
>  I think I would just follow through that type of debugging process.
>
> Robert
>
>
>
> On Sat, May 1, 2010 at 3:11 AM, WeShine Tech <[email protected]>
> wrote:
> > Hello Robert,
> >      Yes, I am not getting any actual error messages.
> >
> >       When the application is down, it does not show any request. Also
> there
> > is nothing shown in the logs.
> >
> >       Yes, As far as my knowledge is concerned there should not be any
> front
> > end issue. Can you suggest me somethings I could verify. Also like I
> > mentioned before my other versions of the applications worked fine after
> > this one was down. So one more reason why I beleive it must be the front
> end
> > issue.
> >
> >      I have been in discussions with Google Support team over the same
> issue
> > as well. They suggested it is latency issue and that I need to optimize
> my
> > application. But again only some requests should be stoped and the rest
> my
> > application should have continued working. So any suggestions on that ?
> >
> > Thanks and Regards,
> > Anupam M.
> >
> > On Fri, Apr 30, 2010 at 8:57 PM, Robert Kluin <[email protected]>
> > wrote:
> >>
> >> So you are not getting any actual error messages?
> >>
> >> Do you see requests showing up in the request log when expected?  When
> >> you tell your app to do something does a request show up?
> >>
> >> Are you sure you do not have a front-end issue?
> >>
> >> Robert
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Apr 28, 2010 at 11:44 PM, WeShine Tech
> >> <[email protected]> wrote:
> >> > Hello Robert,
> >> >       The errors that I see are mostly warning for the CPU consumption
> >> > exceeding the quota limit. I read on some thread that if one of the
> url
> >> > requests exceeds the quota limit the application goes down. I just
> want
> >> > to
> >> > confirm this.
> >> >      Also this request is a simple async service (GWT). So if I just
> >> > split
> >> > this service into multiple services will my issue be solved ?
> >> >      Also once the application is down, when I can expect it to start
> >> > again.
> >> >     Answers to the rest of the questions:
> >> >     Between the versions there have been some minor bug fixes. However
> I
> >> > checked the logs of the older version and realized the          same
> log
> >> > regarding the CPU warning did exist at both the versions. So what I
> >> > could
> >> > conclude is that may be the quota did not exceed the limit for my
> older
> >> > version because it had comparatively less load.
> >> >
> >> >     I did check the whole log in detail and did not find any such log
> >> > which
> >> > would say :
> >> > This request caused a new process to be started for your
> >> > application, and thus caused your application code to be loaded for
> >> > the first time. This request may thus take longer and use more CPU
> >> > than a typical request for your application.
> >> >     And regarding the cold start, can I expect any message in the log
> >> > regarding the same ?
> >> >
> >> >
> >> >
> >> > On Wed, Apr 28, 2010 at 7:44 PM, Robert Kluin <[email protected]
> >
> >> > wrote:
> >> >>
> >> >> Anupam,
> >> >>
> >> >>   What are the actual errors you are seeing?  Are errors in your
> >> >> app's error log?
> >> >>
> >> >>   Further comments / questions inline:
> >> >>
> >> >
> >> >
> >> >>
> >> >> On Wed, Apr 28, 2010 at 12:31 AM, WeShine Tech
> >> >> <[email protected]> wrote:
> >> >> >  Hello Robert,
> >> >> >
> >> >> >       Are you saying that you have other clients (customers)
> running
> >> >> > the
> >> >> > same code on different deployments ?
> >> >> >      No. So what happened is at my clients site the
> >> >> > application stopped responding. So I started using the earlier
> >> >> > versions
> >> >> > of
> >> >> > my application and those seemed to work fine.
> >> >>
> >> >> What has changed between versions?  Have you added additional request
> >> >> handlers, or otherwise increased the work that needs done to load
> your
> >> >> app?
> >> >>
> >> >>
> >> >>
> >> >> >     When you say the log shows latency issues I assume you mean the
> >> >> > requests
> >> >> > are taking
> >> >> > a lot of CPU time?
> >> >> >      That is correct. But the same requests work absolutely fine
> >> >> > otherwise.
> >> >> > So why would some requests take a lot of CPU time only on
> >> >> > some occasions where as work efficiently most of the times? Could
> you
> >> >> > share
> >> >> > some tippers for resolving this issue.
> >> >>
> >> >> If the app sits idle it will be unloaded from the app severs.  As I
> >> >> understand, apps may be more aggressively unloaded during times when
> >> >> the overall traffic to app engine itself is high.  What you are
> >> >> describing sounds like this could be the issue.
> >> >>
> >> >> Look in your apps info log for messages like:
> >> >>   This request caused a new process to be started for your
> >> >> application, and thus caused your application code to be loaded for
> >> >> the first time. This request may thus take longer and use more CPU
> >> >> than a typical request for your application.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> >     The application is not a very high traffic one because of its
> >> >> > nature.
> >> >> > However after receiving high amount of load for almost two hours it
> >> >> > went
> >> >> > down. Also it has performed very well with more traffic in the
> past.
> >> >> > So
> >> >> > I am
> >> >> > not sure it could be the Cold Start.
> >> >>
> >> >> This is almost the definition of the 'cold start' problem:  it does
> >> >> well under load, but once there is a drop in traffic you get
> >> >> performance issues.
> >> >>
> >> >>
> >> >>
> >> >> > Thanks and Regards,
> >> >> > Anupam M.
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Wed, Apr 28, 2010 at 9:31 AM, Robert Kluin
> >> >> > <[email protected]>
> >> >> > wrote:
> >> >> >>
> >> >> >> Anupam,
> >> >> >>  Are you saying that you have other clients (customers) running
> the
> >> >> >> same code on different deployments, or are you saying you have
> >> >> >> loaded
> >> >> >> this app more heavily while running the current code?  When you
> say
> >> >> >> the log shows latency issues I assume you mean the requests are
> >> >> >> taking
> >> >> >> a lot of CPU time?
> >> >> >>
> >> >> >> It sounds like the app is not very high traffic.  Could this be
> the
> >> >> >> cold start issue?  If you hit the site a lot (once every couple
> >> >> >> seconds) does it respond OK?
> >> >> >>
> >> >> >>
> >> >> >> Robert
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> On Tue, Apr 27, 2010 at 11:35 PM, WeShine Tech
> >> >> >> <[email protected]> wrote:
> >> >> >> > I did look into the problem and have been suggested that it
> could
> >> >> >> > be
> >> >> >> > due
> >> >> >> > to
> >> >> >> > latency issues. Please could you guide me through as to how to
> fix
> >> >> >> > this.
> >> >> >> > I
> >> >> >> > have used the same code with more number of clients before but
> >> >> >> > never
> >> >> >> > faced a
> >> >> >> > problem like this.
> >> >> >> > The logs also show latency issues. And I did run the older
> version
> >> >> >> > of
> >> >> >> > my
> >> >> >> > application using the appspot url. The older version performed
> >> >> >> > just
> >> >> >> > fine.
> >> >> >> > However I did not try running the application using the
> >> >> >> > "appname.appspot.com" url.
> >> >> >> >
> >> >> >> >
> >> >> >> > On Tue, Apr 27, 2010 at 11:44 PM, Robert Kluin
> >> >> >> > <[email protected]>
> >> >> >> > wrote:
> >> >> >> >>
> >> >> >> >> Were there any actual exceptions in the app's log?
> >> >> >> >>
> >> >> >> >> Did you see the requests in the request log?
> >> >> >> >>
> >> >> >> >> If you were using a custom domain, could you access the site
> >> >> >> >> directly
> >> >> >> >> at the 'appname'.appspot.com url?
> >> >> >> >>
> >> >> >> >> Robert
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> On Mon, Apr 26, 2010 at 9:52 AM, WeShine Tech
> >> >> >> >> <[email protected]> wrote:
> >> >> >> >> > Hello,
> >> >> >> >> >        I have an application which requires resources just on
> >> >> >> >> > some
> >> >> >> >> > particular days. However today my application actually failed
> >> >> >> >> > at
> >> >> >> >> > my
> >> >> >> >> > clients site. The application logs do read some high CPU
> usage
> >> >> >> >> > for
> >> >> >> >> > some of the url but that is it. It would completely stop
> >> >> >> >> > responding
> >> >> >> >> > at
> >> >> >> >> > times for all and any requests. Please suggest me some work
> >> >> >> >> > around
> >> >> >> >> > for
> >> >> >> >> > this problem. I have started my billing and have allowed a
> >> >> >> >> > large
> >> >> >> >> > number of resources to be consumed per day. The consumption
> >> >> >> >> > shown
> >> >> >> >> > in
> >> >> >> >> > the admin console is as low as 1% of what has been allocated.
> >> >> >> >> >
> >> >> >> >> > Do let me know if there is any more information required to
> be
> >> >> >> >> > shared
> >> >> >> >> > from my side. But the problem is extremely critical and needs
> >> >> >> >> > to
> >> >> >> >> > be
> >> >> >> >> > fixed as soon as possible.
> >> >> >> >> >
> >> >> >> >> > Any help is appreciated.
> >> >> >> >> >
> >> >> >> >> > Thanks and Regards,
> >> >> >> >> > Anupam M.
> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> > You received this message because you are subscribed to the
> >> >> >> >> > Google
> >> >> >> >> > Groups "Google App Engine" group.
> >> >> >> >> > To post to this group, send email to
> >> >> >> >> > [email protected].
> >> >> >> >> > To unsubscribe from this group, send email to
> >> >> >> >> > [email protected]<google-appengine%[email protected]>
> .
> >> >> >> >> > For more options, visit this group at
> >> >> >> >> > http://groups.google.com/group/google-appengine?hl=en.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> You received this message because you are subscribed to the
> >> >> >> >> Google
> >> >> >> >> Groups
> >> >> >> >> "Google App Engine" group.
> >> >> >> >> To post to this group, send email to
> >> >> >> >> [email protected].
> >> >> >> >> To unsubscribe from this group, send email to
> >> >> >> >> [email protected]<google-appengine%[email protected]>
> .
> >> >> >> >> For more options, visit this group at
> >> >> >> >> http://groups.google.com/group/google-appengine?hl=en.
> >> >> >> >>
> >> >> >> >
> >> >> >> > --
> >> >> >> > You received this message because you are subscribed to the
> Google
> >> >> >> > Groups
> >> >> >> > "Google App Engine" group.
> >> >> >> > To post to this group, send email to
> >> >> >> > [email protected].
> >> >> >> > To unsubscribe from this group, send email to
> >> >> >> > [email protected]<google-appengine%[email protected]>
> .
> >> >> >> > For more options, visit this group at
> >> >> >> > http://groups.google.com/group/google-appengine?hl=en.
> >> >> >> >
> >> >> >>
> >> >> >> --
> >> >> >> You received this message because you are subscribed to the Google
> >> >> >> Groups
> >> >> >> "Google App Engine" group.
> >> >> >> To post to this group, send email to
> >> >> >> [email protected].
> >> >> >> To unsubscribe from this group, send email to
> >> >> >> [email protected]<google-appengine%[email protected]>
> .
> >> >> >> For more options, visit this group at
> >> >> >> http://groups.google.com/group/google-appengine?hl=en.
> >> >> >>
> >> >> >
> >> >> > --
> >> >> > You received this message because you are subscribed to the Google
> >> >> > Groups
> >> >> > "Google App Engine" group.
> >> >> > To post to this group, send email to
> >> >> > [email protected].
> >> >> > To unsubscribe from this group, send email to
> >> >> > [email protected]<google-appengine%[email protected]>
> .
> >> >> > For more options, visit this group at
> >> >> > http://groups.google.com/group/google-appengine?hl=en.
> >> >> >
> >> >>
> >> >> --
> >> >> You received this message because you are subscribed to the Google
> >> >> Groups
> >> >> "Google App Engine" group.
> >> >> To post to this group, send email to
> [email protected].
> >> >> To unsubscribe from this group, send email to
> >> >> [email protected]<google-appengine%[email protected]>
> .
> >> >> For more options, visit this group at
> >> >> http://groups.google.com/group/google-appengine?hl=en.
> >> >>
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google
> >> > Groups
> >> > "Google App Engine" group.
> >> > To post to this group, send email to
> [email protected].
> >> > To unsubscribe from this group, send email to
> >> > [email protected]<google-appengine%[email protected]>
> .
> >> > For more options, visit this group at
> >> > http://groups.google.com/group/google-appengine?hl=en.
> >> >
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Google App Engine" group.
> >> To post to this group, send email to [email protected].
> >> To unsubscribe from this group, send email to
> >> [email protected]<google-appengine%[email protected]>
> .
> >> For more options, visit this group at
> >> http://groups.google.com/group/google-appengine?hl=en.
> >>
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<google-appengine%[email protected]>
> .
> > For more options, visit this group at
> > http://groups.google.com/group/google-appengine?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<google-appengine%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to