JPA Timeout Problem: code=700, state="HYT01", message="Timeout"

[Former Member]

Dear Developers

We have a serious problem by using JPA on SAP NetWeaver AS.

On our development system the codes works fine but in the customer system the SAP AS generates "randomly" when accesing our DB tables following exception:

com.sap.sql.jdbc.direct.DirectPreparedStatement: FATAL SQL error occurred on connection XYZ: code=700, state="HYT01", message="Timeout";

Environment:

NetWeaver 7.2 SP6

MaxDB

The Problem is very hard to analyze as it only appears randomly and at different places, but it makes our software unusable. Any help is welcome.

Especially:

- what does code 700 mean?

- what does state "HYTO1" mean?

Remark:

We saw the problem already once. That time we found out that a missing "allocationSize" attribute in the "@SequenceGenerator" annotation created the problem. But that problem is now already solved.

Thanks

Rolf

Edited by: Rolf Grüninger on Dec 24, 2011 10:24 AM

[rolf_paulsen · Accepted solution]

Hi Rolf,

error 700 = "Session inactivity timeout (work rolled back)", see

[http://hypertext.at/knowhow/maxdb-htmldoc-75/87/0c7fe872ff11d2a9aa00a0c9430730/frameset.htm]

The session timeout is a parameter of the db server/listener.

You can avoid session timeouts on the java side by setting the "Connection Lifetime" of the jdbc data source to a value shorter than the timeout of the database. Try e.g. 300 sec.

Regards

Rolf

[Former Member · Accepted solution]

Thank you very much.

The problem is solved.

Strange is that this problem did not appear before in our system. Maybe the default behavior of SAP AS in handling open JDBC connections has changed in 7.2 SP6.