[英]javax.persistence.PersistenceException: Transaction failed to flush
I got the JPA exception 我有JPA例外
"javax.persistence.PersistenceException: Transaction failed to flush"
“ javax.persistence.PersistenceException:事务刷新失败”
Then I deleted my local datastore(datastore-indexes-auto.xml and local_db.bin) from my system. 然后,从系统中删除了本地数据存储区(datastore-indexes-auto.xml和local_db.bin)。 Recreated all the data again and after that, the exception was gone.
再次重新创建所有数据,然后异常消失了。 I want to know what did just happened ?
我想知道刚刚发生了什么?
The following is the stacktrace 以下是stacktrace
[RPC Fault faultString="org.springframework.orm.jpa.JpaSystemException : Transaction failed to flush; nested exception is javax.persistence.PersistenceException: Transaction failed to flush" faultCode="Server.Processing" faultDetail="null"]
at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:290]
at mx.rpc::Responder/fault()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\Responder.as:58]
at mx.rpc::AsyncRequest/fault()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:103]
at NetConnectionMessageResponder/statusHandler()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\messaging\channels\NetConnectionChannel.as:581]
at mx.messaging::MessageResponder/status()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\messaging\MessageResponder.as:222]
I believe it is due to this problem with the time it takes for AppEngine to start up, thereby causing timeout errors. 我认为这是由于AppEngine启动所花费的时间问题,从而导致超时错误。
http://googleappengine.blogspot.com/2009/12/request-performance-in-java.html http://googleappengine.blogspot.com/2009/12/request-performance-in-java.html
If you've been following the App Engine Java runtime group, you may have noticed some discussions about performance of the Java runtime.
如果您一直在关注App Engine Java运行时组,则可能已经注意到有关Java运行时性能的一些讨论。 Many of you have complained about hard-to-predict DeadlineExceededExceptions, or unexpectedly slow requests that use a high amount of CPU.
你们中的许多人抱怨难以预测的DeadlineExceededExceptions或使用大量CPU的意外慢请求。 These issues often have the same root cause: App Engine is preparing a new instance of your code to respond an incoming request.
这些问题通常具有相同的根本原因:App Engine正在准备代码的新实例以响应传入的请求。
It was reported by Grails http://jira.grails.org/browse/GPAPPENGINE-67 据Grails报道, http://jira.grails.org/browse/GPAPPENGINE-67
There is an open issue Google has not fixed yet, even after several years. Google尚未解决一个公开问题,即使几年后也没有解决。
https://code.google.com/p/googleappengine/issues/detail?id=7706 https://code.google.com/p/googleappengine/issues/detail?id=7706
As a Java project becomes more complicated and requires loading more classes & jars at startup, instance startup time degrades to the point where instances blow the 60s user-facing request deadline.
随着Java项目变得越来越复杂,并且在启动时需要加载更多的类和jar,实例启动时间会降低到实例超过60年代面向用户的请求期限的程度。
You MIGHT be able to work around this by keeping an idle instance resident in memory so it doesn't have to spin up. 您可能可以通过将一个空闲实例驻留在内存中来解决此问题,因此它不必启动。
https://developers.google.com/appengine/docs/adminconsole/performancesettings#scheduler https://developers.google.com/appengine/docs/adminconsole/performancesettings#scheduler
https://appengine.google.com/settings https://appengine.google.com/settings
I don't know google-app-engine, but I assume you have some limited space in DB there? 我不知道google-app-engine,但是我想您那里的数据库空间有限? Maybe you just run out of space?
也许只是空间用完了?
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.