Our Hibernate 3.1.3 application started acting up. The symptoms were after a call to Query.list(), one of the queried tables was being locked. This is strange, given that the operation is read-only, and that it only happened on one of the many such calls. The problematic query was probably the largest query in the system. We ran the application in three different environments, but it only failed in one. The failed environment was running SQL Server Developer Edition 8.00.194 (RTM). The two successful environments were running SQL Server Developer Edition 8.00.2039 (SP4). Our hypothesis is that this accounts for the difference. Early versions of MSDE had issues closing cursors -- perhaps we've been bitten by that.
... until the collector arrives ...
This "blog" is really just a scratchpad of mine. There is not much of general interest here. Most of the content is scribbled down "live" as I discover things I want to remember. I rarely go back to correct mistakes in older entries. You have been warned :)
Blog Archive
-
▼
2007
(94)
-
▼
Jan 2007
(14)
- BIRT vs Script Extensions vs jTDS vs Eclipse Plug-ins
- Excel User-defined Worksheet Functions
- Building esi.execute
- Eclipse xdoclet Error
- SQL Server 2000 vs. Hibernate 3
- Hibernate Logging
- JDK Logging
- Eclipse Applications and JConsole
- log4j Logging
- Hibernate 3.1.3 Failed Saves
- Eclipse Java Compiler Bug
- Eclipse Java Compiler Non-Null Warnings
- Hibernate vs. Object.equals()
- IE7 vs. Automatic Windows Authentication
-
▼
Jan 2007
(14)