开发者

Hibernate Issuing too many queries on MySQL

I am using hibernate 3.0 in spring with Mysql 5. I have configured JNDI datasource in JBOSS and using it in application context.

My Problem is that Hibernate is issuing average 466.4 queries per second to the database with hardly any load on website.

ApplicationCon开发者_开发问答text.xml snippet is

<bean id="dataSource" class="org.springframework.jndi.JndiObjectFactoryBean" scope="singleton">
    <property name="jndiName" value="java:MyCustomDSName" />
    <property name="resourceRef" value="true" /> 
</bean>

I am using JTA transaction at java level. Any help welcome.


One of these should be the case

  • You're getting/processing too many requests - unlikely in dev.
  • You're running into an N+1 select condition - very common.

Please post your domain model, and the queries being executed.


This is typically caused by N+1 query issues. However, you can use a unit test assert mechanism to find all those JPA and Hibernate data access methods that cause N+1 query issues, like this JUnit assert mechanism using datasource-proxy.

Also, you are better off switching all EAGER associations to LAZY because EAGER fetching can easily generate N+1 query issues if you forget to JOIN FETCH the associations in every JPQL or Criteria API query.

LAZY loading can also cause N+1 query issues. This happens when you iterate over a collections of child entities while initializing a parent Proxy on every iteration. Again, this can be easily detected using this JUnit assert mechanism using datasource-proxy.


How are you using JTA transactions? If every Java method is marked to require a new transaction, this could explain part of your problem. Also, your Hibernate object relationships should be reviewed. If you have complex relationships, a lot of eagerly-loaded objects defined in your model relationships, or circular relationships, you could have harder problems to solve.

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜