These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: Move to jre 1.6 and jboss 5.1
PostPosted: Mon Aug 10, 2009 10:14 am 
Newbie

Joined: Sun Mar 02, 2008 2:05 am
Posts: 6
Hi,
In production, we currently have:
* jdk 1.5
* jboss 4.2.1
* hibernate 3.2.5

We want to move to using jdk 1.6, which means we move to jboss 4.2.3/5.1. Now the issue is hibernate. I saw this ticket:
http://opensource.atlassian.com/project ... e/HHH-2412

I am not worried about compiling hibernate and can continue to use hibernate distribution binaries. But comment by Steve at the end of the above ticket worried me:

>>The "difficult to detect" errors generally fall into the category of problems where Hibernate code is relying on iteration of non-ordered collections.

Also, reading the Jboss 5.x release notes talk about the above issue but don't say anything about using already jdk1.5 compiled hibernate binaries.

Can someone throw more light on this issue? I have searched both jboss and hibernate forums but didn't hear people complain about this.


Top
 Profile  
 
 Post subject: Re: Move to jre 1.6 and jboss 5.1
PostPosted: Mon Aug 10, 2009 11:44 pm 
Newbie

Joined: Sun Mar 02, 2008 2:05 am
Posts: 6
I know people have been using hibernate with jdk 1.6, based on comments on this forum. But my worry is: Is it *reliable enough* to use the current distribution of hibernate 3.3.2 with jre 1.6? One of the comments in HHH-2412:
Quote:
We've not had much luck running Hibernate (generally 3.2.4.sp1.cp06) under JDK 1.6. The problems can be difficult to detect, so an initial switch might appear to work. We can recreate a number of errors, but pinpointing the exact issue has been difficult - but a switch back to JDK 1.5 always resolves anomalies. We would see this error on one of our systems - after the exception occurred the session factory goes bad and only a restart allows continuation.
...
With JDK 1.5 planned to sunset in October of 2009 we see an urgent need for a 1.6 upgrade.


Another comment:
Quote:
The "difficult to detect" errors generally fall into the category of problems where Hibernate code is relying on iteration of non-ordered collections. This is something that changed in at least the sun 1.6 jdk. Those uses need to be cleaned up to require the properly ordered collections when/where needed.


Recently, we also ran our application with jre 1.6 (and hibernate 3.2.5) with seemingly no problems. But we tested only a few scenarios. Just that it will be great if someone can confirm that above is a problem only when using hibernate binaries compiled with jdk 1.6 and its not a problem with current binary distribution of hibernate (which has been compiled using jdk < 1.6). Else, we'll take the plunge and qa report problems, if any :-)


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.