[appengine-java] createEntityManager() taking too long
I'm using JPA and see that calls to createEntityManager() are taking several seconds (e.g., 6 seconds). This is with HRD and reserved instances. And it's not the first time either, subsequent calls are also slow. Is anyone else seeing this, and is there a way to speed these up? -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/MMVaNUzDPvoJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Channel API not working on development server
Channel API isn't working at all for me on development server - is there any setting that isn't default? Everything works fine when I upload. I'm using 1.5.2 Java. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/icGpSzipNRYJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] How do you prevent _ah requests from hitting the servlet filter?
Thanks Hari. If I understand you correctly, nothing stops unauthorized users from directly accessing internal pages (i.e., those other than login or index)...that's not acceptable for my app. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] How do you prevent _ah requests from hitting the servlet filter?
I'm building a healthcare app that will filter all requests (url pattern *, ideally). In the filter, I'm checking to see if the user is logged in and throwing the login page if he isn't (using Google user service). On the dev server this is a problem because the login page is simply a /_ah/login call and that will hit the filter again and cause an infinite loop. Is there a simple way to have the filter catch everything except some patterns like say /_ah/*? I don't want to enumerate all the URLs in the filter if I can avoid it. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: What is entity detached yet this operation requires it to be attached?
I can see why messing with a new entity outside a transaction before
persist is an issue if datanucleus.NontransactionalWrite is set to
false, but I have both datanucleus.NontransactionalRead and
datanucleus.NontransactionalWrite set to true and I still get the
error. The puzzling thing is this error comes up only once in a while
though the exact same code gets executed every time. Looks like
something intermittent...at least for me.
On Sep 3, 12:30 am, Didier Durand durand.did...@gmail.com wrote:
Hi,
This means that you are trying to act on an entity via the Persistence
Manager when this same entity is not yet under control of the PM.
It usually happens when you do a new on a Class and do not call the
persist() function of the PM for that newly created instance before
doing what you try to do then to reach the exception that you mention.
Hope it's clear even though without all details, I have to stay
abstract and generic...
regards
didier
On Sep 2, 8:45 pm, nksi n.nks...@gmail.com wrote:
I also have a similar problem.
in my exsample:
@Entity
class Test {
@Id
@Column(name = ID)
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
@Column(nullable = false)
private Boolean isLatest;
}
# service
Test test = TestDao.getByCode(code)
test.setIsLatest(false)
TestDao.save(createTest())
#warning-log
Request completed without committing or rolling back transaction with
id 7. Transaction will be rolled back.
When I comment out the line of TestDao.save(createTest()), test is
merged.
And when i comment out the lines to merge, TestDao.save is success.
I wanna merge and save for same Model.
why can't i do it?plz tell me about it.
On 7月21日, 午前12:56, Sekhar sek...@allurefx.com wrote:
Anyone? Would appreciate just about any help you can give!
On Jul 15, 8:45 am, Sekhar sek...@allurefx.com wrote:
I pretty frequently get an error for my JPA entities saying an entity
is is detached yet this operation requires it to be attached and the
transaction isrolledback:
com.google.apphosting.utils.servlet.TransactionCleanupFilter
handleAbandonedTxns: Request completed without committing or
rollingbacktransaction with id 6520345908250195886. Transaction will
berolledback.
What does this error mean and how do I get rid of this? I did check
the DataNucleus docs and didn't really get any info on this. I have
datanucleus.NontransactionalRead and datanucleus.NontransactionalWrite
both set to true and open the transactions only to do the merge - is
that the problem? E.g., something like:
ListMyEntity list = query.getResultList();
MyEntity e0 = list.get(0);
e0.setWhatever(whatever);
tx.begin();
entityManager.merge(e0);
tx.commit();
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: App Engine SDK 1.3.7 bugfix release
Eclipse is still showing 1.3.6...any ETA on that? On Aug 30, 4:12 pm, Ikai L (Google) ika...@google.com wrote: Hey everyone, I just wanted to let you all know that we're releasing a bugfix release, 1.3.7. You can see our blog post here: http://googleappengine.blogspot.com/2010/08/app-engine-137-sdk-bugfix... There are two issues this release addresses: - Python SDK will correctly assign a namespace based on a Google Apps domain - Java SDK will not longer throw a SecurityException (http://code.google.com/p/googleappengine/issues/detail?id=3598) You can find this release on our downloads page: http://code.google.com/appengine/downloads.html -- Ikai Lan Developer Programs Engineer, Google App Engine Blog:http://googleappengine.blogspot.com Twitter:http://twitter.com/app_engine Reddit:http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: What is entity detached yet this operation requires it to be attached?
Anyone? Would appreciate just about any help you can give! On Jul 15, 8:45 am, Sekhar sek...@allurefx.com wrote: I pretty frequently get an error for my JPA entities saying an entity is is detached yet this operation requires it to be attached and the transaction isrolledback: com.google.apphosting.utils.servlet.TransactionCleanupFilter handleAbandonedTxns: Request completed without committing or rollingbacktransaction with id 6520345908250195886. Transaction will berolledback. What does this error mean and how do I get rid of this? I did check the DataNucleus docs and didn't really get any info on this. I have datanucleus.NontransactionalRead and datanucleus.NontransactionalWrite both set to true and open the transactions only to do the merge - is that the problem? E.g., something like: ListMyEntity list = query.getResultList(); MyEntity e0 = list.get(0); e0.setWhatever(whatever); tx.begin(); entityManager.merge(e0); tx.commit(); -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] What is entity detached yet this operation requires it to be attached?
I pretty frequently get an error for my JPA entities saying an entity is is detached yet this operation requires it to be attached and the transaction is rolled back: com.google.apphosting.utils.servlet.TransactionCleanupFilter handleAbandonedTxns: Request completed without committing or rolling back transaction with id 6520345908250195886. Transaction will be rolled back. What does this error mean and how do I get rid of this? I did check the DataNucleus docs and didn't really get any info on this. I have datanucleus.NontransactionalRead and datanucleus.NontransactionalWrite both set to true and open the transactions only to do the merge - is that the problem? E.g., something like: ListMyEntity list = query.getResultList(); MyEntity e0 = list.get(0); e0.setWhatever(whatever); tx.begin(); entityManager.merge(e0); tx.commit(); -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Startup error (UnsupportedOperationException)
I keep getting an UnsupportedOperationException error on startup something like 80% of the time. If I'm lucky, I don't get it and the server runs fine from then on. Looks like some startup issue. If I remember, there was some thread saying this was the result of a race condition with DataNucleus, but I can't find that thread anymore. Could someone help please? This is getting a bit frustrating. Thanks! SEVERE: [1275287104906000] javax.servlet.ServletContext log: Exception while dispatching incoming RPC call com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract java.util.ArrayList com.allurefx.herdspot.client.HerdspotService.getEventsSummary(boolean) throws com.google.gwt.user.client.rpc.SerializationException' threw an unexpected exception: java.lang.UnsupportedOperationException at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java: 378) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java: 581) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java: 188) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java: 224) at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java: 62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:713) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 511) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1166) at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java: 51) 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 com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java: 122) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: 216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java: 765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 418) at com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java: 70) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at com.google.appengine.tools.development.JettyContainerService $ApiProxyHandler.handle(JettyContainerService.java:349) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java: 542) at org.mortbay.jetty.HttpConnection $RequestHandler.content(HttpConnection.java:938) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java: 409) at org.mortbay.thread.QueuedThreadPool $PoolThread.run(QueuedThreadPool.java:582) Caused by: java.lang.UnsupportedOperationException at org.datanucleus.store.appengine.EntityUtils.getPropertyName(EntityUtils.java: 62) at org.datanucleus.store.appengine.DatastoreFieldManager.getPropertyName(DatastoreFieldManager.java: 1073) at org.datanucleus.store.appengine.DatastoreFieldManager.fetchObjectField(DatastoreFieldManager.java: 309) at org.datanucleus.store.appengine.DatastoreFieldManager.fetchStringField(DatastoreFieldManager.java: 202) at org.datanucleus.state.AbstractStateManager.replacingStringField(AbstractStateManager.java: 1180) at com.allurefx.herdspot.server.data.Token.jdoReplaceField(Token.java) at com.allurefx.herdspot.server.data.Token.jdoReplaceFields(Token.java) at org.datanucleus.state.JDOStateManagerImpl.replaceFields(JDOStateManagerImpl.java: 2772) at org.datanucleus.state.JDOStateManagerImpl.replaceFields(JDOStateManagerImpl.java: 2791) at org.datanucleus.store.appengine.DatastorePersistenceHandler.fetchObject(DatastorePersistenceHandler.java: 480) at org.datanucleus.state.JDOStateManagerImpl.validate(JDOStateManagerImpl.java: 4263) at org.datanucleus.ObjectManagerImpl.findObject(ObjectManagerImpl.java:
[appengine-java] Still can't update app
I'm still getting errors updating my app - 500 errors like below. I thought this had to do with the GAE problems, but looks like those are resolved now, more or less. Anyone else seeing these? Unable to update app: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=herdspotversion=2; 500 Internal Server Error Server Error (500) A server error has occurred. See the deployment console for more details Unable to update app: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=herdspotversion=2; 500 Internal Server Error Server Error (500) A server error has occurred. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Still can't update app
Never mind, working OK now. On May 25, 2:52 pm, Sekhar sek...@allurefx.com wrote: I'm still getting errors updating my app - 500 errors like below. I thought this had to do with the GAE problems, but looks like those are resolved now, more or less. Anyone else seeing these? Unable to update app: Error posting to URL:https://appengine.google.com/api/appversion/create?app_id=herdspotve... 500 Internal Server Error Server Error (500) A server error has occurred. See the deployment console for more details Unable to update app: Error posting to URL:https://appengine.google.com/api/appversion/create?app_id=herdspotve... 500 Internal Server Error Server Error (500) A server error has occurred. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Extremely annoying error 203 - please help!!!
Thanks, yes - this error is no longer appearing now. The task executes some JPA operations, and I'm listening for timeouts and continuing the operation in another call if necessary (occasionally, it processes many entities, so can last a while). I'm still getting the below two errors however: (1) Error and exception: org.datanucleus.transaction.Transaction commit: Operation commit failed on resource: org.datanucleus.store.appengine.datastorexaresou...@16b7e0e, error code UNKNOWN and transaction: [DataNucleus Transaction, ID=Xid= com.allurefx.herdspot.server.task.GoogleTaskServlet doPost: javax.persistence.RollbackException: Transaction failed to commit (2) Exception com.google.apphosting.utils.servlet.TransactionCleanupFilter handleAbandonedTxns: Request completed without committing or rolling back transaction with id -3057717142251548962. Transaction will be rolled back. In general, what's the approved way to handle db operations that can exceed the 30 sec time limit? What I'm doing now is to queue a task from inside the servlet and let the task execute in however many iterations are necessary. On May 11, 10:04 pm, App Engine Team appengine.nore...@gmail.com wrote: Hey Sekhar This error code indicates that the request exceeded the 30 second deadline, but we were unable to throw a HardDeadlineExceedError (or your code catches this error and was doing clean up work). Without seeing your code, it's hard to know for sure. If it is datastore code, you might be seeing this as a result of a datastore issue causing increased latency with requests:http://groups.google.com/group/google-appengine-downtime-notify/brows... On May 10, 11:13 pm, Sekhar sek...@allurefx.com wrote: I've been struggling to get past this wretched error when using task queues: A serious 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. If you see this message frequently, you should contact the App Engine team. (Error code 203) Could someone help please? I tried custom queues and default queue; one param and two params. It used to fail intermittently, now it fails regularly. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Extremely annoying error 203 - please help!!!
I've been struggling to get past this wretched error when using task queues: A serious 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. If you see this message frequently, you should contact the App Engine team. (Error code 203) Could someone help please? I tried custom queues and default queue; one param and two params. It used to fail intermittently, now it fails regularly. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Geocoding API quickly throwing OVER_QUERY_LIMIT error
Anyone? I'm still getting this error, and it's kind of critical for me. Hope one of you can help. On Apr 23, 6:04 pm, Sekhar sek...@allurefx.com wrote: The geocoding API is throwing OVER_QUERY_LIMIT error after just one or two queries for me. The problem is intermittent (was failing consistently and then worked OK for some time just now). This is happening only in production, there doesn't seem to be any such problem in my dev server. I guess this is similar to what was discussed inhttp://goo.gl/Zl4M, but looks like that one was fixed. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Geocoding API quickly throwing OVER_QUERY_LIMIT error
The geocoding API is throwing OVER_QUERY_LIMIT error after just one or two queries for me. The problem is intermittent (was failing consistently and then worked OK for some time just now). This is happening only in production, there doesn't seem to be any such problem in my dev server. I guess this is similar to what was discussed in http://goo.gl/Zl4M, but looks like that one was fixed. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: JPA enhancement problem (DataNucleus)
They aren't that complex, and I never really got any compile-time errors (which I think you are referring to) - all the issues are run- time. Anyway, I went ahead and limited the ORM compiles to just the subdirectory that has the entities (using the Eclipse GAE option). Hopefully that'll fix the errors; will report back if it doesn't. On Mar 13, 8:59 am, David Fuelling sappe...@gmail.com wrote: I get this issue pretty often too, although my experience is that you likely have an issue with one of your entities (sometimes your entity can be properly coded, but there could be a fluke with how DataNucleus +GAE interpret a particular feature/annotation, especially with JPA). For example, I had an entity that would fail DataNucleus validation at first, but when I would do a Clean All+Auto Build, the Datanucleus error would go away until some other class (any java class) was re- compiled. I ended up discovering this by iteratively removing JPA features from my Entity one at a time (@OneToOne relationships, etc) until the this class not enhanced errors went away). Eventually I was able to nail down that I was either annotating something incorrectly or DataNucleus/GAE didn't support a particular feature, or in one case an actual bug. Not exactly a clear-cut answer, but that's the path I took. How complex are your entities? david On Mar 11, 7:21 pm, Sekhar sek...@allurefx.com wrote: I'm using the Eclipse Google plugin, and every once in a while after a build I get the dreaded this class is not enhanced! errors for all my entities (even when I don't edit any of them). Any idea why this is? If I touch the files, they get built/enhanced again fine, but this is getting to be a real annoyance. I'd appreciate any pointers you can give! -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: org.datanucleus.store.appengine.MetaDataValidator checkForIllegalChildField
Bump. Could someone from Google/DataNucleus help please? On Jan 9, 7:31 pm, Sekhar sek...@allurefx.com wrote: I'm getting a warning for an embedded child: org.datanucleus.store.appengine.MetaDataValidator checkForIllegalChildField: Unable to validate relation com.allurefx.herdspot.server.data.Person.im I understand we get the checkForIllegalChildField error for many-to- one children that have a Long (rather than Key/String) primary key, but what I have is an embedded field that can't have a primary key. What's the reason for this warning, and what's the resolution? -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] org.datanucleus.store.appengine.MetaDataValidator checkForIllegalChildField
I'm getting a warning for an embedded child: org.datanucleus.store.appengine.MetaDataValidator checkForIllegalChildField: Unable to validate relation com.allurefx.herdspot.server.data.Person.im I understand we get the checkForIllegalChildField error for many-to- one children that have a Long (rather than Key/String) primary key, but what I have is an embedded field that can't have a primary key. What's the reason for this warning, and what's the resolution? -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Upgrade issue with Google SDK 1.2.5
Had the same problem, just remapping the SDK fixed it. This is under WIndow-Preferences-Google-App Engine. On Sep 6, 8:35 am, James H james.hollier...@gmail.com wrote: I used the Eclipse Soft Updates menu on Sep 4th to apply SDK 1.2.5 after noticing Red errors in the local runtime log telling me to do so. Actually, first I noticed my production app was failing to retrieve data so I figured I needed to first upgrade as instructed by the log message and then see if there were still any data issues. I had been running SDK 1.2.2 since July without problems locally or in production. The install of the upgrade ran without errors. Here is the Eclipse install history: Jul 12, 2009 1:24:28 PM file:/C:/homeGoogle/programs/eclipse/ site- install success Jul 12, 2009 1:49:03 PM Date / Time Target Action Status Jul 12, 2009 1:48:12 PM com.google.gdt.eclipse.suite.e33.feature_1.0.1.v200905131156 feature- install success Jul 12, 2009 1:48:26 PM com.google.gdt.eclipse.suite.e33.feature_1.0.1.v200905131156 feature- enable success Jul 12, 2009 1:48:26 PM com.google.gwt.eclipse.sdkbundle.e33.feature_1.6.4.v200904062254 feature-install success Jul 12, 2009 1:49:03 PM com.google.gwt.eclipse.sdkbundle.e33.feature_1.6.4.v200904062254 feature-enable success Jul 12, 2009 1:50:20 PM Date / Time Target Action Status Jul 12, 2009 1:50:06 PM com.google.appengine.eclipse.sdkbundle.e33.feature_1.2.1.v200905131156 feature-install success Jul 12, 2009 1:50:20 PM com.google.appengine.eclipse.sdkbundle.e33.feature_1.2.1.v200905131156 feature-enable success Jul 24, 2009 10:01:27 PM Date / Time Target Action Status Jul 24, 2009 10:01:01 PM com.google.appengine.eclipse.sdkbundle.e33.feature_1.2.2.v200907131018 feature-install success Jul 24, 2009 10:01:27 PM com.google.appengine.eclipse.sdkbundle.e33.feature_1.2.2.v200907131018 feature-enable success Jul 24, 2009 10:01:27 PM com.google.appengine.eclipse.sdkbundle.e33.feature_1.2.1.v200905131156 feature-disable success Sep 4, 2009 6:27:25 AM Date / Time Target Action Status Sep 4, 2009 6:26:51 AM com.google.gdt.eclipse.suite.e33.feature_1.1.0.v200907291650 feature- install success Sep 4, 2009 6:27:12 AM com.google.gdt.eclipse.suite.e33.feature_1.1.0.v200907291650 feature- enable success Sep 4, 2009 6:27:12 AM com.google.gdt.eclipse.suite.e33.feature_1.0.1.v200905131156 feature- disable success Sep 4, 2009 6:27:12 AM com.google.appengine.eclipse.sdkbundle.e33.feature_1.2.5.v200909021033 feature-install success Sep 4, 2009 6:27:25 AM com.google.appengine.eclipse.sdkbundle.e33.feature_1.2.5.v200909021033 feature-enable success Sep 4, 2009 6:27:25 AM com.google.appengine.eclipse.sdkbundle.e33.feature_1.2.2.v200907131018 feature-disable success Sep 5, 2009 11:13:51 AM Date / Time Target Action Status Sep 5, 2009 11:12:38 AM com.google.gwt.eclipse.sdkbundle.e33.feature_1.7.0.v200907131018 feature-install success Sep 5, 2009 11:13:48 AM com.google.gwt.eclipse.sdkbundle.e33.feature_1.7.0.v200907131018 feature-enable success Sep 5, 2009 11:13:48 AM com.google.gwt.eclipse.sdkbundle.e33.feature_1.6.4.v200904062254 feature-disable success At this point my Eclipse behaves as though the Google SDK is NOT installed. For example, the Google Icons are NOT displayed in the Toolbar, etc. From the above install history, it appears the following are enabled and the older version have been disabled: com.google.gwt.eclipse.sdkbundle.e33.feature_1.7.0.v200907131018 com.google.appengine.eclipse.sdkbundle.e33.feature_1.2.5.v200909021033 com.google.gdt.eclipse.suite.e33.feature_1.1.0.v200907291650 How do I get this SDK working again? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
