Hi Dejan,
Dejan Bosanac wrote:
>
> it seems like you're closing all that is there to close, but maybe missing
> to close it in some situations. There isn't much we can do, until we have
> a
> reproducible "test case", so if you can just strip down your app only on
> messaging related part and t
Hi,
it seems like you're closing all that is there to close, but maybe missing
to close it in some situations. There isn't much we can do, until we have a
reproducible "test case", so if you can just strip down your app only on
messaging related part and that, it would be great.
Cheers
--
Dejan B
Hi Dejan,
I'll post the problem on Jira, but I don't have any test case. The web
application is really big, so I don't think I'm able to create one.
Could you give some hints about what I should close on the message consumer
side? Or should I close also something in the message listener part?
R
Hi,
we didn't here about this problem before. Can you raise a Jira for it, and
preferably provide a test case?
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
Hello to everyone,
I'm using Apache 2, Tomcat 6 and ActiveMQ 5.2.0. I'm using request-reply
messages mode. ActiveMQ works well except that it doesn't close the
ESTABLISHED connections. So, after a couple of hours running, there are not
available file descriptors left to accept new connections due
