February 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2640) Clob management and deadlock

by Samuel Emangard (JIRA)

Clob management and deadlock ---------------------------- Key: HHH-2640 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2640 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.0.ga Environment: JDK 1.5, Oracle 10g v2 Reporter: Samuel Emangard Priority: Trivial Attachments: Samuel.rar Mapping documents: <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC '-//Hibernate/Hibernate Mapping DTD 3.0//EN' 'http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd'> <hibernate-mapping package="com.toluna.samuel.hibernate.emailtemplate"> <class name="EmailTemplate" table="EmailTemplate"> <id name="id" type="long"> <column name="template_id" not-null="true"/> <generator class="native"/> </id> <property name="name"> <column name="email_name" not-null="false"/> </property> <property name="htmlTextClob" type="clob"> <column name="html_Text" not-null="false"/> </property> <property name="plainTextClob" type="clob"> <column name="plain_Text" not-null="false"/> </property> </class> </hibernate-mapping> Extract also of my Java bean: ublic class EmailTemplate { private long id; private String name; private String plainText = " "; private String htmlText = " "; private Clob plainTextClob; private Clob htmlTextClob; ... Code of the test case: Session ss = HibernateUtil.getSessionFactory().getCurrentSession(); //S_LOGGER.debug("Number of current Hibernate sessions: "+ HibernateUtil.getSessionFactory().getStatistics().getSessionOpenCount()); ss.getTransaction().begin(); EmailTemplate et = (EmailTemplate) ss.load(EmailTemplate.class, new Long("299941536982302")); S_LOGGER.debug(et.getName()); Thread.sleep(5000); S_LOGGER.debug("BEFORE FLUSH"); ss.flush(); S_LOGGER.debug("AFTER FLUSH"); ss.getTransaction().commit(); The generated SQL : The load statement is always generated: /* load com.toluna.samuel.hibernate.emailtemplate.EmailTemplate */ select emailtempl0_.template_id as template1_0_0_, emailtempl0_.email_name as email2_0_0_, emailtempl0_.html_Text as html3_0_0_, emailtempl0_.plain_Text as plain4_0_0_ from EmailTemplate emailtempl0_ where emailtempl0_.template_id=? .... Depending on the implementation of the getter, the following update statement is generated: /* update com.toluna.samuel.hibernate.emailtemplate.EmailTemplate */ update EmailTemplate set email_name=?, html_Text=?, plain_Text=? where template_id=? Here is the getter: Clob getHtmlTextClob() { //1- //return Hibernate.createClob(htmlText != null ? htmlText : " "); //2- return htmlTextClob; } With 1- the update statement is generated With 2- the update statement is not generated Why? Extract of the setter: void setHtmlTextClob(Clob htmlTextClob) { this.htmlTextClob = htmlTextClob; try { if (htmlTextClob != null) { htmlText = HibernateUtil.getStringFromClob(htmlTextClob); //htmlText = "samuel"; } else htmlText = ""; } catch (SQLException e) { throw new RuntimeException(e); } catch (IOException e) { throw new RuntimeException(e); } } I have also another more critical issue which seems tied to the previous: If I write the following piece of test code instead of the one shown above: Session ss = HibernateUtil.getSessionFactory().openSession(); //S_LOGGER.debug("Number of current Hibernate sessions: "+ HibernateUtil.getSessionFactory().getStatistics().getSessionOpenCount()); EmailTemplate et = (EmailTemplate) ss.load(EmailTemplate.class, new Long("299941536982302")); S_LOGGER.debug(et.getName()); Thread.sleep(5000); S_LOGGER.debug("BEFORE FLUSH"); ss.flush(); S_LOGGER.debug("AFTER FLUSH"); As you can see in this piece of code i do not manage transactions explicitly and in that case my 2 java threads generated update statements which never ended: there was a deadlock on the DB. During the last test, If I still did not manage transactions explicitly but I modified the getter like that: Clob getHtmlTextClob() { return htmlTextClob; } Then neither update statements nor deadlock were generated. I wrote this piece of test code to reproduce deadlock I was facing on my Jonas server. Could you please help me to understand this behaviour? Here is anextract of my hibernate.cfg.xml: <property name="connection.url">jdbc:oracle:thin:@192.168.2.7:1521:tlorcl1</property> <property name="connection.username">samuel</property> <property name="connection.password">toluna</property> <property name="connection.driver_class">oracle.jdbc.driver.OracleDriver</property> <property name="dialect">org.hibernate.dialect.Oracle9Dialect</property> <property name="hibernate.show_sql">true</property> <property name="hibernate.format_sql">true</property> <property name="hibernate.use_sql_comments">true</property> <property name="myeclipse.connection.profile">QA</property> <property name="current_session_context_class">thread</property> Thanks in advance Regards Samuel -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-445) Hi Gavin, I am facing the below issue in my application.Could you provide your suggesstion on this?

by Yohida (JIRA)

Hi Gavin, I am facing the below issue in my application.Could you provide your suggesstion on this? --------------------------------------------------------------------------------------------------- Key: EJB-445 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-445 Project: Hibernate Entity Manager Issue Type: Bug Environment: hibernate 2.0 and oracle database Reporter: Yohida RMICallHandler-5 15:55:46,933 WARN [StaleObjectStateException] An operation failed due to stale data net.sf.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) for com.domain.user.bo.ModeListImpl instance with identifier: com.domain.user.bo.ModeListImpl@175718c[objectId=<null>] at net.sf.hibernate.persister.AbstractEntityPersister.check(AbstractEntityPersister.java:513) at net.sf.hibernate.persister.NormalizedEntityPersister.update(NormalizedEntityPersister.java:664) at net.sf.hibernate.persister.NormalizedEntityPersister.update(NormalizedEntityPersister.java:639) at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:52) at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2449) at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2435) at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2393) at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2261) at com.retek.rpm.domain.core.persistence.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:201) -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2860) Consolidate Session creation options/parameters

by Steve Ebersole (JIRA)

Consolidate Session creation options/parameters ----------------------------------------------- Key: HHH-2860 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2860 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 This is a partial follow-on for the deprecation of Session#connection() -- 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, 9 months

2
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3646) implement Criteria API querying of collection-of-component

by David Mansfield (JIRA)

implement Criteria API querying of collection-of-component ---------------------------------------------------------- Key: HHH-3646 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3646 Project: Hibernate Core Issue Type: Patch Components: query-criteria Affects Versions: 3.2.6 Environment: hibernate 3.2.6, tested on linux 64-bit openjdk 1.6 (jdk1.5 for compiling). mapping created under annotations 3.3.1ga Reporter: David Mansfield Attachments: hib-core-query-collection-of-elements-3_2_6.patch the attached patch implements a first cut, extremely rough, yet working extension of the CriteriaQueryTranslator class to allow for querying of properties of components inside a collection, or querying properties of associated elements of components inside a collection. eg for * code is lightly tested, this example is for illustrative purposes only * i use annotations, so my example is expressed in those terms, and i've only tested with mappings generated via annotations, however, the modifications only apply to the core. @Entity class Order { @Id String id; @CollectionOfElements Set<OrderLineItem> lineItems; } @Embeddable class OrderLineItem { @ManyToOne Product product; Integer quantity; } @Entity class Product { String name; } Then we can now do: Criteria c = session.createCriteria(Order.class) .createCriteria("lineItems") .add(Restrictions.gt("quantity", new Integer(1)) .list(); or Criteria c = session.createCriteria(Order.class) .createCriteria("lineItems") .createCriteria("product") .add(Restrictions.like("name", "cake%") .list(); -- 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, 9 months

7
25
0 / 0

[Hibernate-JIRA] Created: (HHH-3769) Enabling jmx statistics cause OOM

by Sid (JIRA)

Enabling jmx statistics cause OOM --------------------------------- Key: HHH-3769 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3769 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.2.0.ga Reporter: Sid It looks like when org.hibernate.jmx.StatisticsService.statisticsEnabled=true all query strings get logged to org.hibernate.stat.StatisticsImpl.queryStatistics. There is a clear method in org.hibernate.stat.StatisticsImpl that reset all statistics but i don't see this method being called other than when some one calls org.hibernate.jmx.StatisticsService.clear() As queryStatistics is a HasMap this will causes OOM. -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3593) be able to configure statistics enablement

by John Mazzitelli (JIRA)

be able to configure statistics enablement ------------------------------------------ Key: HHH-3593 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3593 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: John Mazzitelli Priority: Minor Right now, in order to enable Hibernate to collect and emit statistics to monitoring tools, your application has to manually execute code similar to the following: StatisticsService mBean = new StatisticsService(); SessionFactory sessionFactory = ...get hibernate session factory... mBean.setSessionFactory(sessionFactory); ObjectName objectName = new ObjectName("Hibernate:application=MY_APP_NAME,type=statistics"); MBeanServer mbs = ManagementFactory.getPlatformMBeanServer(); mbs.registerMBean(mBean, objectName); sessionFactory.getStatistics().setStatisticsEnabled(true); It would be nice if this was configurable, so a user of Hibernate doesn't need to write this code. For example: hibernate.statistics.enabled=true hibernate.statistics.objectname=Hibernate:application=MY_APP_NAME,type=statistics hibernate.statistics.mbeanserver=*platform* This would turn on Hibernate statistics and tell it to register the Statistics MBean in the JVM's platform MBean Server (ManagementFactory.getPlatformMBeanServer). Of course, *platform* would only be valid on Java5 or higher VMs. Note that hibernate will need to allow the object name to be configurable as well. Or... hibernate.statistics.enabled=true hibernate.statistics.objectname=Hibernate:application=MY_APP_NAME,type=statistics hibernate.statistics.mbeanserver=my_mbs_name This tells Hibernate to register the MBean in the named MBeanServer where the "my_mbs_name" is the default domain name of the MBeanServer you want (if it doesn't exist, Hibernate should create the MBeanServer with the named default domain). In fact, I had the Remoting project do something similar, so you can see code that gets the MBeanServer using these two ways by looking at the .patch attached to: https://jira.jboss.org/jira/browse/JBREM-746 and its related fix. -- 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, 9 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2680) Blobs not updated on Session.merge() for detached instances

by Timo Thomas (JIRA)

Blobs not updated on Session.merge() for detached instances ----------------------------------------------------------- Key: HHH-2680 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2680 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1, 3.2.2 Environment: Windows XP Prof., Java 1.5_010, HSQLDB 1.8.0 Reporter: Timo Thomas Attachments: BlobTest.zip Blob columns are not updated when a detached instance is saved at the session with merge(). See attached TestCase. -- 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, 9 months

11
27
0 / 0

[Hibernate-JIRA] Created: (HHH-4509) Ability to control JBoss Cache eviction via session factory properties

by Brian Stansberry (JIRA)

Ability to control JBoss Cache eviction via session factory properties ---------------------------------------------------------------------- Key: HHH-4509 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4509 Project: Hibernate Core Issue Type: New Feature Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 A la what Galder has added for the Infinispan integration. -- 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, 9 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2843) org.hibernate.PropertyAccessException: IllegalArgumentException occurred calling getter of natural Key component

by Charles Canning (JIRA)

org.hibernate.PropertyAccessException: IllegalArgumentException occurred calling getter of natural Key component ---------------------------------------------------------------------------------------------------------------- Key: HHH-2843 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2843 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: Linux Reporter: Charles Canning The full description is here in the forums: http://forum.hibernate.org/viewtopic.php?t=979408 I will provide more details if I can. -- 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, 9 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-438) @IndexedEmbedded does not work for child classes in inheritance tree

by Ted Williams (JIRA)

@IndexedEmbedded does not work for child classes in inheritance tree -------------------------------------------------------------------- Key: HSEARCH-438 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-438 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.1.GA Environment: Jboss 4.2.3.GA Hibernate Core 3.2 Hibernate Search 3.1.1.GA Reporter: Ted Williams Priority: Critical Attachments: Classes.zip When using @IndexedEmbedded on a set/list of parent/top classes the @Field annotations in the child classes are not picked up and indexed. @IndexedEmbedded(depth=100) @OneToMany(fetch = FetchType.LAZY, mappedBy = "top", cascade = CascadeType.ALL) public Set<Parent> getParents() { return parents; } public class Child extends Parent { private String childName; @Field(name = "childName", index=Index.TOKENIZED) // This field is not picked up!!! . . } -- 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, 9 months

5
23
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2010