websphere 7 JMS 连接池；不断成长
我正在运行 websphere 7 (fixpack 7.0.0.1.9) & websphere-mq7（修复包 7.0.1.5）。
我已将我的工厂（FACTORY 和 MQ_FACTORY）的连接池设置为...
FACTORY
Connection timeout : 180 seconds
Maximum connections : 10 connections
Minimum connections : 1 connections
Reap time : 180 seconds
Unused timeout 1800 seconds
Aged timeout 0 seconds
Purge policy :EntirePool
MQ_FACTORY
Connection timeout : 180 seconds
Maximum connections : 10 connections
Minimum connections : 1 connections
Reap time : 180 seconds
Unused timeout 1800 seconds
Aged timeout 0 seconds
Purge policy :EntirePool
PMI 工具显示以下内容...
JCA Connection Pools...
CreateCount : 27.0
CloseCount : 4.0
PoolSize : 23.0
JMS Connection Factories
CreateCount : 14.0
CloseCount : 2.0
PoolSize : 12.0
Websphere MQ JMS Provider
CreateCount : 13.0
CloseCount : 2.0
PoolSize : 11.0
我的连接池如何大于池大小？！？！？！ 为什么泳池尺寸仍然很大？？？
我发送的消息越多，它就越大。
例如，我刚刚发送了更多消息，现在我的尺寸是...
JCA Connection Pools...
CreateCount : 35.0
CloseCount : 0.0
PoolSize : 35.0
FreePoolSize: 14.0
JMS Connection Factories
CreateCount : 15.0
CloseCount : 0.0
PoolSize : 15.0
FreePoolSize: 0.0
Websphere MQ JMS Provider
CreateCount : 20.0
CloseCount : 0.0
PoolSize : 20.0
FreePoolSize: 14.0
这是工厂的统计数据...
JMS$MQ_FACTORY
CreateCount : 6.0
CloseCount : 0.0
PoolSize : 6.0
FreePoolSize: 5.0
JMS$FACTORY
CreateCount : 14.0
CloseCount : 4.0
PoolSize : 10.0
FreePoolSize: 5.0
jms/MQ_FACTORY
CreateCount : 6.0
CloseCount : 0.0
PoolSize : 6.0
FreePoolSize: 0.0
jms/FACTORY
CreateCount : 9.0
CloseCount : 0.0
PoolSize : 9.0
FreePoolSize: 0.0
有人有任何想法吗？
谢谢 杰夫·波特
I'm running websphere 7 (fixpack 7.0.0.1.9) & websphere-mq7 (fixpack 7.0.1.5).
I've set the connection pool for both my FACTORIES (FACTORY and MQ_FACTORY) to...
FACTORY
Connection timeout : 180 seconds
Maximum connections : 10 connections
Minimum connections : 1 connections
Reap time : 180 seconds
Unused timeout 1800 seconds
Aged timeout 0 seconds
Purge policy :EntirePool
MQ_FACTORY
Connection timeout : 180 seconds
Maximum connections : 10 connections
Minimum connections : 1 connections
Reap time : 180 seconds
Unused timeout 1800 seconds
Aged timeout 0 seconds
Purge policy :EntirePool
The PMI tool shows the following...
JCA Connection Pools...
CreateCount : 27.0
CloseCount : 4.0
PoolSize : 23.0
JMS Connection Factories
CreateCount : 14.0
CloseCount : 2.0
PoolSize : 12.0
Websphere MQ JMS Provider
CreateCount : 13.0
CloseCount : 2.0
PoolSize : 11.0
HOW is my connection pool bigger than the pool size?!?!?!
HOW come the pool size remains high???
The more messages I send in, the bigger it gets.
So for example, I've just sent in a load more messages and now my sizes are...
JCA Connection Pools...
CreateCount : 35.0
CloseCount : 0.0
PoolSize : 35.0
FreePoolSize: 14.0
JMS Connection Factories
CreateCount : 15.0
CloseCount : 0.0
PoolSize : 15.0
FreePoolSize: 0.0
Websphere MQ JMS Provider
CreateCount : 20.0
CloseCount : 0.0
PoolSize : 20.0
FreePoolSize: 14.0
Here are the stats for the factories...
JMS$MQ_FACTORY
CreateCount : 6.0
CloseCount : 0.0
PoolSize : 6.0
FreePoolSize: 5.0
JMS$FACTORY
CreateCount : 14.0
CloseCount : 4.0
PoolSize : 10.0
FreePoolSize: 5.0
jms/MQ_FACTORY
CreateCount : 6.0
CloseCount : 0.0
PoolSize : 6.0
FreePoolSize: 0.0
jms/FACTORY
CreateCount : 9.0
CloseCount : 0.0
PoolSize : 9.0
FreePoolSize: 0.0
Does anyone have any ideas?
Thanks
Jeff Porter
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
“JCA 连接池”表示“JMS 连接工厂”和“WebSphere MQ JMS 提供程序”的总数。 （请注意，这两个单独统计数据的总和等于“JCA 连接池”中的统计数据。）
此外，连接池设置适用于每个配置的连接工厂以及“JMS 连接工厂”和“WebSphere MQ JMS Provider”统计数据表示所有子模块（即所有连接工厂）的总和。鉴于您说过“我已经为我的工厂设置了连接池”（强调我的），我假设您实际上有两个不同的连接工厂，这可以解释为什么这些值更高比每个单独连接工厂的最大连接数。
如果您在 ISC 中使用性能查看器，您应该能够展开每个模块以查看各个子模块。如果您通过
wsadmin检查统计信息，则需要获取 JCA 模块的子统计信息 (getSubStats)。The "JCA Connection Pools" represents the totals for the "JMS Connection Factories" and "WebSphere MQ JMS Provider." (Notice that the sum of these two individual stats equals the stats in the "JCA Connection Pools.")
Also, the connection pooling settings are for each configured connection factory, and the "JMS Connection Factories" and "WebSphere MQ JMS Provider" statistics represent the sum for all submodules (i.e. for all connection factories). Given that you stated "I've set the connection pool for both my FACTORY" (emphasis mine), I'm assuming that you actually have two different connection factories, which could explain why these values are higher than each individual connection factory's max connections.
If you are using the Performance Viewer in the ISC, you should be able to expand each module to view the individual submodules. If you are checking the stats through
wsadmin, you will need to grab the substats (getSubStats) for the JCA modules.请检查您的代码，如果您已关闭 QueueConnection，以防您打开。请确保在任何情况下连接都是关闭的，无论连接创建和启动后是否还有任何异常。
please check in your code, if you had closed the QueueConnection, incase you open. Please make sure the connection is closed in any scenario, no matter if there is also any exception after the connection is created and started.