Hello Michael, > 2005-06-21 10:44:31 11603 11509 COMMUNIC Connection > broken by appl state > 10 T99
This means the client hang up without a proper disconnect ... > "Thread-43" daemon prio=1 tid=0x7a333fb8 nid=0xc74 runnable > [7b724000..7b725218] > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at > com.sap.dbtech.rte.comm.SocketComm.receiveData(SocketComm.java:634) > at > com.sap.dbtech.rte.comm.SocketComm.receive(SocketComm.java:508) > at > com.sap.dbtech.rte.comm.JdbcCommunication.execute(JdbcCommunic > ation.java:44) ... and this means the client is still waiting for the reply from the kernel ... (*if* this corresponds to the session we have seen in the knldiag). Did you change anything in network configuration of the machine, or its general system configuration? Regards Alexander Schröder SAP DB, SAP Labs Berlin > -----Original Message----- > From: Michael Ruf [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 21, 2005 10:59 AM > To: maxdb@lists.mysql.com > Subject: 11509 COMMUNIC Connection broken by appl state 10 > > Hi, > > we have setup a new maxdb database server 7.5.0.26 ( OS is > Suse9.3, Kernel > 2.6.11 ). With this new DB we have some strange errors. Maybe we have > forgotten something. > > 2005-06-21 10:44:31 11603 11509 COMMUNIC Connection > broken by appl state > 10 T99 > 2005-06-21 10:44:31 11603 WNG 11824 COMMUNIC Releasing T99 > connection aborted > 2005-06-21 10:44:31 11603 12929 TASKING Task T99 started > 2005-06-21 10:44:31 11603 11007 COMMUNIC wait for connection T99 > > When this error occurs, we got deadlocks in our application > in the jdbc Driver > > "Thread-43" daemon prio=1 tid=0x7a333fb8 nid=0xc74 runnable > [7b724000..7b725218] > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at > com.sap.dbtech.rte.comm.SocketComm.receiveData(SocketComm.java:634) > at > com.sap.dbtech.rte.comm.SocketComm.receive(SocketComm.java:508) > at > com.sap.dbtech.rte.comm.JdbcCommunication.execute(JdbcCommunic > ation.java:44) > at > com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:453) > - locked <0x488faaa8> (a com.sap.dbtech.jdbc.ConnectionSapDB) > at > com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:375) > at > com.sap.dbtech.jdbc.StatementSapDB.sendCommand(StatementSapDB. > java:734) > at > com.sap.dbtech.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:778) > at > com.sap.dbtech.jdbc.StatementSapDB.execute(StatementSapDB.java:250) > at > com.sap.dbtech.jdbc.StatementSapDB.executeQuery(StatementSapDB > .java:382) > > regards > Michael > > -- > 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]
