hibernate-issues September 2012

hibernate-issues@lists.jboss.org

1 participants
633 discussions

Start a nNew thread

[Hibernate-JIRA] (HHH-7467) session.get is returning object which does not exist

by Suneel Nallagonda (JIRA)

12 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] (HHH-7516) session.get is returning object which does not exist

by Suneel Nallagonda (JIRA)

12 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] (HSEARCH-1188) Discuss and prototype capability to delegate both indexing and search to remote Lucene engines

by Sanne Grinovero (JIRA)

12 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7617) Gradle eclipse task missing src paths and test source generation

by Brett Meyer (JIRA)

12 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7615) Binder unable to determine correct columns for non-explicit references to PK of joined tables

by John Verhaeg (JIRA)

12 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] (HHH-7614) @FetchProfile fails for OneToMany and ManyToMany associations

by Daniela Roth (JIRA)

12 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7562) Error locating Hibernate Session Factory in Terracotta configuration with EHCache

by David Harrigan (JIRA)

12 years, 3 months

4
7
0 / 0

[Hibernate-JIRA] (JPA-34) JPA2 Criteria API creates invalid SQL when using groupBy

by Stephan Windmüller (JIRA)

12 years, 3 months

2
11
0 / 0

[Hibernate-JIRA] (HHH-7611) Incorrect GROUP BY query produced using JPA Criteria API with PostgreSQL

by Craig Ringer (JIRA)

12 years, 3 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6433) PostCommitListeners are called during rollback

by Shawn Clowater (JIRA)

PostCommitListeners are called during rollback ---------------------------------------------- Key: HHH-6433 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6433 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.2 Environment: JDK 1.6u25, Win7, Oracle10 Reporter: Shawn Clowater EntityActions that are registered as part of transaction completion are still called when the transaction didn't succeed. As an example, the DeleteEntityAction {code} public void doAfterTransactionCompletion(boolean success, SessionImplementor session) throws HibernateException { if ( getPersister().hasCache() ) { final CacheKey ck = new CacheKey( getId(), getPersister().getIdentifierType(), getPersister().getRootEntityName(), getSession().getEntityMode(), getSession().getFactory() ); getPersister().getCacheAccessStrategy().unlockItem( ck, lock ); } postCommitDelete(); } {code} The success is false in the event of a rollback so it doesn't update the cache but it still calls the postCommitDelete which triggers the postCommitDelete listeners. I would think this should only occur in the event that the transaction was actually committed. To add insult to injury the ActionQueue will also add failed actions to the after transaction completion queue and invalidate the query spaces. {code} public void execute(Executable executable) { try { executable.execute(); } finally { registerCleanupActions( executable ); } } private void registerCleanupActions(Executable executable) { beforeTransactionProcesses.register( executable.getBeforeTransactionCompletionProcess() ); if ( session.getFactory().getSettings().isQueryCacheEnabled() ) { final String[] spaces = (String[]) executable.getPropertySpaces(); afterTransactionProcesses.addSpacesToInvalidate( spaces ); session.getFactory().getUpdateTimestampsCache().preinvalidate( spaces ); } afterTransactionProcesses.register( executable.getAfterTransactionCompletionProcess() ); } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

← Newer
1
...
48
49
50
51
52
53
54
...
64
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2012