I think he was referring to your clients which could be adjusted to pool
a small amount of connections, rather than opening many.
You obviously can't control this from the server-side. Still its very
uncommon to really need 1000 connections at the same time, it generally
suggests your clients open way to many connections. Or they're opened
and closed very fast, so the server can't keep up in its default
configuration and has many "waiting to be closed connections".
For each connection to your server there is a single file pointer. You
can, amongsts others, use 'lsof' to see how many for your java-proces
(see man lsof for usage examples).
You can also see connections in CLOSE_WAIT using lsof.
If you really have that many clients, there isn't much you can do.
You're limited to adjusting the server in such a way it can hold more
file pointers (i.e. use ulimit) or change your server-architecture to
have more servers (with that many clients, some redundancy is a good
thing anyway).
Best regards,
Arjen
On 16-1-2014 9:54 Michael Priess wrote:
Hi,
correct me if I'm wrong but if I listen to a topic the connection must be
always open? In my thinking a PooledConnectionFactory make only sense if
I'm sending a lot of messages to the broker.
BTW. know someone the exactly number of file handles which are open per
connection on the server?
2014/1/15 Jose María Zaragoza <demablo...@gmail.com>
2014/1/13 Michael Priess <digitalover...@googlemail.com>:
Is there a way how to find which client open so much connections? Is
there
a reason why ActiveMQ doesn't close this connections?
Any idea how to debug such an issue?
Why dont use PooledConnectionFactory?
Regards
