[google-appengine] Re: Urgent: Channel API issues?
Yeah. Channel API will be permanently disabled on 31st OCT 2017. Here's the link for more info: https://cloud.google.com/appengine/docs/deprecations/channel On Saturday, January 7, 2017 at 12:45:38 PM UTC+5:30, Attila-Mihaly Balazs wrote: > > Just FYI from one channel user to the other: Channel is deprecated won't > be available as of December this year so you should start looking for > alternatives really soon. > > Attila > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7f0044d3-8943-488e-a4d4-6355bfe1220e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Urgent: Channel API issues?
Yeah. Issue has been fixed it seems. Brought back the old production version of our app to default which had real time notifications enabled. Working fine as expected. Thank you very much :) On Saturday, January 7, 2017 at 8:01:38 AM UTC+5:30, Ster Nem wrote: > > And of course after wasting all this time, it looks like it now works on > our sandbox environment. > > Of course my product environment is down because my quota has been > exceeded. 7 hours til reset. I hope Google compensates me for at least > today's "overuse" and more since my team has lost their Friday evening.. > > On Friday, January 6, 2017 at 9:26:34 PM UTC-5, Ster Nem wrote: >> >> Further details as my team have been debugging this for the past 3.5 >> hours. >> >> This part on our server returns error free: >> ChannelService channelService = >> ChannelServiceFactory.getChannelService(); >> token = channelService.createChannel(clientId, 1439); >> >> >> When we try and use this token it fails and as Ananthakrishnan desribes, >> our GWT code is setup to retry by creating a new channel. This killed our >> quota. >> >> We also have a java client using this channel and we are able debug. We >> are noticing that our parsing logic for the response from >> talkgadget.google.com doesn't seem to give us valid results. Something >> is wrong on that end. >> >> On Friday, January 6, 2017 at 8:53:10 PM UTC-5, Ananthakrishnan >> Venkatasubramanian wrote: >>> >>> Core problem for this issue is socket onopen handler is not getting >>> invoked instead onerror is getting called again and again. We are creating >>> a new channel token in onerror handler. So again and again, channel token >>> will be created, onerror handler invoked and it never goes to onopen >>> handler. The problem started on 07-JAN-2017 SATURDAY around 3:20 or 3:30 AM >>> IST onwards and it is still continuing. So far for these many years/days it >>> was working fine. Waiting for the fix so that we can turn on the real time >>> notifications back in our system. >>> >>> On Saturday, January 7, 2017 at 7:03:20 AM UTC+5:30, Ananthakrishnan >>> Venkatasubramanian wrote: >>>> >>>> Yeah. Facing the same issue and the application got >>>> crashed/continuously reloaded for the users. Please address this a.s.a.p. >>>> Currently we have disabled the real time notifications and addressed the >>>> production app issue. >>>> >>>> On Saturday, January 7, 2017 at 4:57:25 AM UTC+5:30, Ster Nem wrote: >>>>> >>>>> I use app engine channels to ensure my clients receive real-time >>>>> orders at their restaurant that they can fulfill. >>>>> >>>>> Within the past hour or so, I'm now getting this message when the >>>>> client side software tries to establish a channel: >>>>> >>>>> com.google.apphosting.api.ApiProxy$OverQuotaException: The API call >>>>> xmpp.CreateChannel() required more quota than is available. >>>>> >>>>> I'm definitely not over the quota, and I even have an idle sandbox app >>>>> engine id and can't seem to establish channels testing there. >>>>> >>>>> Anyone else see this issue? Can someone look into it? >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/fbacdd22-23be-48ec-8ad3-4a22ebbdad09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Urgent: Channel API issues?
Core problem for this issue is socket onopen handler is not getting invoked instead onerror is getting called again and again. We are creating a new channel token in onerror handler. So again and again, channel token will be created, onerror handler invoked and it never goes to onopen handler. The problem started on 07-JAN-2017 SATURDAY around 3:20 or 3:30 AM IST onwards and it is still continuing. So far for these many years/days it was working fine. Waiting for the fix so that we can turn on the real time notifications back in our system. On Saturday, January 7, 2017 at 7:03:20 AM UTC+5:30, Ananthakrishnan Venkatasubramanian wrote: > > Yeah. Facing the same issue and the application got crashed/continuously > reloaded for the users. Please address this a.s.a.p. Currently we have > disabled the real time notifications and addressed the production app issue. > > On Saturday, January 7, 2017 at 4:57:25 AM UTC+5:30, Ster Nem wrote: >> >> I use app engine channels to ensure my clients receive real-time orders >> at their restaurant that they can fulfill. >> >> Within the past hour or so, I'm now getting this message when the client >> side software tries to establish a channel: >> >> com.google.apphosting.api.ApiProxy$OverQuotaException: The API call >> xmpp.CreateChannel() required more quota than is available. >> >> I'm definitely not over the quota, and I even have an idle sandbox app >> engine id and can't seem to establish channels testing there. >> >> Anyone else see this issue? Can someone look into it? >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7149c4e9-a27d-463a-9a00-4af97927f12e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Urgent: Channel API issues?
Core problem for this issue is socket onopen handler is not getting invoked instead onerror is getting called again and again. We are creating a new channel token in onerror handler. So again and again, channel token will be created, onerror handler invoked and it never goes to onopen handler. The problem started around 3:20 or 3:30 AM IST onwards and it still continuing. So far for these many years/days it was working fine. Waiting for the fix so that we can turn on the real time notifications back in our system. On Saturday, January 7, 2017 at 7:03:20 AM UTC+5:30, Ananthakrishnan Venkatasubramanian wrote: > > Yeah. Facing the same issue and the application got crashed/continuously > reloaded for the users. Please address this a.s.a.p. Currently we have > disabled the real time notifications and addressed the production app issue. > > On Saturday, January 7, 2017 at 4:57:25 AM UTC+5:30, Ster Nem wrote: >> >> I use app engine channels to ensure my clients receive real-time orders >> at their restaurant that they can fulfill. >> >> Within the past hour or so, I'm now getting this message when the client >> side software tries to establish a channel: >> >> com.google.apphosting.api.ApiProxy$OverQuotaException: The API call >> xmpp.CreateChannel() required more quota than is available. >> >> I'm definitely not over the quota, and I even have an idle sandbox app >> engine id and can't seem to establish channels testing there. >> >> Anyone else see this issue? Can someone look into it? >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/de89d2ae-465a-42cf-906c-117b39830cd8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Urgent: Channel API issues?
Yeah. Facing the same issue and the application got crashed/continuously reloaded for the users. Please address this a.s.a.p. Currently we have disabled the real time notifications and addressed the production app issue. On Saturday, January 7, 2017 at 4:57:25 AM UTC+5:30, Ster Nem wrote: > > I use app engine channels to ensure my clients receive real-time orders at > their restaurant that they can fulfill. > > Within the past hour or so, I'm now getting this message when the client > side software tries to establish a channel: > > com.google.apphosting.api.ApiProxy$OverQuotaException: The API call > xmpp.CreateChannel() required more quota than is available. > > I'm definitely not over the quota, and I even have an idle sandbox app > engine id and can't seem to establish channels testing there. > > Anyone else see this issue? Can someone look into it? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f9cc1f7e-d8e8-41e0-ba57-f75513aa9b0d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: SearchException - Failed to complete request
Hey Nick, Will try your suggestion. Thanks for the quick response :) On Thursday, April 14, 2016 at 10:48:33 PM UTC+5:30, Nick (Cloud Platform Support) wrote: > > Hey Ananthakrishnan, > > While we are aware this can happen, as it has for other users in the past, > and we commit ourselves daily to maintaining the uptime of our systems, I'm > glad to hear that it is not consistent, and you have a retry logic. This is > indeed a best practice for distributed systems which need to have a higher > level of fault-tolerance and defensive programming (using incremental > backoff, etc.) than traditional single-system applications. > > Search API is a backend API service for App Engine, and it basically is a > distributed system. Hence it can happen that one job is stuck, takes longer > time to complete, and results in timeout. The exception only means that the > particular request timed out. If you would like to experiment with > different settings than a 10 second timeout, you can specify your desired > timeout value > <https://cloud.google.com/appengine/docs/java/javadoc/com/google/appengine/api/search/SearchServiceConfig.Builder#setDeadline-java.lang.Double-> > using > the setDeadline() method during building of the SearchService. > > I hope this response has been helpful - let me know if you have any > further questions and I'll be happy to assist. > > Sincerely, > > Nick > Cloud Platform Community Support > > On Thursday, April 14, 2016 at 4:10:52 AM UTC-4, Ananthakrishnan > Venkatasubramanian wrote: >> >> Hey Nick, >> >> Thanks for your kind reply. Will keep an eye on this thread for further >> updates. >> >> Regards, >> Ananthakrishnan. >> >> On Thursday, April 14, 2016 at 5:21:45 AM UTC+5:30, Nick (Cloud Platform >> Support) wrote: >>> >>> Hey Ananthakrishnan, >>> >>> This appears to be some kind of internal error, and is not something you >>> can necessarily prevent as a developer. It appears it has happened in >>> the past >>> <https://groups.google.com/forum/#!msg/google-appengine/ETydrw1RJ6Y/jrx1zgyfCgAJ> >>> >>> and was related to an internal issue. I'll look into this and report back >>> with any findings. >>> >>> Sincerely, >>> >>> Nick >>> Cloud Platform Community Support >>> >>> On Tuesday, April 12, 2016 at 10:51:18 AM UTC-4, Ananthakrishnan >>> Venkatasubramanian wrote: >>>> >>>> Hi, >>>> >>>> >>>> We have an application developed using Java running in google appengine. >>>> >>>> >>>> When AppEngine's Search API is accessed for querying the records, >>>> sporadically we get the following exception (not always). But when we try >>>> again it is responding with results. >>>> >>>> >>>> Stacktrace : >>>> Class : class com.google.appengine.api.search.SearchExceptionMessage : >>>> Failed to complete request in 9498ms >>>> >>>> at >>>> com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:355) >>>> at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:96) >>>> at >>>> com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73) >>>> at >>>> com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32) >>>> at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:506) >>>> >>>> >>>> Please let us know what is the issue behind this failure and what's the >>>> remedy for it. >>>> >>>> >>>> Thanks in Advance. >>>> >>>> >>>> Regards, >>>> >>>> Ananthakrishnan. >>>> >>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/9b76fbcf-587b-438a-9b68-0b57dd0e9a29%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: SearchException - Failed to complete request
Hey Nick, Thanks for your kind reply. Will keep an eye on this thread for further updates. Regards, Ananthakrishnan. On Thursday, April 14, 2016 at 5:21:45 AM UTC+5:30, Nick (Cloud Platform Support) wrote: > > Hey Ananthakrishnan, > > This appears to be some kind of internal error, and is not something you > can necessarily prevent as a developer. It appears it has happened in the > past > <https://groups.google.com/forum/#!msg/google-appengine/ETydrw1RJ6Y/jrx1zgyfCgAJ> > > and was related to an internal issue. I'll look into this and report back > with any findings. > > Sincerely, > > Nick > Cloud Platform Community Support > > On Tuesday, April 12, 2016 at 10:51:18 AM UTC-4, Ananthakrishnan > Venkatasubramanian wrote: >> >> Hi, >> >> >> We have an application developed using Java running in google appengine. >> >> >> When AppEngine's Search API is accessed for querying the records, >> sporadically we get the following exception (not always). But when we try >> again it is responding with results. >> >> >> Stacktrace : >> Class : class com.google.appengine.api.search.SearchExceptionMessage : >> Failed to complete request in 9498ms >> >> at >> com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:355) >> at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:96) >> at >> com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73) >> at >> com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32) >> at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:506) >> >> >> Please let us know what is the issue behind this failure and what's the >> remedy for it. >> >> >> Thanks in Advance. >> >> >> Regards, >> >> Ananthakrishnan. >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/94e93511-c735-4f01-963f-0b793394005d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Error code 206 in Google AppEngine
Hi, Thanks for the reply. Will file it in the issue tracker. For this particular issue, there is no stacktrace in the appengine logs. Only the mentioned Error Message came in the logs and the request was terminated with 500. On Wednesday, April 13, 2016 at 7:35:54 PM UTC+5:30, Nicholas (Google Cloud Support) wrote: > > Thanks for bringing this to our attention though this group is better > suited for best practices and implementation-type. For specific issues that > you believe to be problems with the platform, I would direct you to our > Public > Issue Tracker for App Engine > <https://code.google.com/p/googleappengine/issues/list>. That is a more > appropriate forum for this type of issue to get the appropriate attention. > > Should you file an issue there, please provide a link to it on this > thread, Also, since 500 errors can be served for almost any error in > application code, please include error logs, stack traces and code samples > that might be related on said issue. > > On Tuesday, April 12, 2016 at 10:42:28 AM UTC-4, Ananthakrishnan > Venkatasubramanian wrote: >> >> Hi, >> >> >> We have an application developed using Java running in Google AppEngine. >> >> >> Recently came across with following error in google appengine and >> returned 500 (production environment). >> >> >> *Error Message:* A problem was encountered with the process that handled >> this request, causing it to exit. This is likely to cause a new process to >> be used for the next request to your application.*(Error code 206)* >> >> >> The request ran for only 968ms and throwed 500 with the above message. >> >> >> *Note:* All the other requests that came prior to the same instance of >> the server didn't cause any errors. They ran successfully. >> >> >> Please provide the reasons for this kind of failure and what is the >> remedy for it. >> >> >> Thanks in Advance. >> >> >> Regards, >> >> Ananthakrishnan. >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/8116c7f6-5e24-429d-aac4-642ec669de65%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] SearchException - Failed to complete request
Hi, We have an application developed using Java running in google appengine. When AppEngine's Search API is accessed for querying the records, sporadically we get the following exception (not always). But when we try again it is responding with results. Stacktrace : Class : class com.google.appengine.api.search.SearchExceptionMessage : Failed to complete request in 9498ms at com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:355) at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:96) at com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73) at com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32) at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:506) Please let us know what is the issue behind this failure and what's the remedy for it. Thanks in Advance. Regards, Ananthakrishnan. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/3fa8c197-aa3a-4e85-a867-4bae0283794e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Error code 206 in Google AppEngine
Hi, We have an application developed using Java running in Google AppEngine. Recently came across with following error in google appengine and returned 500 (production environment). *Error Message:* A problem was encountered with the process that handled this request, causing it to exit. This is likely to cause a new process to be used for the next request to your application.*(Error code 206)* The request ran for only 968ms and throwed 500 with the above message. *Note:* All the other requests that came prior to the same instance of the server didn't cause any errors. They ran successfully. Please provide the reasons for this kind of failure and what is the remedy for it. Thanks in Advance. Regards, Ananthakrishnan. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7dd2db34-6a84-4895-b0e2-73788bef51e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Full Text Search API: com.google.appengine.api.search.SearchException: Temporary search service error
Hi, We are running the FullText Search feature in production for the past 15 days. Found the following weird behaviour sometimes in fulltext search while accessing the results via the application developed in JAVA. *com.google.appengine.api.search.SearchException: Temporary search service error* at com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:357) at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:94) at com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73) at com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32) at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:505) *Note:* This error is not happening always. Atleast 5-10, we are getting this error per day. But on next try, it is returning the results without any error. Please give us a direction as how to solve this problem. Thanks. Regards, Anantha Krishnan. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] FullText Search: Latency Issue - Not showing results
Hi, Clearly the search request came into the instance that has been running for some time. Document was indexed successfully at 12:00:09 (UTC) and the request for search came in at 12:00:45 (UTC), 12:01:47 (UTC), 12:01:49 (UTC), 12:03:08 (UTC) 12:03:24 (UTC). There was no instance restarts during these time. Only in the last request came in at 12:03:24 (UTC), the results came successfully (1 record found) and the other 4 requests for search which came after indexing the document failed to return results (ie...0 records found was the result being returned). Please let me know if you need any other information regarding this. Thanks. Regards, Anantha Krishnan. On Monday, January 20, 2014 1:52:01 PM UTC+5:30, Vinny P wrote: On Sat, Jan 18, 2014 at 1:34 AM, Ananthakrishnan Venkatasubramanian ananthakrishnan.venkatasubraman...@a-cti.com javascript: wrote: Why didn't the first query give the results when i tried for the first time both in text search viewer as well as via the application? Does this occur primarily on new App Engine instances, or instances that have been running for some time? Sometimes newly-created instances have difficulties accessing App Engine services. You can test this by examining the instance IDs on each log. On Sat, Jan 18, 2014 at 1:34 AM, Ananthakrishnan Venkatasubramanian ananthakrishnan.venkatasubraman...@a-cti.com javascript: wrote: Hi, We are a premium account user Just FYI, this forum is open to all, not just premium accounts. If you want to utilize your premium support, you should email or call Google with the contact information that you received as part of your support package. I try to give people the same level of advice and explanation regardless whether they have free or paid accounts :-) - -Vinny P Technology Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] FullText Search: Latency Issue - Not showing results
Hi, We are a premium account user. We are running the FullText Search feature in production for the past 3 days. Found the following weird behaviour in fulltext search while accessing the results via the application as well as text search viewer. field1 = (value1 OR value2 OR value3) AND field2 = (value4) Didn't return any results either from the application or the text search viewer which is weird because the data was created and indexed as a document successfully. Then I tried the following in the viewer by removing the field1 filter, field2 = (value4) It showed up the result in text search viewer successfully. Finally i tried the first query again which has the extra filter which is this, field1 = (value1 OR value2 OR value3) AND field2 = (value4) It showed up the results in the text search viewer successfully. The same first query which is shown above gave results via the application also after that. Why didn't the first query give the results when i tried for the first time both in text search viewer as well as via the application? Please give us a direction as how to solve this problem. Thanks. Regards, Anantha Krishnan -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Problem in Full Text Search - com.google.appengine.api.search.SearchException: Transient error, please try again.
Hi, We are a premium account user. We are in the process of implementing full-text search in our application developed using Java. While searching for documents in an index with pagination using cursor, at one point of time we are getting the following exception as we paginate. Pagination does work for most of the cases though and then fails at some point of time with the exception. *com.google.appengine.api.search.SearchException: Transient error, please try again.* at com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:345) at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:94) at com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73) at com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32) at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:497) at com.adaptavant.distributedsource.dao.SearchDAO.readIndex(SearchDAO.java:683) at com.adaptavant.distributedsource.service.SearchService.searchSimilarContacts(SearchService.java:3336) at com.adaptavant.distributedsource.controller.SearchController.searchSimilarContacts(SearchController.java:253) at sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_$1.run(Method_.java:179) at java.security.AccessController.doPrivileged(Native Method) at com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_.privilegedInvoke(Method_.java:176) at com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_.invoke_(Method_.java:137) at com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_.invoke(Method_.java:45) at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:219) at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:745) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:686) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:936) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:838) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:812) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.adaptavant.distributedsource.filter.JsonpCallbackFilter.doFilter(JsonpCallbackFilter.java:62) at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:125) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:35) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.JdbcMySqlConnectionCleanupFilter.doFilter(JdbcMySqlConnectionCleanupFilter.java:60) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at
[google-appengine] Problem in Full Text Search - com.google.appengine.api.search.PutException: Failed to complete request in 5622ms
Hi, We are a premium account user. We are in the process of implementing full-text search in our application developed using Java. While writing a document to an index, we are facing the failure sometimes sporadically and not always. Here's the following exception stacktrace for the same. *com.google.appengine.api.search.PutException: Failed to complete request in 5622ms* at com.google.appengine.api.search.IndexImpl$3.wrap(IndexImpl.java:306) at com.google.appengine.api.search.IndexImpl$3.wrap(IndexImpl.java:285) at com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:53) at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:90) at com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73) at com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32) at com.google.appengine.api.search.IndexImpl.put(IndexImpl.java:478) Please provide us a direction as to how to solve this problem. Thanks in advance for the solution. Regards, Anantha Krishnan -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Problem in Full Text Search - com.google.appengine.api.search.SearchException: Transient error, please try again.
Hi, We are a premium account user. We are in the process of implementing full-text search in our application developed using Java. While searching for documents in an index with pagination using cursor, at one point of time we are getting the following exception as we paginate. Pagination does work for most of the cases though and then fails at some point of time with the exception. *com.google.appengine.api.search.SearchException: Transient error, please try again.* at com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:345) at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:94) at com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73) at com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32) at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:497) Please provide us a direction as to how to solve this problem. Thanks. Regards, Anantha Krishnan. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Problem in Full Text Search - com.google.appengine.api.search.PutException: Failed to complete request in 5622ms
Hi, We are a premium account user. We are in the process of implementing full-text search in our application developed using Java. While writing a document to an index, we are facing the failure sometimes sporadically and not always. Here's the following exception stacktrace for the same. *com.google.appengine.api.search.PutException: Failed to complete request in 5622ms* at com.google.appengine.api.search.IndexImpl$3.wrap(IndexImpl.java:306) at com.google.appengine.api.search.IndexImpl$3.wrap(IndexImpl.java:285) at com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:53) at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:90) at com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73) at com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32) at com.google.appengine.api.search.IndexImpl.put(IndexImpl.java:478) at com.adaptavant.distributedsource.dao.SearchDAO.IndexADocument(SearchDAO.java:437) at com.adaptavant.distributedsource.service.SearchService.updateContactDocumentInIndex(SearchService.java:3494) at com.adaptavant.distributedsource.service.ContactService.createContactFromExportableMessage(ContactService.java:3861) at com.adaptavant.distributedsource.controller.JobController.createContactFromExportableMessage(JobController.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_$1.run(Method_.java:179) at java.security.AccessController.doPrivileged(Native Method) at com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_.privilegedInvoke(Method_.java:176) at com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_.invoke_(Method_.java:137) at com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_.invoke(Method_.java:45) at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:219) at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:745) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:686) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:936) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:838) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:812) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.adaptavant.distributedsource.filter.JsonpCallbackFilter.doFilter(JsonpCallbackFilter.java:62) at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:125) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:35) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.JdbcMySqlConnectionCleanupFilter.doFilter(JdbcMySqlConnectionCleanupFilter.java:60) at
Re: [google-appengine] SocketTimeoutException from one AppEngine Server to another
Hi, FYI: As you have suggested, we deployed the Server B as backend module and Server A as frontend module in the same App ID and used URLFetch in module A(Server A) to communicate with module B (Server B) of the same app. Still the same problem for one user who is using the application and that's me. So there is no question of exceeding the per minute quota limits or any other for that matter. As you have quoted: Longer-term, the even better option would be to refactor your application code so shared services are available as libraries and not as individual endpoints. Libraries will increase the size of the application or the parent module if you opt for modules. Deploying the app with libraries is old fashion...Its not good to follow if you consider the growth of the application. REST based service is the current trend. All this together, does that mean SOA (Service Oriented Architecture) or REST API Services will fluctuate in Google AppEngine (ie) from AppEngine Server to another AppEngine Server very often? Thanks. Regards, Anan On Wednesday, December 11, 2013 12:13:06 PM UTC+5:30, Ananthakrishnan Venkatasubramanian wrote: Hi, Definitely Server A is not exceeding the per minute quota for URLFetch API Calls (32,000 calls per min). SocketTimeOutExceptions are coming even there is less traffic in both the Servers. Note: We have idle instances in both the servers Definitely there is no question of queueing the requests also. Requests should be served at any point of time. As far as AppStats is concerned, we already knew how to do it. Its a matter of enabling. We will enable it and give you the information about it in private. As you have suggested, we deployed the Server B as backend module and Server A as frontend module in the same App ID and used URLFetch in module A(Server A) to communicate with module B (Server B) of the same app. Still the same problem. Those exceptions are repeating. The only thing we need to test now with modules is cut down the URLFetch in module A(Server A) and communicate directly with module B(Server B). Technically we need to integrate the codebase of Server B inside module A(Server A). This we can do it and try out from our end. But my question is, imagine there are two different organisation using AppEngine and one of the sever in the organisation running in AppEngine needs to communicate with the server in the other organisation running same in AppEngine, they have to communicate with URLFetch calls only. We cannot force the organisations to create one common App and use modules to avoid SocketTimeOutExceptions. Can you please give the appropriate reasons/solutions for the same? Please let me know if you need any other information regarding this. Thanks. Regards, Anantha Krishnan. On Wednesday, December 11, 2013 10:24:14 AM UTC+5:30, Vinny P wrote: On Tue, Dec 10, 2013 at 2:52 AM, Ananthakrishnan Venkatasubramanian ananthakrishnan.venkatasubraman...@a-cti.com wrote: Server A B represent different application IDs and the error rate depends on traffic. Most likely you are hitting App Engine per-minute rate limits then. Your traffic goes up, which leads to increased requests between your AB servers, which causes App Engine throttling to kick in to protect resource usage. The best way to fix this is to consolidate your applications; instead of running applications A and B, run them within a single application ID as separate versions or as different modules, then communicate intra-app using task queues and other methods. Longer-term, the even better option would be to refactor your application code so shared services are available as libraries and not as individual endpoints. On Tue, Dec 10, 2013 at 2:52 AM, Ananthakrishnan Venkatasubramanian ananthakrishnan.venkatasubraman...@a-cti.com wrote: We don't have appstats available at the moment. Why not? Install it using the guide available at: https://developers.google.com/appengine/docs/java/tools/appstats - -Vinny P Technology Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: SocketTimeoutException from one AppEngine Server to another
Hi, Thanks for the response. We have tried with minimum connectionTimeout and readTimeOuts also from 10-35 secs instead of using 60secs. Still the same problem. If we go in for Backend instead of Fronend in Server B, can you please tell me how that will solve this SocketTimeOutException? Thanks. Regards, Anantha Krishnan On Tuesday, December 10, 2013 5:09:57 PM UTC+5:30, timh wrote: You could well be in breach of the TOS doing this. (I assume you have checked) In addition if a front facing request is setting the deadline to 60 secs, and a front facing request maximum lifetime is 60 secs then it would seem you could run into troubles. Why not try with a short timeout and then retry? T On Tuesday, December 10, 2013 12:57:21 AM UTC+8, Ananthakrishnan Venkatasubramanian wrote: Hi, We are a Premier Account User in GoogleAppEngine. We have two front-end servers running on Google AppEngine developed using Java. Front-end server A communicates with another front-end server B using URLFetch(java.net) request. We have set the maximum connectionTimeOut and readTimeOuts (6ms) also for URLFetch in server A. All the requests from server A to B works successfully 70% of the time. But we are finding weird scenarios like 30% of the time where server A would have given URLFetch request to Server B and throwing java.net.SocketTimeoutException: Timeout while fetching URL. Note: The request from Server A to B remains dead air for 60 seconds and there aren't any request being received at Server B for the same. There are no instance restarts on both the servers. But when the client retries the request again, it runs successfully. We have 2 idle instances and instance classes configured to F4 on both the servers. Can we please know why the request from Server A timeouts out without a request being received at the other server end (ie) Server B? Thanks. Regards, Anantha Krishnan -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] SocketTimeoutException from one AppEngine Server to another
Hi, Definitely Server A is not exceeding the per minute quota for URLFetch API Calls (32,000 calls per min). SocketTimeOutExceptions are coming even there is less traffic in both the Servers. Note: We have idle instances in both the servers Definitely there is no question of queueing the requests also. Requests should be served at any point of time. As far as AppStats is concerned, we already knew how to do it. Its a matter of enabling. We will enable it and give you the information about it in private. As you have suggested, we deployed the Server B as backend module and Server A as frontend module in the same App ID and used URLFetch in module A(Server A) to communicate with module B (Server B) of the same app. Still the same problem. Those exceptions are repeating. The only thing we need to test now with modules is cut down the URLFetch in module A(Server A) and communicate directly with module B(Server B). Technically we need to integrate the codebase of Server B inside module A(Server A). This we can do it and try out from our end. But my question is, imagine there are two different organisation using AppEngine and one of the sever in the organisation running in AppEngine needs to communicate with the server in the other organisation running same in AppEngine, they have to communicate with URLFetch calls only. We cannot force the organisations to create one common App and use modules to avoid SocketTimeOutExceptions. Can you please give the appropriate reasons/solutions for the same? Please let me know if you need any other information regarding this. Thanks. Regards, Anantha Krishnan. On Wednesday, December 11, 2013 10:24:14 AM UTC+5:30, Vinny P wrote: On Tue, Dec 10, 2013 at 2:52 AM, Ananthakrishnan Venkatasubramanian ananthakrishnan.venkatasubraman...@a-cti.com javascript: wrote: Server A B represent different application IDs and the error rate depends on traffic. Most likely you are hitting App Engine per-minute rate limits then. Your traffic goes up, which leads to increased requests between your AB servers, which causes App Engine throttling to kick in to protect resource usage. The best way to fix this is to consolidate your applications; instead of running applications A and B, run them within a single application ID as separate versions or as different modules, then communicate intra-app using task queues and other methods. Longer-term, the even better option would be to refactor your application code so shared services are available as libraries and not as individual endpoints. On Tue, Dec 10, 2013 at 2:52 AM, Ananthakrishnan Venkatasubramanian ananthakrishnan.venkatasubraman...@a-cti.com javascript: wrote: We don't have appstats available at the moment. Why not? Install it using the guide available at: https://developers.google.com/appengine/docs/java/tools/appstats - -Vinny P Technology Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] SocketTimeoutException from one AppEngine Server to another
Hi, We are a Premier Account User in GoogleAppEngine. We have two front-end servers running on Google AppEngine developed using Java. Front-end server A communicates with another front-end server B using URLFetch(java.net) request. We have set the maximum connectionTimeOut and readTimeOuts (6ms) also for URLFetch in server A. All the requests from server A to B works successfully 70% of the time. But we are finding weird scenarios like 30% of the time where server A would have given URLFetch request to Server B and throwing java.net.SocketTimeoutException: Timeout while fetching URL. Note: The request from Server A to B remains dead air for 60 seconds and there aren't any request being received at Server B for the same. There are no instance restarts on both the servers. But when the client retries the request again, it runs successfully. We have 2 idle instances and instance classes configured to F4 on both the servers. Can we please know why the request from Server A timeouts out without a request being received at the other server end (ie) Server B? Thanks. Regards, Anantha Krishnan -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: SEARCH API: Problem in Adding Documents To An Index
Hi, When will this issue be fixed and ready to use. Waiting for the reply. Thanks. On Friday, May 18, 2012 9:42:35 AM UTC+5:30, Jeff Dutton wrote: I'm seeing this as well. It seems to have started for me at 2012-05-17 16:28:25.705 EST. On Thursday, May 17, 2012 11:51:33 PM UTC-4, Ananthakrishnan Venkatasubramanian wrote: Hi, I have been using Search API for my application so far successfully. I was able to add documents to index successfully yesterday. But when I tried to execute the same today, it gave me this exception. *Exception:* Caused by: java.lang.NoSuchMethodError: com.google.appengine.api.search.Index.add(Ljava/lang/Iterable;)Lcom/google/appengine/api/search/AddDocumentsResponse; I am trying to add only one document to an index and that its not working. Please give me the solution to solve this problem. Thanks. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/mHuXy9c-i9gJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] SEARCH API: Problem in Adding Documents To An Index
Hi, I have been using Search API for my application so far successfully. I was able to add documents to index successfully yesterday. But when I tried to execute the same today, it gave me this exception. *Exception:* Caused by: java.lang.NoSuchMethodError: com.google.appengine.api.search.Index.add(Ljava/lang/Iterable;)Lcom/google/appengine/api/search/AddDocumentsResponse; I am trying to add only one document to an index and that its not working. Please give me the solution to solve this problem. Thanks. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/wsrGcSVLNukJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Regarding Cursor Problem in SEARCH API
Hi, I am using SEARCH API to perform text search in my application developed using Google AppEngine (Platform: JAVA). I am facing problems with the cursor. Initially I won't have the cursor string and so by using following codes I am able to get first set of records that I needed along with the cursor string. *Code:* query = Query.newBuilder() .setOptions( QueryOptions.newBuilder().setLimit( limit ).setCursor( Cursor.newBuilder().build() ).build() ) .build( queryString ); searchResults = getIndex( accountPin ).search( query ); nextCursor = searchResults.getCursor().toWebSafeString(); *Result Cursor (nextCursor):* false:CqADCuUBCswB9wUnngv/c35zdGFnaW4tY21zAP//AIuSX19mdHNfXwD//wCiYXBwZW5naW5lAP//AIyLkmluZGV4AP//AKJNUDUwVlYA//8AjIuSZG9jX2lkAP//AKI4UUk3NDQA//8AjIA4UUk3NDQA//8AAP8B//6MgYyLnpiWkdKckoz/AHRtoKCZi4ygoP8AXZ6Pj5qRmJaRmv8Ac3RtlpGbmof/AF2yr8rPqan/AHN0bZuQnKCWm/8AXceutsjLy/8Ac3/HrrbIy8v/AP/+EAohwwIDw+6dfww5APRh2PpIARINRG9jdW1lbnRJbmRleBqfAShBTkQgKElTICJjdXN0b21lcl9uYW1lIiAiYXBwZW5naW5lIikgKElTICJncm91cF9uYW1lIiAic35zdGFnaW4tY21zIikgKElTICJuYW1lc3BhY2UiICIiKSAoSVMgImluZGV4X25hbWUiICJNUDUwVlYiKSAoT1IgKFFUICJ0ZXN0IikgKElTICJfX2dhdG9tX18iICJ0ZXN0IikpKUoFCABA6Ac= Is the result cursor which I showed above is a *websafestring*? I don't think so. If it is a *websafestring, *I should be able to put as parameter in URL and get the subsequent records. For the subsequent requests, I will use the following query. *CODE:* query = Query .newBuilder() .setOptions( QueryOptions.newBuilder().setLimit( limit ).setCursor( Cursor.newBuilder().build( nextCursor ) ).build() ) .build( queryType + queryString ); But when I try with the cursor what I have showed, its giving me an exception. *SAMPLE URL:* http://example.appspot.com/?queryType=allqueryString=** testlimit=10cursor=false:**CqADCuUBCswB9wUnngv/**c35zdGFnaW4tY21zAP//* *AIuSX19mdHNfXwD//**wCiYXBwZW5naW5lAP//**AIyLkmluZGV4AP//AKJNUDUwVlYA//** 8AjIuSZG9jX2lkAP//**AKI4UUk3NDQA//8AjIA4UUk3NDQA//** 8AAP8B//6MgYyLnpiWkdKckoz/**AHRtoKCZi4ygoP8AXZ6Pj5qRmJaRmv** 8Ac3RtlpGbmof/AF2yr8rPqan/**AHN0bZuQnKCWm/8AXceutsjLy/**8Ac3/HrrbIy8v/AP/http://29.stagin-cms.appspot.com/services/data/v1.0/objects/search/?apikey=MP50VVqueryType=allqueryString=testlimit=10cursor=false:CqADCuUBCswB9wUnngv/c35zdGFnaW4tY21zAP//AIuSX19mdHNfXwD//wCiYXBwZW5naW5lAP//AIyLkmluZGV4AP//AKJNUDUwVlYA//8AjIuSZG9jX2lkAP//AKI4UUk3NDQA//8AjIA4UUk3NDQA//8AAP8B//6MgYyLnpiWkdKckoz/AHRtoKCZi4ygoP8AXZ6Pj5qRmJaRmv8Ac3RtlpGbmof/AF2yr8rPqan/AHN0bZuQnKCWm/8AXceutsjLy/8Ac3/HrrbIy8v/AP/ EAohwwIDw 6dfww5APRh2PpIARINRG9jdW1l**bnRJbmRleBqfAShBTkQgKElTICJjdX** N0b21lcl9uYW1lIiAiYXBwZW5naW5l**IikgKElTICJncm91cF9uYW1lIiAic3** 5zdGFnaW4tY21zIikgKElTICJuYW1l**c3BhY2UiICIiKSAoSVMgImluZGV4X2** 5hbWUiICJNUDUwVlYiKSAoT1IgKFFU**ICJ0ZXN0IikgKElTICJfX2dhdG9tX1** 8iICJ0ZXN0IikpKUoFCABA6Ac= *Exception:* at com.google.appengine.api.**urlfetch.URLFetchServiceImpl.**conver tApplicationException(**URLFetchServiceImpl.java:115) at com.google.appengine.api.**urlfetch.URLFetchServiceImpl.**fetch( URLFetchServiceImpl.**java:42) at com.google.apphosting.utils.**security.urlfetch.**URLFetchServic eStreamHandler$**Connection.fetchResponse(**URLFetchServiceStreamHandler.** java:418) at com.google.apphosting.utils.**security.urlfetch.**URLFetchServic eStreamHandler$**Connection.getInputStream(**URLFetchServiceStreamHandler.** java:297)* * *I have used URLEncoder and URLDecoder for the cursor string.But that will not workSince it will replace '+' sign with empty space.* *Please suggest me a solution to fix this problem.* -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/w5LCFTLCWDoJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
