November 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-578) JTA transaction commit: Access a Sealed WorkQueue which has not been sealed

by Fabián Guerra (JIRA)

JTA transaction commit: Access a Sealed WorkQueue which has not been sealed --------------------------------------------------------------------------- Key: HSEARCH-578 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-578 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.1 Environment: JDK 1.8.0_18 + Glassfish 2.1.1 + Spring 3.0.3 + Hibernate 3.5.3 + Hibernate Search 3.2.1 + MySQL 5.1.48 + Windows XP SP3 Reporter: Fabián Guerra Priority: Blocker Attachments: application-context.xml, hibernate.log, search-context.xml I'm facing a problem using hibernate search as HSEARCH-540 bug, after an entity has been persited hibernate tries to index it but I got: org.hibernate.annotations.common.AssertionFailure: Access a Sealed WorkQueue which has not been sealed I'm not using annotations to handle POJO's and transactions, I use Spring's HibernateTemplate to persist objects and Aspects to transaction management. (Config files attached) example: @Override public void add(Item item) { getHibernateTemplate().save(item); } -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-159) Sort + Pagination returns wrong results.

by Jason Eacott (JIRA)

Sort + Pagination returns wrong results. ---------------------------------------- Key: HSEARCH-159 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-159 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.0.1.GA Environment: hib 3.2.5ga Reporter: Jason Eacott Perhaps I am doing something wrong? Using the code below if I call getSearchResults("test",0,10); //returns incorrect data I get a different item at the head of the list than if I call getSearchResults("test",0,100);// (this one has correct data, total results for this search is 196 in my ndx & db) if I dont try to paginate the results then the sort items are in order and are correct. and if I paginate with just 1 result getSearchResults("test",0,1); and change the sort order I get the same result for each attempt: ie: Sort datesort=new Sort( new SortField( "date_time", SortField.STRING, true ) ); and Sort datesort=new Sort( new SortField( "date_time", SortField.STRING, false ) ); return the same entry - which is NOT the correct result either. This behavious seems to indicate that the data is being sorted after the limit is set and whats worse, if there are 50,000,000 results, even though I only want 10 and hibernate has already correctly hydrated those 10 (albeit the wrong 10) hibernatesearch then loops over all 50,000,000 hits and creates a new (empty) hibernate proxy object for each & discard all but 10! ... @Field(name="date_time", index=Index.UN_TOKENIZED, store=Store.NO) @DateBridge(resolution=Resolution.MINUTE) private Date publishDate; ... public List getSearchResults(Query query,int firstResult,int maxResults) { List result=null; Session sess=null; Transaction tx = null; try { sess=getSessionFactory().openSession(); FullTextSession fullTextSession = Search.createFullTextSession(sess); tx = fullTextSession.beginTransaction(); tx.begin(); org.hibernate.search.FullTextQuery hibQuery= fullTextSession.createFullTextQuery( query, FeedItem.class ); Sort datesort=new Sort( new SortField( "date_time", SortField.STRING, true ) ); hibQuery.setSort(datesort); Criteria dbCr=fullTextSession.createCriteria(FeedItem.class); hibQuery.setCriteriaQuery(dbCr); dbCr.setFirstResult(firstResult); dbCr.setMaxResults(maxResults); } long resultSize=hibQuery.getResultSize(); if (resultSize>0){ result = hibQuery.list() } tx.commit(); } finally { releaseSession(sess); tx=null; } log.debug("<getSearchResults"); return result; } -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3429) SQLQuery, advice user to always use addScalar if CHAR column are involved.

by Anthony Patricio (JIRA)

SQLQuery, advice user to always use addScalar if CHAR column are involved. -------------------------------------------------------------------------- Key: HHH-3429 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3429 Project: Hibernate3 Issue Type: Improvement Components: documentation Reporter: Anthony Patricio Priority: Minor see HHH-2220 If CHAR(2+) is involved in a SQLQuery and if addScalar isn't used, then the returned value is truncated which is very bad. There is no easy fix for this so a little advice in the documentation would be helpful. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2220) session.createSQLQuery(sql) translates database type CHAR(n) to Java type char instead of String

by Regis Pires Magalhaes (JIRA)

session.createSQLQuery(sql) translates database type CHAR(n) to Java type char instead of String ------------------------------------------------------------------------------------------------ Key: HHH-2220 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2220 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.2.0.ga Reporter: Regis Pires Magalhaes createSQLQuery() method translates database type CHAR(n) to Java type char instead of String when using setResultTransformer(Criteria.ALIAS_TO_ENTITY_MAP). That happens when I do not use addScalar(). And that is the only problem that I have found when not filling return types in advance. A workaround I have made is to concatenate the projected field with an empty string (''). See example below: ... query.setResultTransformer(Criteria.ALIAS_TO_ENTITY_MAP); String sqlQuery = "select s.name state from state s where s.name='PI' "; query = session.createSQLQuery(sqlQuery); ... result: [{STATE=P}] name field is CHAR(2) in database definition (PostgreSQL, HSQLDB and Oracle were tested). Note that it works when I concatenate the field used in projection with an empty string: ... String sqlQuery = "select s.name || '' state from state s where s.name='PI' "; ... result: [{STATE=PI}] -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

8
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2429) SQL Character Types Incorrectly mapped to Java objects

by Tyler Van Gorder (JIRA)

SQL Character Types Incorrectly mapped to Java objects ------------------------------------------------------ Key: HHH-2429 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2429 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Hibernate 3.2.1, Oracle10g Reporter: Tyler Van Gorder We have a work flow that allows the user to enter an arbitrary SQL statement to be executed by our application. We pass those queries through session.createSQLQuery(). We ran into a problem with String literals, which are reported by Oracle (ResultSetMetaData) to be CHAR. Reading the JDBC API, CHAR is a fixed length string. Hibernate is incorrectly mapping this to a Character field. We ended up overriding the Oracle dialect with our own as follows: In our constructor, for a dialect that extends Oracle9iDialect: super() registerColumnType(Types.CHAR, "char($l)" ); registerHibernateType( Types.CHAR, Hibernate.STRING.getName() ); The HibernateType is the crucial one and we are overriding the behavior in the base "Dialect" class, so this appears that it would be a problem for all database variants that don't explicitly change this. Thanks. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
3
0 / 0

[Hibernate-JIRA] Created: (HCANN-10) JPA OneToOne(optional=true) not supported, supported alternative NotFound() is hibernate-proprietary!

by Bruno Melloni (JIRA)

JPA OneToOne(optional=true) not supported, supported alternative NotFound() is hibernate-proprietary! ----------------------------------------------------------------------------------------------------- Key: HCANN-10 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-10 Project: Hibernate Commons Annotations Issue Type: Bug Environment: Hibernate 3.3.1, annotations 3.4.0, MsSQL DB. Reporter: Bruno Melloni Rejected issue ANN-725 covers this partially. I might have misunderstood, but it seems the reason for rejecting is that @NotFound provides the same capability. All information I could find for JPA and other ORM tools indicates that this capability is supplied by @OneToOne(optional=true). Hibernate seems to be the lone ORM tool that requires the use of a proprietary annotation: @NotFound. @NotFound works, but the problem is that it makes the application no longer be pure-JPA. Not supporting pure-JPA outer joins would seem to be a major bug. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
16
0 / 0

[Hibernate-JIRA] Created: (HHH-4854) Make constraint violation name extraction language neutral

by Jonas Olsson (JIRA)

Make constraint violation name extraction language neutral ---------------------------------------------------------- Key: HHH-4854 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4854 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.2.6 Environment: Oracle 8 or later Reporter: Jonas Olsson The ViolatedConstraintNameExtracter of Oracle8iDialect uses the following pattern for extracting the contraint violated: return extractUsingTemplate( "constraint (", ") violated", sqle.getMessage() ); and is highly error message language dependent. Changing to: return extractUsingTemplate( "(", ")", sqle.getMessage() ); would eliminate this while still getting the constraint name. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3239) MarkerObject should be serializable when using with swf

by Goran Blankendal (JIRA)

MarkerObject should be serializable when using with swf ------------------------------------------------------- Key: HHH-3239 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3239 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6 and Spring Webflow 2.0 Reporter: Goran Blankendal You get a java.io.NotSerializableException: org.hibernate.util.MarkerObject when using hibernate in a persistence context in SWF 2 See http://forum.springframework.org/showthread.php?t=51738 and http://forum.hibernate.org/viewtopic.php?t=985226 The MarkerObject should be serializable. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2774) Call ResultTransformer.transformList() even if the list argument is an empty list

by Christian Bauer (JIRA)

Call ResultTransformer.transformList() even if the list argument is an empty list --------------------------------------------------------------------------------- Key: HHH-2774 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2774 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Christian Bauer Priority: Trivial I have a case where a ResultTransformer is doing all the work in transformTuple() and always returns null from that method. The transformed target state is held internally in the ResultTransformer instance (I basically turn many tuples into one). Now I can't get this state out of the ResultTransformer because transformList() is not called after transformTuple(). It would be better if transformList() is called even if the list of tuples returned by transformTuple() is empty. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4838) 2L-Querycache ImmutableNaturalKeyLookup not properly recognized as hasImmutableNaturalId() is called on wrong EntityMetamodel

by Guenther Demetz (JIRA)

2L-Querycache ImmutableNaturalKeyLookup not properly recognized as hasImmutableNaturalId() is called on wrong EntityMetamodel ----------------------------------------------------------------------------------------------------------------------------- Key: HHH-4838 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4838 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-Beta-3 Environment: 3.5.0-Beta3, HSQLDB, EHCache as 2L cache implementation Reporter: Guenther Demetz Attachments: TestImmutableNaturalId.jar If a entityclass with immutable naturalId has non-lazy properties (for instance a OneToOne association), then more entityPersisters are involved in the query as it becomes a join-query eager loading the associated entity. The method Loader#getResultFromQueryCache presumes that the first entityPersister in the array is the main entity class. boolean isImmutableNaturalKeyLookup = queryParameters.isNaturalKeyLookup() && getEntityPersisters()[0].getEntityMetamodel().hasImmutableNaturalId(); Debugging attached testcase you can see indeed that getEntityPersisters()[0] returns SingleTableEntityPersister(hello.D) which is the persister of the associated entity, not the main one! Consequently the query is not considered as isImmutableNaturalKeyLookup, despite fullfilling all conditions. Here my output (with enabled p6spy): 11:53:15,651 INFO Version:37 - Hibernate Annotations 3.5.0.Beta1 11:53:15,690 INFO Environment:563 - Hibernate 3.5.0-Beta-3 11:53:15,694 INFO Environment:596 - hibernate.properties not found 11:53:15,700 INFO Environment:774 - Bytecode provider name : javassist 11:53:15,706 INFO Environment:655 - using JDK 1.4 java.sql.Timestamp handling 11:53:15,863 INFO Version:38 - Hibernate EntityManager 3.5.0.Beta1 11:53:16,356 INFO AnnotationBinder:446 - Binding entity from annotated class: hello.A 11:53:16,424 INFO EntityBinder:471 - Bind entity hello.A on table A 11:53:16,526 INFO AnnotationBinder:446 - Binding entity from annotated class: hello.D 11:53:16,527 INFO EntityBinder:471 - Bind entity hello.D on table D 11:53:16,686 WARN Ejb3Configuration:943 - hibernate.connection.autocommit = false break the EJB3 specification 11:53:16,702 INFO HibernateSearchEventListenerRegister:75 - Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled. 11:53:16,718 INFO DriverManagerConnectionProvider:64 - Using Hibernate built-in connection pool (not for production use!) 11:53:16,719 INFO DriverManagerConnectionProvider:65 - Hibernate connection pool size: 20 11:53:16,720 INFO DriverManagerConnectionProvider:68 - autocommit mode: false 11:53:16,921 INFO DriverManagerConnectionProvider:103 - using driver: com.p6spy.engine.spy.P6SpyDriver at URL: jdbc:hsqldb:hsql://localhost 11:53:16,922 INFO DriverManagerConnectionProvider:109 - connection properties: {user=sa, password=****, autocommit=false, release_mode=after_transaction} 11:53:17,002 INFO SettingsFactory:117 - RDBMS: HSQL Database Engine, version: 1.8.0 11:53:17,004 INFO SettingsFactory:118 - JDBC driver: HSQL Database Engine Driver, version: 1.8.0 11:53:17,068 INFO Dialect:223 - Using dialect: org.hibernate.dialect.HSQLDialect 11:53:17,082 INFO JdbcSupportLoader:79 - Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4 11:53:17,085 INFO TransactionFactoryFactory:62 - Transaction strategy: org.hibernate.transaction.JDBCTransactionFactory 11:53:17,089 INFO TransactionManagerLookupFactory:80 - No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended) 11:53:17,090 INFO SettingsFactory:169 - Automatic flush during beforeCompletion(): disabled 11:53:17,091 INFO SettingsFactory:173 - Automatic session close at end of transaction: disabled 11:53:17,097 INFO SettingsFactory:188 - Scrollable result sets: enabled 11:53:17,098 INFO SettingsFactory:196 - JDBC3 getGeneratedKeys(): disabled 11:53:17,099 INFO SettingsFactory:204 - Connection release mode: after_transaction 11:53:17,101 INFO SettingsFactory:231 - Default batch fetch size: 1 11:53:17,103 INFO SettingsFactory:235 - Generate SQL with comments: disabled 11:53:17,104 INFO SettingsFactory:239 - Order SQL updates by primary key: disabled 11:53:17,105 INFO SettingsFactory:243 - Order SQL inserts for batching: disabled 11:53:17,107 INFO SettingsFactory:410 - Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory 11:53:17,114 INFO SettingsFactory:251 - Query language substitutions: {} 11:53:17,115 INFO SettingsFactory:256 - JPA-QL strict compliance: enabled 11:53:17,121 INFO SettingsFactory:261 - Second-level cache: enabled 11:53:17,130 INFO SettingsFactory:265 - Query cache: enabled 11:53:17,143 INFO SettingsFactory:395 - Cache region factory : org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge 11:53:17,144 INFO RegionFactoryCacheProviderBridge:61 - Cache provider: net.sf.ehcache.hibernate.SingletonEhCacheProvider 11:53:17,150 INFO SettingsFactory:275 - Optimize cache for minimal puts: disabled 11:53:17,151 INFO SettingsFactory:284 - Structured second-level cache entries: disabled 11:53:17,151 INFO SettingsFactory:374 - Query cache factory: org.hibernate.cache.StandardQueryCacheFactory 11:53:17,165 INFO SettingsFactory:313 - Statistics: disabled 11:53:17,166 INFO SettingsFactory:317 - Deleted entity synthetic identifier rollback: disabled 11:53:17,166 INFO SettingsFactory:332 - Default entity-mode: pojo 11:53:17,167 INFO SettingsFactory:336 - Named query checking : enabled 11:53:17,167 INFO SettingsFactory:340 - Check Nullability in Core (should be disabled when Bean Validation is on): disabled 11:53:17,240 INFO SessionFactoryImpl:197 - building session factory 11:53:17,260 WARN ConfigurationFactory:131 - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/home/pb00067/Desktop/ehcache-1.7.1/lib/ehcache-core-1.7.1.jar!/ehcache-failsafe.xml 11:53:17,361 WARN SingletonEhCacheProvider:92 - Could not find a specific ehcache configuration for cache named [hello.A]; using defaults. 11:53:17,566 WARN SingletonEhCacheProvider:92 - Could not find a specific ehcache configuration for cache named [hello.D]; using defaults. 11:53:17,661 INFO SchemaExport:226 - Running hbm2ddl schema export 11:53:17,663 INFO SchemaExport:251 - exporting generated schema to database p6spy - 1264416797664|0|0|commit|| p6spy - 1264416797670|1|0|statement alter table A drop constraint FK41F7BDC12E p6spy - 1264416797672|0|0|statement drop table A if exists p6spy - 1264416797673|0|0|statement drop table D if exists p6spy - 1264416797674|1|0|statement drop table hibernate_sequences if exists p6spy - 1264416797675|1|0|statement create table A (oid bigint not null, name varchar(255), version integer not null, assSingleD_oid bigint, primary key (oid), unique (name)) p6spy - 1264416797676|0|0|statement create table D (oid bigint not null, version integer not null, primary key (oid)) p6spy - 1264416797678|1|0|statement alter table A add constraint FK41F7BDC12E foreign key (assSingleD_oid) references D p6spy - 1264416797679|1|0|statement create table hibernate_sequences ( sequence_name varchar(255), sequence_next_hi_value integer ) 11:53:17,679 INFO SchemaExport:268 - schema export complete 11:53:17,684 INFO UpdateTimestampsCache:57 - starting update timestamps cache at region: org.hibernate.cache.UpdateTimestampsCache 11:53:17,686 WARN SingletonEhCacheProvider:92 - Could not find a specific ehcache configuration for cache named [org.hibernate.cache.UpdateTimestampsCache]; using defaults. 11:53:17,689 INFO StandardQueryCache:75 - starting query cache at region: org.hibernate.cache.StandardQueryCache 11:53:17,690 WARN SingletonEhCacheProvider:92 - Could not find a specific ehcache configuration for cache named [org.hibernate.cache.StandardQueryCache]; using defaults. 11:53:17,841 DEBUG ConnectionManager:444 - opening JDBC connection p6spy - 1264416797874|6|1|statement select sequence_next_hi_value from hibernate_sequences where sequence_name = 'A' p6spy - 1264416797876|0|1|statement insert into hibernate_sequences (sequence_name, sequence_next_hi_value) values ('A', 0) p6spy - 1264416797878|0|1|statement update hibernate_sequences set sequence_next_hi_value = 1 where sequence_next_hi_value = 0 and sequence_name = 'A' p6spy - 1264416797879|0|1|commit|| p6spy - 1264416797915|0|0|statement insert into A (assSingleD_oid, name, version, oid) values ('', 'name1', 0, 1) 11:53:17,919 DEBUG UpdateTimestampsCache:66 - Pre-invalidating space [A] p6spy - 1264416797931|0|0|commit|| 11:53:17,934 DEBUG UpdateTimestampsCache:81 - Invalidating space [A], timestamp: 5179051204337665 11:53:17,974 DEBUG StandardQueryCache:127 - checking cached query results in region: org.hibernate.cache.StandardQueryCache 11:53:17,975 DEBUG StandardQueryCache:132 - query results were not found in cache p6spy - 1264416797978|0|0|statement select this_.oid as oid0_1_, this_.assSingleD_oid as assSingleD4_0_1_, this_.name as name0_1_, this_.version as version0_1_, d2_.oid as oid1_0_, d2_.version as version1_0_ from A this_ left outer join D d2_ on this_.assSingleD_oid=d2_.oid where ( this_.name='name1' ) p6spy - 1264416797981|-1||resultset|oid=1, oid=null 11:53:17,985 DEBUG StandardQueryCache:94 - caching query results in region: org.hibernate.cache.StandardQueryCache; timestamp=5179051204546560 11:53:17,992 DEBUG StandardQueryCache:127 - checking cached query results in region: org.hibernate.cache.StandardQueryCache 11:53:17,993 DEBUG StandardQueryCache:185 - Checking query spaces for up-to-dateness: [A] 11:53:17,994 DEBUG UpdateTimestampsCache:102 - [A] last update timestamp: 5179051204337665, result set timestamp: 5179051204546560 11:53:17,994 DEBUG StandardQueryCache:142 - returning cached query results 11:53:17,997 INFO SessionFactoryImpl:908 - closing -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
29
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2010