Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7968631
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T07:06:25+00:00 2026-06-04T07:06:25+00:00

In the last few hours I’ve started getting exceptions when getting entities by key:

  • 0

In the last few hours I’ve started getting exceptions when getting entities by key:

Caused by: java.lang.NullPointerException
    at com.google.appengine.api.datastore.PropertyContainer.getProperties(PropertyContainer.java:48)
    at com.googlecode.objectify.impl.Transmog.load(Transmog.java:336)
    at com.googlecode.objectify.impl.ConcreteEntityMetadata.toObject(ConcreteEntityMetadata.java:203)
    at com.googlecode.objectify.impl.AsyncObjectifyImpl$1.wrap(AsyncObjectifyImpl.java:82)
    at com.googlecode.objectify.impl.AsyncObjectifyImpl$1.wrap(AsyncObjectifyImpl.java:69)
    at com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
    at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
    at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:90)
    at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:90)
    at com.googlecode.objectify.impl.ResultAdapter.get(ResultAdapter.java:29)
    at com.googlecode.objectify.impl.ObjectifyImpl.get(ObjectifyImpl.java:63)

They are intermittent and are thrown approx 50% of the time.

UPDATE

The second line of code throws the exception:

Objectify ofy = ObjectifyService.begin();
retVal = ofy.get(entityKey);

Adding logging to see the value of entityKey….

UPDATE 2

After adding logging, I can confirm that the Key is non-null and also that when I use the key to get the entity using the datastore viewer it works just fine.

UPDATE 3

I can confirm this is an issue to do with Memcache. After disabling objectify caching, I no longer receive this error. So either this is a bug in objectify (unlikely because I haven’t changed/upgraded our objectify library) or the appengine memcache service has changed somehow.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-04T07:06:26+00:00Added an answer on June 4, 2026 at 7:06 am

    It appears that Google broke serialization/deserialization of the Entity class. They have subsequently rolled back the update that caused the problem and the issue is resolved. Kudos to Alfred, Chris, and the other folks who turned around the problem within a couple hours of hearing about it.

    Unfortunately this was not an issue that could be handled by any normal error trapping mechanisms (ie, a serialization exception). The memcache calls succeeded and returned an Entity object, but subsequent calls to getProperties() on the Entity object failed. Nasty bug.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

For the last few hours I've been trying to set up this http://code.google.com/apis/books/docs/dynamic-links.html on
I spent the last few hours getting my website to validate HTML 4.01 Strict
i spent last few hours trying to find what is wrong in my code(?)
I've spent the last few hours finding out why will_paginate wouldn't work on my
I've been spending the last few hours trying to find the memory leak in
last few hours I try to test with spring jpa 2.0 3.0 Finally I
I have been struggling for the last few hours trying to get this search
I've been trying over the last few hours to implement a jQuery easing effect
I've been pulling my hair out for the last few hours with this problem.
I've spent the last few hours looking at Django Docs and similar questions on

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.