blocks|key|5217311|text|其中之一应该是这样的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5217312|5217313|您收到/处理的请求太多-在dev.|unordered-list-item|5217314|您遇到N%2B1+select条件是不太可能的-这很常见。|5217315|5217316|请发布您的域模型，以及正在执行的查询。|5217317|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

One of these should be the case

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

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

blocks|key|2599481|text|您如何使用JTA事务？如果每个Java方法都被标记为需要一个新事务，这可以部分解释您的问题。此外，还应该检查Hibernate对象关系。如果您有复杂的关系，在模型关系或循环关系中定义了许多急切加载的对象，那么您可能会有更难解决的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2599482|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|5194327|text|这通常是由N%2B1查询问题引起的。但是，您可以使用单元测试断言机制来查找所有那些引起N%2B1查询问题(如this+JUnit+assert+mechanism+using+datasource-proxy+)+JPA和Hibernate数据访问方法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5194328|此外，最好将所有的EAGER关联都切换到LAZY，因为如果您忘记在每个JPQL或Criteria+API查询中联接获取关联，EAGER+fetching很容易生成N%2B1查询问题。|5194329|LAZY+loading还可能导致N%2B1查询问题。当您在每次迭代时初始化父代理时，当您迭代子实体的集合时，就会发生这种情况。同样，使用this+JUnit+assert+mechanism+using+datasource-proxy可以轻松地检测到这一点。|5194330|entityMap|0|LINK|mutability|MUTABLE|url|https://vladmihalcea.com/how-to-detect-the-n-plus-one-query-problem-during-testing/|1|https://vladmihalcea.com/eager-fetching-is-a-code-smell/|2|https://vladmihalcea.com/the-best-way-to-handle-the-lazyinitializationexception/|3^0|2C|G|1E|1E|0|0|9|5|K|4|1Q|E|1|0|0|4|2T|G|0|C|2|1V|1E|3|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|H|3|I|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@$9|1F|A|1G|1|1H]|$9|1I|A|1J|1|1K]]|E|$]]|$1|J|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]|T|$5|M|N|O|E|$P|U]]|V|$5|M|N|O|E|$P|Q]]]]

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 <a href="https://vladmihalcea.com/how-to-detect-the-n-plus-one-query-problem-during-testing/" rel="nofollow noreferrer">this JUnit assert mechanism using <code>datasource-proxy</code></a>. 

Also, you are better off switching all <code>EAGER</code> associations to <code>LAZY</code> because <a href="https://vladmihalcea.com/eager-fetching-is-a-code-smell/" rel="nofollow noreferrer">EAGER fetching</a> can easily generate N+1 query issues if you forget to JOIN FETCH the associations in every JPQL or Criteria API query.

<a href="https://vladmihalcea.com/the-best-way-to-handle-the-lazyinitializationexception/" rel="nofollow noreferrer"><code>LAZY</code> loading</a> 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 <a href="https://vladmihalcea.com/how-to-detect-the-n-plus-one-query-problem-during-testing/" rel="nofollow noreferrer">this JUnit assert mechanism using <code>datasource-proxy</code></a>.

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. 

ApplicationContext.xml snippet is 

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

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

Hibernate Issuing too many queries on MySQL

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在spring中使用hibernate 3.0和MySQL5。我已经在JBOSS中配置了JNDI数据源，并在应用程序上下文中使用它。我的问题是，Hibernate平均每秒向数据库发出466.4个查询，而网站上几乎没有任何负载。ApplicationContext.xml代码片段是<bean id="dataSourc...

问Hibernate在MySQL上发出过多查询
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Hibernate在MySQL上发出过多查询EN