org.apache.openjpa.persistence.PersistenceException: Ran out of memory retrieving query results. {prepstmnt 906542123 SELECT t0.id, t0.bean_type, t0.app_name, t0.app_path, t0.conf, t0.group_name, t0.parent_id, t0.run, t0.user_name, t0.auth_token, t0.created_time, t0.end_time, t0.external_id, t0.last_modified_time, t0.log_token, t0.proto_action_conf, t0.sla_xml, t0.start_time, t0.status, t0.wf_instance FROM WF_JOBS t0 WHERE (t0.id = ?) AND t0.bean_type = ?} [code=0, state=53200]

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via oozie-user by Denis Yuen, 1 year ago
Ran out of memory retrieving query results. {prepstmnt 906542123 SELECT t0.id, t0.bean_type, t0.app_name, t0.app_path, t0.conf, t0.group_name, t0.parent_id, t0.run, t0.user_name, t0.auth_token, t0.created_time, t0.end_time, t0.external_id, t0
via oozie-user by Denis Yuen, 1 year ago
Ran out of memory retrieving query results. {prepstmnt 906542123 SELECT t0.id, t0.bean_type, t0.app_name, t0.app_path, t0.conf, t0.group_name, t0.parent_id, t0.run, t0.user_name, t0.auth_token, t0.created_time, t0.end_time, t0.external_id, t0
via openjpa-users by David Beer, 1 year ago
The last packet successfully received from the server was 187,404,662 milliseconds ago. The last packet sent successfully to the server was 187,404,662 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should
via openjpa-users by David Beer, 6 months ago
The last packet successfully received from the server was 187,404,662 milliseconds ago. The last packet sent successfully to the server was 187,404,662 milliseconds ago. is longer than the server configured value of
via openjpa-users by David Beer, 6 months ago
of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
via openjpa-users by David Beer, 6 months ago
of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
org.apache.openjpa.persistence.PersistenceException: Ran out of memory retrieving query results. {prepstmnt 906542123 SELECT t0.id, t0.bean_type, t0.app_name, t0.app_path, t0.conf, t0.group_name, t0.parent_id, t0.run, t0.user_name, t0.auth_token, t0.created_time, t0.end_time, t0.external_id, t0.last_modified_time, t0.log_token, t0.proto_action_conf, t0.sla_xml, t0.start_time, t0.status, t0.wf_instance FROM WF_JOBS t0 WHERE (t0.id = ?) AND t0.bean_type = ?} [code=0, state=53200]
at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4962)
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4922)

Users with the same issue

4 times, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 2 years ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.