May 2012 - hibernate-dev - Jboss List Archives

Hibernate 4.x, JTA(BMT) transactions no longer interchangeable with Hibernate transaction facade?

by Zachary Kurey

Hi all, Am I correct in my interpretation that Hibernate 4 no longer supports interchangeably being able to use either the Hibernate transaction facade(session.beginTransaction) vs. UserTransaction or CMT? I say this because it appears that I always must call session.beginTransaction() when configured to use JTATransactionFactory, in order to have JtaTransaction->local status of active. If local status is not active Hibernate makes no attempt to check the provided JtaPlatform if there is a user transaction in process and blows up whenever trying to execute any changes to the db. In 3.x this worked fine since JTATransactionFactory->isTransactionInProgress always tried to find the configured transaction manager and checked the transaction status properly. But in 4.x I'm not seeing how local status gets set to active to prevent a blow up unless I both call userTransaction.begin() AND session.beginTransaction()... The same problems exist when interacting through the EntityManager API. Even in the ManagedDrivingTest it looks like it is assumed that the client will call session.beginTransaction() after either a CMT or BMT has been started. I would cut over to using the Hibernate facade exclusively, but now it throws 'nested transactions not supported' if beginTransaction is invoked multiple times. The Spring PlatformTransactionManager API deals with multiple layered invocations more gracefully, so I've mostly used that in the past for programmatic transaction management. But regardless, looking at the source there seems to be a new requirement to always have session.beginTransaction() invoked in application code. I've spent days trying to figure out if I've made a configuration mistake, and at this point I'm at the conclusion that either Hibernate behavior in this area was intentionally changed, or that this is a bug. If its a bug it would probably break a lot of apps upgrading from 3.x to 4.x that use programmatically controlled transactions. So I thought I'd just reach out on the mailing list for clarification, or to have an obvious misconfiguration or misunderstanding corrected. For more info on my JTA config there is a forum post I made that is unrelated(realized my error on that topic) here: https://forum.hibernate.org/viewtopic.php?p=2454363 Thanks, Zach

13 years, 7 months

1
1
0 / 0

Hibernate Validator 4.3.0.Final seen in the wild

by Hardy Ferentschik

For more info about $subject see in.relation.to - http://in.relation.to/23184.lace --Hardy

13 years, 7 months

1
0
0 / 0

Released Hibernate Search 4.1.1.Final

by Sanne Grinovero

Hello all, we just uploaded artifacts and distribution bundles for Hibernate Search 4.1.1.Final; for all people using 4.1.0 it's recommended to upgrade! More information on the blog: http://in.relation.to/Bloggers/HibernateSearch411FinalFixFileHandleLeakAn... Cheers, Sanne

13 years, 7 months

1
0
0 / 0

[HSEARCH] Worker Configuration

by Andrej Golovnin

Hi all, I'm in process to migrate an application from an old Hibernate Search version to the latest one. We have been used own implementation of Worker. In the old Hibernate Search version it was possible to define own implementation of Worker using the property "hibernate.search.worker.scope". But it seems not possible to do it in the latest version although the Hibernate Search Guide suggest to use this property. After studying the sources of Hibernate Search I have found that the property to be used is "worker.scope". This change was introduced with the work on the issue HSEARCH-761. Could you please verify what is the right property name and either correct the Hibernate Search Guide or change the property name in the Environment class to the old one. Thanks in advance! Best regards Andrej Golovnin

13 years, 7 months

4
7
0 / 0

problem in select specified fields

by gayan sukumal wiharagoda

Hi, I am new to hibanate,Stuts and Tile. Now I want to get selected specified columns. I have mention the code below. It is not working. List<SelelctItemList> list = new ArrayList<SelelctItemList>(); Query query = (Query) session.createQuery("select s.item_id,s.name,s.unit_price_sel,s.unit_price_buy,su.quantity from service_uses as su INNER JOIN stocks as s ON su.item_id=s.item_id where service_id="+ serviceId); list = ((org.hibernate.Query) query).list(); cheers, Gayan

13 years, 7 months

1
1
0 / 0

Porting seam DVD store example to OGM

by Alan F

Hi all, I've converted the seam hotel booking JPA example to use Hibernate OGM, specifically the MongoDB dialect, and documented what needed to be done on the wiki. The instructions and code should be fairly relevant to the Infinispan dialect too. I did encounter a few issues doing this so I hope the instructions will be useful to others. The main change is that the queries needed converting from criteria queries to Hibernate search/lucene. https://community.jboss.org/wiki/PortingSeamDVDStoreExampleToOGM The code is available on my github: https://github.com/ajf8/seam-dvd-store-ogm Let me know if you spot any errors/improvements in the wiki page or have any fixes to the code. Regards,

13 years, 7 months

1
1
0 / 0

Where are the batched fetch statements generated?

by Clemens Eisserer

Hi, Sorry for posting to the developers list, I have tried all other places dedicated to end-user support, however it seems the question is too in-depth :/ Is it possible to disable prepared statement caching for batched fetching, so I end up with a single query in the < default_batch_fetch_size case only instead of the fixed-size batch loading hibernate does by default? If its not configureable, I would be really grateful for a pointer to the source where that caching and sub-batch-by-sub-batch loading is done. I am latency bound with a low-loaded postgresql-server, so I would be happy if I could trade lower server load with less roundtrips. Thank you in advance, Clemens

13 years, 7 months

1
1
0 / 0

Jenkins Jobs

by Steve Ebersole

Strong, I had to kill hibernate-core-master-matrix job #242. It had been hanging for the last 8+ hours without every even having started any of the individual matrix builds. Is there any way to tell why it has hanging? -- steve(a)hibernate.org http://hibernate.org

13 years, 7 months

2
5
0 / 0

Hibernate Developer IRC meeting - 5/03

by Emmanuel Bernard

Sorry I could not assist the meeting live but reviewed the logs and had some remarks, so ehre are the logs and my remarks :) ## Meeting logs http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2012/... Minutes (text):http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev... Log: http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2012/... ## About parallel arrays vs arrays of objects Even today, there is a cost in using Objects or HashMap as data placeholders. This might not be relevant for us especially since we are not using them for "live" data but since memory footprint has always been a concern for Hibernate, it's worth mentioning. This presentation is quite interesting and show the extra memory cost of such structure compared to arrays http://www.cs.virginia.edu/kim/publicity/pldi09tutorials/memory-efficient... ## PessimisticLockException versus LockAcquisitionException I am not certain of that and Git history got cut short with the migration of entitymanager into core. But I do have recollections of some lock exceptions that were not catch up and I had to use PessimisticLockException. It could have been a change triggered by the TCK. Again I might be wrong, it was a long time ago. Plus ORM's core has evolved since. Emmanuel

13 years, 7 months

5
9
0 / 0

Re: [hibernate-dev] Hibernate Developer IRC meeting - 5/03

by Hardy Ferentschik

On May 4, 2012, at 1:51 PM, Steve Ebersole wrote: > As for perf issues OGM uncovered in ORM... First, none of those involved anything close to the discussion here; they dealt mostly with small things (like hashCode caching) that became big because of size of scale. Second, thats actually exactly how you should discover and treat perf issues. Right, especially the second sentence.

13 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-dev May 2012