Ralf Schneider wrote: > > Hi, > > I make some first experiments with Hibernate 3.1 and MaxDB 7.5.0.19. > Everything works fine, but after some period of time I get an exception > saying: > > ERROR [03.01.2006 00:13:20] (JDBCExceptionReporter.java:72) - [-708] > Timeout > org.hibernate.exception.JDBCConnectionException: could not execute query > at > org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java :7 > 2) > at > org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper. ja > va:43) > at org.hibernate.loader.Loader.doList(Loader.java:2153) > [...] > Caused by: com.sap.dbtech.jdbc.exceptions.ConnectionException: [-708] > Timeout > at > com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:472) > at > com.sap.dbtech.jdbc.CallableStatementSapDB.sendCommand(CallableStatement Sa > pDB.java:1646) > at > com.sap.dbtech.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:783) > at > com.sap.dbtech.jdbc.CallableStatementSapDB.doParse(CallableStatementSapD B. > java:234) > at > com.sap.dbtech.jdbc.CallableStatementSapDB.constructor(CallableStatement Sa > pDB.java:185) > at > com.sap.dbtech.jdbc.CallableStatementSapDB.<init>(CallableStatementSapDB .j > ava:87) > at > com.sap.dbtech.jdbc.ConnectionSapDB.prepareStatement(ConnectionSapDB.jav a: > 721) > at > org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher. ja > va:442) > at > org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher. ja > va:368) > at > org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher .j > ava:105) > at > org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1561) > at org.hibernate.loader.Loader.doQuery(Loader.java:661) > at > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loade r. > java:224) > at org.hibernate.loader.Loader.doList(Loader.java:2150) > > What is happening here? The last entries in knldiag look like this: > > 2006-01-02 22:12:40 11737 11580 COMMUNIC e84_find: UKT7 T85 conn > 1136236331 'Command wait ' > 2006-01-02 22:12:40 11737 11580 COMMUNIC e84_find: UKT7 T86 conn > 1136236331 'Command wait ' > 2006-01-02 22:12:40 11737 WNG 11832 COMMUNIC rejecting request > 2006-01-02 22:12:40 11737 WNG 11837 COMMUNIC ALL are busy (in all UKTs)
For me it looks as if all tasks in the database kernel are eaten up by some application(s) and the next application wanting to communicate to the database kernel does not get a new task. Please check the parameter MAXUSERTASKS and check your application(s) if they hold a session / connection to the database kernel although they do not work with it and block other applications needing such connections for real work. Elke SAP Labs Berlin > 2006-01-02 22:12:40 11737 11580 COMMUNIC e84_find: UKT5 T20 conn 0 > 'Connect wait ' > 2006-01-02 22:12:40 11737 11580 COMMUNIC e84_find: UKT3 T36 conn 0 > 'Connect wait ' > 2006-01-02 22:12:40 11737 11580 COMMUNIC e84_find: UKT7 T37 conn > 1136235733 'Command wait ' > 2006-01-02 22:12:40 11737 11580 COMMUNIC e84_find: UKT7 T38 conn > 1136235733 'Command wait ' > > Any ideas what's going wrong? > > Thanks in advance, > Ralf. > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
