September 2007 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-2131) SYBASE +select for update is showing deadlock because lock is not working properly

by George Thomas (JIRA)

SYBASE +select for update is showing deadlock because lock is not working properly ---------------------------------------------------------------------------------- Key: HHH-2131 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2131 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: sybaseASE 12.5.03 in solaris +hibernate3.1.3 Reporter: George Thomas I am connecting to Sybase database from hibernate.I tried setting locks using while selecting rows 1.session.load(class,id,LOCKMODE.UPGRADE) 2.session.lock(obj,LOCKMODE.UPGRADE) I am attaching a sample code while updating a field in table fund after selecting it. { Fund fund = null; ClientCredential credential = new ClientCredential("testDatabase", fund); org.hibernate.Session session = SessionFactoryManager.getSessionFactory(credential).getCurrentSession(); Transaction transaction = session.beginTransaction(); log.info("Run by " + Thread.currentThread().getName()); fund = (Fund) session.get(Fund.class, new Short((short)12), LockMode.UPGRADE); fund.setLegalEntityOrgId(fund.getLegalEntityOrgId()+1); transaction.commit(); } my requirement was that i wanted to do a select for update.I should acquire lock on certain rows and do a matching and if concurrent request comes ,it should wait till transaction is over that is lock is released. When I went through the hibernate code,the hibernate is making static queries in the beginning while loading session factory.Since we are appending the holdlock during execution,the sybase dialect is not appending. As a work around I tested with native sql with holdlock but when I test concurrent request using threads its bombing.Its throwing LockAcquisitionException.( Your server command (family id #0, process id #3777) encountered a deadlock situation.).can anyone give a solution to this problem??? org.hibernate.exception.LockAcquisitionException: could not update: [com.citco.aexeo.common.dataaccess.domain.Fund#12] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:84) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2223) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2118) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2375) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:91) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:233) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:297) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:985) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:333) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:107) at com.satyam.Testing.doTransaction(Testing.java:103) at com.satyam.MyRunnable.run(MyRunnable.java:13) at java.lang.Thread.run(Thread.java:568) Caused by: com.sybase.jdbc2.jdbc.SybSQLException: Your server command (family id #0, process id #3777) encountered a deadlock situation. Please re-run your command. at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:2636) at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:1996) at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:204) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:187) at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1642) at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate(SybStatement.java:1625) at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java:91) at org.hibernate.jdbc.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:23) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2205) ... 14 more -- 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

14 years, 6 months

6
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2691) Insert Into Select command outputs incorrect exception

by John Aylward (JIRA)

Insert Into Select command outputs incorrect exception ------------------------------------------------------ Key: HHH-2691 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2691 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4.sp1 with Annotations 3.3.0 And Validator 3.0.0 MySQL 5.0.42 Reporter: John Aylward receive following exception: org.hibernate.QueryException: number of select types did not match those for insert [INSERT INTO ProviderInvoiceLineItem (amount,billingAccount,circuit,description,invoice,type) SELECT pili.amount,pili.billingAccount,pili.circuit,pili.description,:newInvoice,pili.type) FROM com.cicat.bedrock.billing.model.ProviderInvoiceLineItem pili WHERE pili.invoice = :oldInvoice] exception should be that token ')' is not excepected near "pili.type" Should not have gotten as far as it did, should have blown up on parsing the HQL -- 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

14 years, 6 months

5
16
0 / 0

[Hibernate-JIRA] Created: (HHH-2374) setFetchMode() ignore incorect path

by Baptiste MATHUS (JIRA)

setFetchMode() ignore incorect path ----------------------------------- Key: HHH-2374 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2374 Project: Hibernate3 Type: Bug Versions: 3.2.0.ga Environment: All DB I guess Reporter: Baptiste MATHUS This bug report is in fact a copy of the one that was already present in H2 : http://opensource.atlassian.com/projects/hibernate/browse/HB-763 . It does not seem to have changed in H3. When calling setFetchMode("path", FetchMode.JOIN) on a criteria, even if the path is not correct, Hibernate does not complain. Its behaviour seems to be to simply ignore this bad path. I guess this should throw an exception. In fact, the bad thing of ignoring bad path is that if the developer was wrong specifying the path (typo, for example), then the join simply won't happen :-/. I wrote a very simple testcase : public void testFindClients() { Session session = HibernateUtil.currentSession(); session.beginTransaction(); Client c = (Client)session.createCriteria(Client.class).setFetchMode("foo", FetchMode.JOIN) .setFetchMode("foo.bar", FetchMode.JOIN).uniqueResult(); session.getTransaction().commit(); } My Client class has some relationships with other classes, but obviously none named "foo". The code above just issue the following select : select this_.ID as ID0_0_, this_.nom as nom0_0_, this_.prenom as prenom0_0_, this_.age as age0_0_ from Client this_ Thanks again for your great work, guys! -- 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

14 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2344) Persistent collection queued operation ignored with lazy inverse one-to-many collection.

by Sebastien Robert (JIRA)

Persistent collection queued operation ignored with lazy inverse one-to-many collection. ---------------------------------------------------------------------------------------- Key: HHH-2344 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2344 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Hibernate 3.2.1 Reporter: Sebastien Robert I load an Object that contains a lazy inverse collection (one-to-many). Hibernate wrap my collection with a PersistentMap There is objects in the collection in the database but in my case the PersistentMap is not yet initialized. I perform a remove operation on the persistentMap with a known key of one of the objects. The map is not initialized (and the relation is an inverse one-to-many) so the map queue the removeOperation. I perform a get operation with the same key and the value is still returned. If we look closer at what happened in the PersistentMap, it's look like this. //***** public Object remove(Object key) { if ( isPutQueueEnabled() ) { // This returned true, the // map is not yet // initialized Object old = readElementByIndex( key ); // This method triggered // an initialization of the // map. // Queued operation are // processed in the after // init method queueOperation( new Remove( key, old ) ); // The remove operation // is queued. return old; } .... //******* When i perform the get operation on the map the map is now initialized. The get is processed by the underlying map and the value is returned. The queued operation is completely ignored. Currently i fixed my code by performing a containsKey before the remove . The containsKey initialize the map and then the remove do not queue the operation. But by looking at all the PersistentCollection it seem that i may have the same problem using put and remove with other persistentCollection. -- 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

14 years, 6 months

7
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2068) TransientObjectException : object references an unsaved transient instance ...

by Ales PROCHAZKA (JIRA)

TransientObjectException : object references an unsaved transient instance ... ------------------------------------------------------------------------------ Key: HHH-2068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2068 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Environment: Windows, Hibernate 3.2.0.cr4, Oracle 9.2.0.1 Reporter: Ales PROCHAZKA Attachments: XTest.zip I found this problem: If I create new object 'o1', which associate another persistent object 'o2' and by calling saveOrUpdate Hibernate throws PropertyValueException, then when I corresct this property and try call saveOrUpdate in another session (in which 'o2' was not saved or loaded) Hibernate throws TransientObjectException. Please see attached code :-) This is a log : Hibernate: select hibernate_sequence.nextval from dual Hibernate: insert into T_TEST (A_POKUS, A_POKUS_LONG, CID, PK) values (?, ?, 3, ?) Hibernate: insert into T_TEST3 (PK) values (?) Hibernate: select hibernate_sequence.nextval from dual Hibernate: select hibernate_sequence.nextval from dual org.hibernate.PropertyValueException: not-null property references a null or transient value: persistent.Test5.pokus at org.hibernate.engine.Nullability.checkNullability(Nullability.java:72) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:284) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:180) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:121) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:186) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:175) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:98) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:509) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:501) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:497) at test.MainTest.test(MainTest.java:71) at test.MainTest.main(MainTest.java:42) org.hibernate.TransientObjectException: persistent.Test3 at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:216) at org.hibernate.type.EntityType.getIdentifier(EntityType.java:108) at org.hibernate.type.ManyToOneType.isDirty(ManyToOneType.java:221) at org.hibernate.type.TypeFactory.findDirty(TypeFactory.java:476) at org.hibernate.persister.entity.AbstractEntityPersister.findDirty(AbstractEntityPersister.java:2900) at org.hibernate.event.def.DefaultFlushEntityEventListener.dirtyCheck(DefaultFlushEntityEventListener.java:474) at org.hibernate.event.def.DefaultFlushEntityEventListener.isUpdateNecessary(DefaultFlushEntityEventListener.java:197) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:120) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:195) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:993) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:340) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at test.MainTest.test(MainTest.java:87) at test.MainTest.main(MainTest.java:42) Thanx -- 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

14 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2708) attribute order-by don't devlared on hibernate-mapping-3.0.dtd

by Sunteya (JIRA)

attribute order-by don't devlared on hibernate-mapping-3.0.dtd -------------------------------------------------------------- Key: HHH-2708 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2708 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Reporter: Sunteya HHH-1414 bug already fixed order-by attribute on the <many-to-many/> element but the dtd file don't allow use order-by attribute. -- 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

14 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2431) QueryPlanCache grows without bound. Eventually gets OutOfMemoryException

by Eric Goff (JIRA)

QueryPlanCache grows without bound. Eventually gets OutOfMemoryException -------------------------------------------------------------------------- Key: HHH-2431 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2431 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: all versions, all platforms Reporter: Eric Goff Every time you execute a query, and that query does not match any existing queries in the QueryPlanCache, that query is *always* added to the Query Plan Cache, along with a lot of various antlr stuff. There seems to be no way to control it. Minimally, there should be some sort of heap of query plans where the least used query plan is ejected when the cache reaches it max size. The cache size should, of course, be user configurable. -- 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

14 years, 7 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2510) override equals()/hashCode() in AliasToBeanResultTransformer

by Maxim Gordienko (JIRA)

override equals()/hashCode() in AliasToBeanResultTransformer ------------------------------------------------------------ Key: HHH-2510 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2510 Project: Hibernate3 Type: Improvement Versions: 3.2.2 Reporter: Maxim Gordienko AliasToBeanResultTransformer whould override equals()/hashCode() to allow convenient second level query caching. Now the only way is to maintain single transformer instance per bean class to allow query cache hit. -- 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

14 years, 7 months

3
9
0 / 0

[Hibernate-JIRA] Created: (ANN-604) There is no annotation to specify default value for a column

by Nicolae Bucalaete (JIRA)

There is no annotation to specify default value for a column ------------------------------------------------------------ Key: ANN-604 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-604 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Nicolae Bucalaete Priority: Critical In hibernate annotation you can't specify default value for a column. If you use xml files for mapping then you have this feature. I consider that this is a major problem with annotation. -- 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

14 years, 7 months

15
17
0 / 0

[Hibernate-JIRA] Created: (HHH-2350) 2nd level cache broken for inverse bidirectional one-to-many relation

by Burkhard Graves (JIRA)

2nd level cache broken for inverse bidirectional one-to-many relation --------------------------------------------------------------------- Key: HHH-2350 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2350 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Database: MySQL, HSQL, ... (seems not to be important) Reporter: Burkhard Graves Attachments: testcase.tgz When using "inverse" one-to-many relations as described in "2.4.6.2.3. Bidirectional association with indexed collections" (http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.ht...) hibernate is wrong when activating 2nd level cache. See the attached example (unzip in /usr/local/hibernate-annotations-3.2.1.GA, testname=org.hibernate.test.annotations.invonetomany.InverseOneToManyTest). More details can be found here: http://forum.hibernate.org/viewtopic.php?t=969456 (and also in InverseOneToManyTest.java). -- 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

14 years, 7 months

3
12
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2007