December 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2948) QueryStatistics.executionMinTime always = 0

by pi zhigang (JIRA)

QueryStatistics.executionMinTime always = 0 -------------------------------------------- Key: HHH-2948 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2948 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.0.ga Environment: database Oracle10g Reporter: pi zhigang Priority: Critical Becuase executionMinTime is initialized as zero (long default): --- org.hibernate.stat.QueryStatistics.java ---- private long executionMinTime; and, the logic for assignment statement is: void executed(long rows, long time) { if (time < executionMinTime) executionMinTime = time; ... I think the initial value for executionMinTime should be: private long executionMinTime = Long.MAX_VALUE; -- 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

18 years, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3021) Document that application servers may ignore Hibernate connection properties

by James Roper (JIRA)

Document that application servers may ignore Hibernate connection properties ---------------------------------------------------------------------------- Key: HHH-3021 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3021 Project: Hibernate3 Issue Type: Improvement Components: documentation Reporter: James Roper Priority: Trivial I'd just like to suggest that it would be really helpful to put a note in the configuration section of the documentation stating that JEE application servers may ignore the hibernate connection properties. For example, JDBC datasources returned by Websphere AS as shareable resource refs ignore the transaction isolation level set on them (this makes sense, if one application modifies the isolation level of a connection, it could produce unexpected results in another application). This has nothing to do with Hibernate, except that it means that the hibernate.connection.isolation property will be ignored. It would just be nice to the Hibernate users if a note was put into the documentation mentioning this before they start trying to use the hibernate properties to configure connection specific properties. -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1582) PostInsertListener + "post-commit-insert"

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582?page=c... ] Emmanuel Bernard commented on HHH-1582: --------------------------------------- javax.transaction.Synchronization and o.h.Transaction.registerSynchronization() > PostInsertListener + "post-commit-insert" > ----------------------------------------- > > Key: HHH-1582 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.1.2 > Reporter: Daniel Gredler > Assignee: Emmanuel Bernard > Fix For: 3.3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > I'm using a custom PostInsertEventListener mapped to the "post-commit-insert" event to process domain objects. However, PostInsertEventListener's onPostInsert(PostInsertEvent) is getting called even when the insert was not successful (ie, due to a unique constraint in the database or some such). It looks to me like Hibernate should either a) not invoke the event listener if the insert failed or b) provide state (perhaps in the form of a boolean indicating success/failure). Personally I'd rather the method not be called on failure, but there may be use cases out there for the second option. > As an example, it looks like Hibernate's own LuceneEventListener will add a domain object to the index in onPostInsert(PostInsertEvent) even if the insert failed. > Note that this problem also seems to exist in EntityDeleteAction and EntityUpdateAction (which would mean that Hibernate's LuceneEventListener removes domain objects from the Lucene index even if the delete fails!). -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-1026) Change visibility of abstract method getName in org.hibernate.tool.ant.ExporterTask from friendly to protected or public

by Peter Merker (JIRA)

Change visibility of abstract method getName in org.hibernate.tool.ant.ExporterTask from friendly to protected or public ------------------------------------------------------------------------------------------------------------------------ Key: HBX-1026 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1026 Project: Hibernate Tools Issue Type: Improvement Affects Versions: 3.2.cr1 Environment: Doesn't really matter. Reporter: Peter Merker In order to be able to subclass ExporterTask in your own custom package it is necessary to change the visibility of it's abstract method getName from friendly to either protected or public. -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1582) PostInsertListener + "post-commit-insert"

by Darren Bell (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582?page=c... ] Darren Bell commented on HHH-1582: ---------------------------------- Could you explain "Transaction synchronization" please. > PostInsertListener + "post-commit-insert" > ----------------------------------------- > > Key: HHH-1582 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.1.2 > Reporter: Daniel Gredler > Assignee: Emmanuel Bernard > Fix For: 3.3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > I'm using a custom PostInsertEventListener mapped to the "post-commit-insert" event to process domain objects. However, PostInsertEventListener's onPostInsert(PostInsertEvent) is getting called even when the insert was not successful (ie, due to a unique constraint in the database or some such). It looks to me like Hibernate should either a) not invoke the event listener if the insert failed or b) provide state (perhaps in the form of a boolean indicating success/failure). Personally I'd rather the method not be called on failure, but there may be use cases out there for the second option. > As an example, it looks like Hibernate's own LuceneEventListener will add a domain object to the index in onPostInsert(PostInsertEvent) even if the insert failed. > Note that this problem also seems to exist in EntityDeleteAction and EntityUpdateAction (which would mean that Hibernate's LuceneEventListener removes domain objects from the Lucene index even if the delete fails!). -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1725) lazy properties, events and collection xxx was not processed by flush exception and EJB3 incompatibility

by Adrian Pillinger (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1725?page=c... ] Adrian Pillinger commented on HHH-1725: --------------------------------------- Please could a hibernate developer comment on why this was rejected. It seems as though lots of us encounter this bug and it is very important to our development that it is fixed. > lazy properties, events and collection xxx was not processed by flush exception and EJB3 incompatibility > -------------------------------------------------------------------------------------------------------- > > Key: HHH-1725 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1725 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.2.0.cr2 > Reporter: Tomasz Bech > > It is realted to anomaly: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1540 > 'When using custom event listeners, sometimes you mess with (and initialize) lazy collections by mistake, which causes CollectionEntry.postFlush(PersistentCollection) to throw an AssertionFailure' > It is questionable why AT ALL exception is raised in this case! > What is the most important: EJB3 spec is not prohibiting to check/read/ object involved in the event, so current implementation is agains EJB3 spec. > Events are often used for validation so it is quite probable that the lazy property (collection) has to be accessed - and when it is lazy and not initialized before the exception is raised. Why hibernate cannot treat it in nicer way and allow such actions. > One workaround is to not-use-lazy (very bad). > Second workaround: in the code outside flush (not in event) pre-initialize all lazy properties (in fact simulation of 'not-lazy). -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-443) AssertionFailure occurs with listeners on models with many-to-many collection.

by Adrian Pillinger (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-443?page=co... ] Adrian Pillinger commented on HHH-443: -------------------------------------- We use a new session in the listener and still encounter this bug. > AssertionFailure occurs with listeners on models with many-to-many collection. > ------------------------------------------------------------------------------- > > Key: HHH-443 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-443 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.2 > Environment: Hibernate version 3.0.2 > Oracle9i > Reporter: Tom Kucharski > > The problem occurs when insert or update listener is created on hibernate session on model with many-to-many collection and listener is making some queries with this model. > The listener is needed for checking data integrity , so I need to make some select clauses within this listener. > That is my code from PreInsertEventListener.onPreInsert() method (some lines were removed for clearance) : > //I set this on FlushMode.NEVER because StackOverflowError is thrown > event.getSession().setFlushMode(FlushMode.NEVER); > // Function below makes database query using criteria API > String o = listener.validate(event.getEntity(),event.getSession()); > if (o != null) { > // I don't know if this is correct, but why not?? I don't catch this exception in my code and I have auto_close_session and auto_flush_session on true > throw new ConstraintViolationException(o,null,null); > } > // set to default settings > event.getSession().setFlushMode(FlushMode.AUTO); > That's exception from my WebLogic 8.1 server > <2005-05-05 18:05:15 CEST> <Error> <org.hibernate.AssertionFailure> <000000> <an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) > org.hibernate.AssertionFailure: collection was not processed by flush() > at org.hibernate.engine.CollectionEntry.postFlush(CollectionEntry.java:144) > at org.hibernate.event.def.AbstractFlushingEventListener.postFlush(AbstractFlushingEventListener.java:305) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:28) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:678) > at pl.softbank.cepik.modris.common.client.util.DefaultModrisClient.updateObject(DefaultModrisClient.java:196) > at pl.softbank.cepik.modris.dict.common.client.CommonDictModrisClient.insert(CommonDictModrisClient.java:71) -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3020) Cannot control Hibernate reverse engineering strategy for NUMERIC(1)

by alessandro.regonini (JIRA)

Cannot control Hibernate reverse engineering strategy for NUMERIC(1) -------------------------------------------------------------------- Key: HHH-3020 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3020 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.1 Environment: WinXP with Orcale 9i Reporter: alessandro.regonini I cannot change the default Hibernate behaviour to reverse engineering a NUMERIC(1) into a boolean java data type. I tried to modify the reverse engineering file forcing all possible mapping without success. How to reverse engineering an Oracle 9 NUMERIC(1) into a java.lang.Integer ??? -- 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

18 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Updated: (HBX-623) Add ability in reverse engineering config file to support cascades

by Jeffrey Williams (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-623?page=co... ] Jeffrey Williams updated HBX-623: --------------------------------- Attachment: many-to-one-attributes-with-test.diff Ok, I have added a simple Junit test that test that the attribute to the many to one has been picked up and added to the hibernate configuration file. Not sure if you need any thing more advanced. > Add ability in reverse engineering config file to support cascades > ------------------------------------------------------------------ > > Key: HBX-623 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-623 > Project: Hibernate Tools > Issue Type: Patch > Components: reverse-engineer > Affects Versions: 3.0beta2 > Environment: Hibernate Tools Beta 5 > Reporter: tony anecito > Priority: Critical > Fix For: 3.2.1 > > Attachments: many-to-one-attributes-with-test.diff, many-to-one-attributes.diff > > > Please add ability to add cascade tag to resultant mapping files in the reveng file. Currently have to modifiy velocity template file -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-623) Add ability in reverse engineering config file to support cascades

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-623?page=co... ] Max Rydahl Andersen commented on HBX-623: ----------------------------------------- etc needs to be on the classpath so hibernate.properties gets picked up. to run from inside eclipse just run the tests like a normal junit test. > Add ability in reverse engineering config file to support cascades > ------------------------------------------------------------------ > > Key: HBX-623 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-623 > Project: Hibernate Tools > Issue Type: Patch > Components: reverse-engineer > Affects Versions: 3.0beta2 > Environment: Hibernate Tools Beta 5 > Reporter: tony anecito > Priority: Critical > Fix For: 3.2.1 > > Attachments: many-to-one-attributes.diff > > > Please add ability to add cascade tag to resultant mapping files in the reveng file. Currently have to modifiy velocity template file -- 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

18 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2007