From: <leg...@at...> - 2003-11-05 17:12:18
|
The following comment has been added to this issue: Author: John Kristian Created: Wed, 5 Nov 2003 11:05 AM Body: It's not cache configuration, in my case. The test case that exposed this bug evicts cache entries (by calling the SessionFactory.evict methods). Why? It makes database changes that cause triggers (in the database) to change other tables that are cached by Hibernate, and it needs to see the results (not stale cache entries). I have an extensive test suite, but I can't publish it (it's the intellectual property of my employer). Anyway, it's too large and platform-dependent for the Hibernate team's use. I'll think about developing something more suitable, but it seems like a project that would exceed my time budget for Hibernate improvements. Sorry. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-453 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-453 Summary: ClassCastException in ReadWriteCache.afterUpdate Type: Bug Status: Closed Priority: Major Resolution: FIXED Project: Hibernate2 Components: core Fix Fors: 2.1 rc1 Versions: 2.1 rc1 Assignee: Reporter: John Kristian Created: Tue, 4 Nov 2003 4:37 PM Updated: Tue, 4 Nov 2003 5:57 PM Environment: Windows XP, WebLogic 8.1 SP1, Microsoft SQL Server Description: Hibernate 2.1 beta 6 propagates an AssertionFailure and logs error.log (attached). This did not occur with 2.1 beta 5. notlock.patch (attached) solves this problem for me. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |