【问题标题】:Google App Engine getJDOExceptionForNucleusException Error When Querying DatabaseGoogle App Engine getJDOExceptionForNucleusException 查询数据库时出错
【发布时间】:2015-07-24 18:00:30
【问题描述】:

我正在开发一个项目,其中 Google App Engine 托管后端数据存储,并且我能够发送 JSON 请求以通过我的网站访问它。

我有多个表(即订单信息、优惠券等),并且刚刚创建了一个新表 Session。这个想法是,我希望数据库存储会话 ID,而不是使用 Memcache 来保存数据。我编写了代码来检查它,但是每当我在数据库中搜索会话 ID 时,它都会返回一个错误:

org.datanucleus.api.jdo.NucleusJDOHelper getJDOExceptionForNucleusException: Exception thrown
Received a request to find an object of kind Session but the provided identifier is the String representation of a Key for kind Token

这是我所指的本次会议的数据库表的图片:

我对此感到困惑的问题是,当我使用字符串作为主键对数据库执行的其他查询工作正常时,为什么这会成为一个问题......有人有什么想法吗?

完整的错误输出:

org.datanucleus.api.jdo.NucleusJDOHelper getJDOExceptionForNucleusException: Exception thrown
Received a request to find an object of kind Session but the provided identifier is the String representation of a Key for kind Token
org.datanucleus.exceptions.NucleusFatalUserException: Received a request to find an object of kind Session but the provided identifier is the String representation of a Key for kind Token
    at com.google.appengine.datanucleus.EntityUtils.stringToInternalKey(EntityUtils.java:423)
    at com.google.appengine.datanucleus.EntityUtils.idToInternalKey(EntityUtils.java:218)
    at com.google.appengine.datanucleus.EntityUtils.idToInternalKey(EntityUtils.java:208)
    at com.google.appengine.datanucleus.DatastoreIdentityKeyTranslator.getKey(DatastoreIdentityKeyTranslator.java:32)
    at org.datanucleus.ObjectManagerImpl.newObjectId(ObjectManagerImpl.java:3443)
    at org.datanucleus.api.jdo.JDOPersistenceManager.newObjectIdInstance(JDOPersistenceManager.java:1618)
    at org.datanucleus.api.jdo.JDOPersistenceManager.getObjectById(JDOPersistenceManager.java:1740)
    at com.package.core.DataSourceMgr.getObjectById(DataSourceMgr.java:118)
    at com.package.service.SessionService.getSession(SessionService.java:39)
    at com.package.misc.TESTQueryDBForSessionID.execute(TESTQueryDBForSessionID.java:25)
    at com.package.batch.CronShell.doGet(CronShell.java:40)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    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.package.core.DataSourceFilter.doFilter(DataSourceFilter.java:35)
    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 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.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:257)
    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.headerComplete(HttpConnection.java:923)
    at com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
    at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:146)
    at com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:482)
    at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:437)
    at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:444)
    at com.google.tracing.CurrentContext.runInContext(CurrentContext.java:230)
    at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:308)
    at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:300)
    at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:441)
    at com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:234)
    at java.lang.Thread.run(Thread.java:745)

【问题讨论】:

    标签: java google-app-engine google-cloud-datastore database nosql


    【解决方案1】:

    显然,问题有两个方面。

    首先,系统在我使用字符串作为主键时遇到了问题(不知道为什么这个是问题而其他人没有问题......)。将其切换为随机生成的 long。

    这解决了第一个问题,但随后出现了第二个问题,当您有一个长作为 GAE 数据存储的主键/ID 时,您无法查询它。您必须使用 Long(盒装版本,大写 L)而不是 long 才能正常工作。之后,能够删除数据存储区中的现有项目并上传新代码。

    tl;dr -- 如果有人再次遇到这种情况,请确保: 1)您正在使用某种类型的 Long 作为 ID/主键 2)您在代码中使用了 Long(不长):

    public class Session extends BaseEntity {
        @PrimaryKey
        @Persistent(valueStrategy = IdGeneratorStrategy.IDENTITY)
        private Long id;
        //...
    }
    

    -拍拍

    【讨论】:

      猜你喜欢
      • 2018-04-02
      • 2013-05-17
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多