blocks|key|178425|text|这可能不是你想要的。但你到底要用什么来做游泳池？如果您还没有决定，请查看C3PO，它提供了用于监视的JMX公开属性|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|178426|entityMap|0|LINK|mutability|MUTABLE|url|http://sourceforge.net/projects/c3p0/^0|10|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

This might not be what you want. But what are you using for the pool anyway? If you haven't decided, check out <a href="http://sourceforge.net/projects/c3p0/" rel="nofollow">C3PO</a>, it provides JMX exposed attributes for monitoring

blocks|key|384497|text|对于典型的服务器端java应用程序，最首选的监视方式之一是通过JMX。大多数应用程序(包括连接池)提供了默认的JMX+(称为MBeans或托管bean)，可用于监视。连接池(例如，C3P0)创建一个MBean，将其与底层可用的JMX服务器绑定(几乎所有应用服务器中都有它，包括tomcat、JBoss)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|384498|此MBean将保存有关连接池的所有信息。您已经提到您正在使用JBoss服务器。在Jboss提供的web管理控制台上，应该有一个条款可以查看所有的MBeans+(包括已部署连接池的MBean+)。|384499|另一种监控方式是通过JConsole实用程序，这是随Java而来的。同样的JConsole也可以用于监视JBoss。|384500|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.oracle.com/jmxetc/entry/what_is_jmx|1|http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html|2|http://community.jboss.org/wiki/JBossMBeansInJConsole^0|1J|4|V|3|0|0|0|A|8|1|1E|7|2|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]|$9|16|A|17|1|18]]|E|$]]|$1|J|3|-4|5|6|7|19|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]]]]

For a typical server side java application, one of the most preferred way of monitoring is through the <a href="http://blogs.oracle.com/jmxetc/entry/what_is_jmx">JMX</a>. Most of the application (including connection pools) offer a default JMX bean (called MBeans or managed beans) which can be used for monitoring. A connection pool (e.g. C3P0) creates an MBean binds it with the underlying available JMX server (which is there in almost all of the application server including tomcat, JBoss)

This MBean will hold all the information about the connection pool. You have mentioned you are using JBoss server. On the web admin console offered by Jboss, there should be a provision to view all the MBeans (including the MBean of deployed Connection pool). 

Another way to monitor is though <a href="http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html">JConsole</a> utility which comes with Java. The same JConsole can be used to <a href="http://community.jboss.org/wiki/JBossMBeansInJConsole">monitor the JBoss</a> AS as well.

blocks|key|384538|text|FlexyPool是一个数据源代理，为几乎所有已知的连接池提供更好的监视和故障转移：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|384539|Apache+DBCP|unordered-list-item|384540|Apache+DBCP2|384541|C3P0|384542|BoneCP|384543|HikariCP|384544|Tomcat+CP|384545|Vibur+DBCP|384546|Bitronix事务管理器|384547|Atomikos+TransactionsEssentials|384548|它允许您监视以下指标：|384549|并发连接直方图|384550|并发连接请求直方图|384551|数据源连接获取时间直方图|384552|连接租赁时间直方图|384553|最大池大小直方图|384554|全连接获取时间直方图|384555|溢出池大小直方图|384556|重试尝试直方图|384557|通过这种方式，您可以调整池的大小，以便它能够容纳尽可能多的应用程序节点，同时保护您不受某些意外交通高峰的影响。|384558|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/vladmihalcea/flexy-pool|1|http://vladmihalcea.com/the-simple-scalability-equation/^0|0|9|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|19|6|1|0^^$0|@$1|2|3|4|5|6|7|1Q|8|@]|9|@$A|1R|B|1S|1|1T]]|C|$]]|$1|D|3|E|5|F|7|1U|8|@]|9|@]|C|$]]|$1|G|3|H|5|F|7|1V|8|@]|9|@]|C|$]]|$1|I|3|J|5|F|7|1W|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|1X|8|@]|9|@]|C|$]]|$1|M|3|N|5|F|7|1Y|8|@]|9|@]|C|$]]|$1|O|3|P|5|F|7|1Z|8|@]|9|@]|C|$]]|$1|Q|3|R|5|F|7|20|8|@]|9|@]|C|$]]|$1|S|3|T|5|F|7|21|8|@]|9|@]|C|$]]|$1|U|3|V|5|F|7|22|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|23|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|F|7|24|8|@]|9|@]|C|$]]|$1|10|3|11|5|F|7|25|8|@]|9|@]|C|$]]|$1|12|3|13|5|F|7|26|8|@]|9|@]|C|$]]|$1|14|3|15|5|F|7|27|8|@]|9|@]|C|$]]|$1|16|3|17|5|F|7|28|8|@]|9|@]|C|$]]|$1|18|3|19|5|F|7|29|8|@]|9|@]|C|$]]|$1|1A|3|1B|5|F|7|2A|8|@]|9|@]|C|$]]|$1|1C|3|1D|5|F|7|2B|8|@]|9|@]|C|$]]|$1|1E|3|1F|5|6|7|2C|8|@]|9|@$A|2D|B|2E|1|2F]]|C|$]]|$1|1G|3|-4|5|6|7|2G|8|@]|9|@]|C|$]]]|1H|$1I|$5|1J|1K|1L|C|$1M|1N]]|1O|$5|1J|1K|1L|C|$1M|1P]]]]

<a href="https://github.com/vladmihalcea/flexy-pool" rel="nofollow noreferrer">FlexyPool</a> is a data source proxy offering better monitoring and failover for almost all known connection pools:

<ul>
<li>Apache DBCP</li>
<li>Apache DBCP2</li>
<li>C3P0</li>
<li>BoneCP</li>
<li>HikariCP</li>
<li>Tomcat CP</li>
<li>Vibur DBCP</li>
<li>Bitronix Transaction Manager</li>
<li>Atomikos TransactionsEssentials</li>
</ul>

It allows you monitor the following metrics:

<ul>
<li>concurrent connections histogram</li>
<li>concurrent connection requests histogram</li>
<li>data source connection acquiring time histogram</li>
<li>connection lease time histogram</li>
<li>maximum pool size histogram</li>
<li>total connection acquiring time histogram</li>
<li>overflow pool size histogram</li>
<li>retries attempts histogram</li>
</ul>

This way you can adjust the pool size so that it can accommodate as many application nodes as possible while protecting you from some <a href="http://vladmihalcea.com/the-simple-scalability-equation/" rel="nofollow noreferrer">unexpected traffic spikes</a>.

blocks|key|2207249|text|我发现，当使用JConsole时，正如其他答案所建议的那样，通过JMX连接到JBoss+(5.2)时，连接池的MBeans是不可见的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2207250|相反，我使用了内置的JMXConsole，通常可以在：http://localhost:8080/jmx-console上使用--您可能需要更改部署的主机名和端口。|2207251|如果正在运行，您将看到用户名和密码提示。|2207252|默认用户名/密码是：admin/admin|2207253|我第一次尝试时，什么也没发生，我不得不更新文件:+server/default/conf/props/jmx-console-users.properties并取消第2行的注释：|2207254|#+A+sample+users.properties+file+for+use+with+the+UsersRolesLoginModule
admin=admin|code-block|syntax|javascript|2207255|一旦完成，我就可以登录了。在ObjectName+Filter输入：jboss.jca:*时，我随后选择了适当的连接池链接，例如：name=DefaultDS，，它显示了所有连接池信息，例如AvailableConnectionCount、InUseConnectionCount等。|2207256|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.jboss.org/wiki/JMXConsole|1|http://localhost:8080/jmx-console^0|7|8|0|A|A|0|R|X|1|0|0|A|B|0|0|0|E|H|Y|B|1T|F|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]|$9|1B|A|1C|1|1D]]|E|$]]|$1|H|3|I|5|6|7|1E|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1I|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1J|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|1K|8|@$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1R|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]]]

I found that when using JConsole as suggested in other answers to connect to JBoss (5.2) via JMX the MBeans for the Connection Pooling were not visible.

Instead I used the built in <a href="https://developer.jboss.org/wiki/JMXConsole" rel="nofollow" title="JMXConsole">JMXConsole</a> typically available at: <a href="http://localhost:8080/jmx-console" rel="nofollow">http://localhost:8080/jmx-console</a> - you may have to change the hostname and port for your deployment.

If this is running you will see a username and password prompt. 
The default username/password is: admin/admin 
I found the first time I tried this, nothing happened, I had to update the file: server/default/conf/props/jmx-console-users.properties and uncomment the 2nd line: 

<pre><code># A sample users.properties file for use with the UsersRolesLoginModule
admin=admin
</code></pre>

Once this was done I could login. At that point in the ObjectName Filter I entered: jboss.jca:* I then selected the appropriate connection pool link for example: name=DefaultDS,service=ManagedConnectionPool which shows all the connection pool information, e.g. AvailableConnectionCount, InUseConnectionCount etc.

I need an insight on monitoring connection pool in my web application. 
The technical specifications about the application is mentioned below:

<ol>
<li>Application Server - JBoss Application Server </li>
<li>Database - Oracle 10g </li>
<li>Back-end - Hibernate </li>
</ol>

I need to know that what are the different ways of monitoring connection pool and how we can do that. Whether through Hibernate or through JBoss or anyother way?
Please suggest me the right way to do that.

Connection Pool Monitoring

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我需要一个在我的web应用程序监控连接池的洞察力。有关该应用程序的技术规格如下：应用服务器- JBoss应用服务器数据库- Oracle 10g后端Hibernate我需要知道监视连接池的不同方式是什么，以及我们如何做到这一点。不管是通过Hibernate还是通过JBoss还是其他方式？请给我建议正确的方法。

问连接池监控
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问连接池监控EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问连接池监控
EN