Hi Takashi,
Follow the stack overflow link:
http://stackoverflow.com/questions/12674796/org-datanucleus-transaction-transaction-rollback-on-google-app-engine
Just to know what expect from Google´s support. Which are the further steps
to solve this problem? Like I said, this is a huge problem, an
On Sat, Sep 29, 2012 at 12:17 PM, Ricardo wrote:
> I´m changing a property of a child thata has a relation owened
> one-to-many, and in the end saving the parent´s entity.
In one transaction? How big is the change? Are those child entities
necessarily to have the owned one-to-many relationship?
I´m changing a property of a child thata has a relation owened one-to-many,
and in the end saving the parent´s entity.
Yes, I can change the entities (parent and child) in the admin console
without problems.
Em sexta-feira, 28 de setembro de 2012 23h08min34s UTC-3, Takashi Matsuo
(Google) escr
Hi Ricardo,
Thanks for the info.
What kind of change are you trying to make on this entity?
Can you change this entity via the datastore viewer of the admin console?
Does it also fail?
-- Takashi
On Sat, Sep 29, 2012 at 5:32 AM, Ricardo wrote:
> Hi Takashi,
>
> Yes, that´s right. Always this
Hi Takashi,
Yes, that´s right. Always this Rollback critical error. I neither can catch
the error, what gives me a awful message to my user.
Anoter strange behavior that I could experience is that the restore tool
inside the datastore admin console, never ends when this entity is inside
one
Hi Ricardo,
Are you saying a particular entity always throws an error when changing?
Can you tell me your app-id and the key in question?
On Thu, Sep 27, 2012 at 4:42 AM, Ricardo wrote:
> It seems, to me, the rollback operation is not finishing in the 60´s
> second wich each request has to end
It seems, to me, the rollback operation is not finishing in the 60´s second
wich each request has to ends and the roolback operation is canceled. In
this way the object ends in this a state that we cant write on it.
This problems seems to me very serious because the user object end in
this "un
I think it's not related to a particular User as we see really a lot
of HardDeadlineExceededError errors (followed by the error code 104 message
at the end of log) for the last few days, which is very disturbing.
>From what I've seen, it happens when request is routed to a new instance
that fa
