Hello Heikki, Thanks for your response. �Hmmm... �When I run 'show processlist', I get something like the following:
+----+------+------------------------------------+----------+---------+---------+-------+------------------+ | Id | User | Host � � � � � � � � � � � � � � � | db � � � | Command | Time � �| State | Info � � � � � � | +----+------+------------------------------------+----------+---------+---------+-------+------------------+ | �2 | root | 127.0.0.1:1589 � � � � � � � � � � | swpadata | Query � | 0 � � � | NULL �| show processlist | | 82 | root | leroy.con.somedomain12345.com:3448 | swpadata | Sleep � | 1735789 | � � � | NULL � � � � � � | | 83 | root | leroy.con.somedomain12345.com:3450 | swpadata | Sleep � | 1735912 | � � � | NULL � � � � � � | | 84 | root | 127.0.0.1:1050 � � � � � � � � � � | swpadata | Sleep � | 1746236 | � � � | NULL � � � � � � | | 85 | root | 127.0.0.1:1051 � � � � � � � � � � | swpadata | Sleep � | 1746236 | � � � | NULL � � � � � � | | 86 | root | 127.0.0.1:1052 � � � � � � � � � � | swpadata | Sleep � | 59 | � � � | NULL � � � � � � | | 87 | root | 127.0.0.1:1053 � � � � � � � � � � | swpadata | Sleep � | 1746214 | � � � | NULL � � � � � � | | 88 | root | 127.0.0.1:1055 � � � � � � � � � � | swpadata | Sleep � | 44 | � � � | NULL � � � � � � | | 89 | root | 127.0.0.1:1057 � � � � � � � � � � | swpadata | Sleep � | 293 | � � � | NULL � � � � � � | | 90 | root | 127.0.0.1:1058 � � � � � � � � � � | swpadata | Sleep � | 44 | � � � | NULL � � � � � � | +----+------+------------------------------------+----------+---------+---------+-------+------------------+ 10 rows in set (0.00 sec) (Sorry about the formatting...) �What's this showing me? �That all of these transactions are outstanding and not committed? �Since there's nothing other than 'NULL' in the 'Info' column, I'm having a hard time figuring out which transaction is problematic. �I've used the client port addresses to figure out which process the transactions belong to, but, unfortunately, that in itself doesn't provide me any insights. �Could you offer any tips on how to use this information? Also, what would I have to have done to get into that state? �If I have auto-commits off, and then try to perform some command that fails (therefore unexpectedly exiting the relevant section of my code without either a commit or a rollback), would that do it? �And if I then continue issuing other queries or updates over the same connection, would they still work fine, therefore hiding the fact that a transaction's been left dangling? �If so, what's the right thing to do here: issue a rollback? Thank you for your help with this. Best regards, Alex > Alex, >> ---TRANSACTION 0 125987852, ACTIVE 1217449 sec, OS thread id 1712 > you have transactions which have been active 1.2 million seconds, > that is, 15 days! > > You should commit those transactions. > > You can also use SHOW PROCESSLIST to show those open sessions. > > Regards, > > Heikki __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
