[Hibernate-JIRA] Closed: (HHH-910) Queries consume more and more clockticks as Session life goes on
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-910?page=co... ]
Steve Ebersole closed HHH-910.
------------------------------
Closing stale resolved issues
> Queries consume more and more clockticks as Session life goes on
> ----------------------------------------------------------------
>
> Key: HHH-910
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-910
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Affects Versions: 3.1 beta 2
> Environment: Confirmed on WinXP+MSSQL and OS X+MySQL.
> Hibernate 3.1b2, one Session per thread.
> Reporter: Karl Wettin
> Priority: Critical
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> I haven't had time to trace it down in the Hibernate source code yet. I'll do it later this week if nobody beats me to it.
> As I have been importing huge amounts of data to my database, data that might be updates and that might be creations, I've have noticed that the querys takes more and more time. Starting at 3ms, 50000 queries later at 10 seconds to execute. In the begining I though it took more and more time since the number of rows in my tables grew, but 10 seconds? makePersistent and commit never took more time, just queries.
> So then I decided to commit the transaction and recreate the Session every 50 instances made pesistent. Now it stays down. So there is something really bad going on with the Session.
--
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
15 years, 1 month
[Hibernate-JIRA] Closed: (HHH-962) org.hibernate.dialect.IngresDialect no longer works with paged queries
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-962?page=co... ]
Steve Ebersole closed HHH-962.
------------------------------
Closing stale resolved issues
> org.hibernate.dialect.IngresDialect no longer works with paged queries
> ----------------------------------------------------------------------
>
> Key: HHH-962
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-962
> Project: Hibernate Core
> Issue Type: Bug
> Affects Versions: 3.1 rc3
> Environment: JBoss 4.0.3RC2, EJB3RC2, Java1.5_04, Ingres 3.0.2, WinXP
> Reporter: Stefan Lindner
> Attachments: IngresDialectFix.patch
>
>
> Thsi issue is related to the Ingres support of EJB/Hibernate 3.1 Beta 3
> The following code fragment worked with EJB Beta1
> Query q = manager.createQuery("Select org FROM OrganisationBean org");
> query.setMaxResults(1);
> OrganisationBean ob = (OrganisationBean)(query.getSingleResult());
> It does not work anymore with EJB3RC1/RC2. The error messge now is
> javax.ejb.EJBTransactionRolledbackException = null; CausedByException is:
> paged queries not supported
> My dialect is set to org.hibernate.dialect.IngresDialect
> <property name="hibernate.dialect" value="org.hibernate.dialect.IngresDialect" />
> When I change the dialect to org.hibernate.dialect.GenericDialect the code works again
> with EJB3RC1+RC2. This means
> 1, Ingres supports paged queries
> 2. The dialect org.hibernate.dialect.IngresDialect properly managed paged queries in
> EJB3Beta1
> 3. The dialect org.hibernate.dialect.IngresDialect does not handle this correct anymore.
--
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
15 years, 1 month
[Hibernate-JIRA] Closed: (HHH-1117) Incorrect org.hibernate.jdbc.ConnectionManager.isAggressiveRelease()
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1117?page=c... ]
Steve Ebersole closed HHH-1117.
-------------------------------
Closing stale resolved issues
> Incorrect org.hibernate.jdbc.ConnectionManager.isAggressiveRelease()
> --------------------------------------------------------------------
>
> Key: HHH-1117
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1117
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Affects Versions: 3.1 rc2
> Environment: Hibernate 3.1 rc2
> Reporter: Adamansky Anton
> Assignee: Steve Ebersole
> Priority: Critical
>
> Hibernate is aggressively releases connections
> in the following invironment:
> hibernate.connection.release_mode=after_transaction
> hibernate.connection.autocommit=false & connection.getAutoCommit() == false
> But accourdingly to javadoc org.hibernate.jdbc.ConnectionManager.isAggressiveRelease()
> Connections will be aggresivelly released after each statement if either:
> 1) The defined release-mode is {@link ConnectionReleaseMode#AFTER_STATEMENT};
> 2) The defined release-mode is {@link ConnectionReleaseMode#AFTER_TRANSACTION}
> Hibernate fails the case 2)
> I've looked into code (), and found
> org.hibernate.jdbc.ConnectionManager.isAggressiveRelease() {
> ....
> return releaseMode == ConnectionReleaseMode.AFTER_STATEMENT ||
> ( releaseMode != ConnectionReleaseMode.AFTER_TRANSACTION && inAutoCommitState );
> }
> but, it should be:
> org.hibernate.jdbc.ConnectionManager.isAggressiveRelease() {
> ....
> return releaseMode == ConnectionReleaseMode.AFTER_STATEMENT ||
> ( releaseMode == ConnectionReleaseMode.AFTER_TRANSACTION && inAutoCommitState );
> }
> Anton
--
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
15 years, 1 month