Hello,
Any idea? I can't stop the application cleanly if QPID keep retrying the
connection indefinitely (its connection thread remains alive).
Thanks
Marco
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Java-client-Cannot-stop-during-failover-tp7595882p7595930.html
Sent
I'm surprised that calling Connection.stop() doesn't abort failover.
Nevertheless, to abort failover I believe you can just return false from
org.apache.qpid.jms.ConnectionListener.preFailover(). I guess your
implementation would return false if the application was trying to shut
down.
I don't
Connection.stop() and close() don't seem to help.
Returning false from preFailover() is not a solution because that is invoked
once before the start of a failover, but my problem is when the failover is
already started when you try to shut down.
I'm starting to think I'll have to give up with
Ken,
It works for me.
Bill
On Thu, Jul 25, 2013 at 6:43 PM, Ken Giusti kgiu...@redhat.com wrote:
Hi Bill,
Care to try out a patch for me?
https://issues.apache.org/jira/browse/QPID-5019
If this works, I'll try to get Justin to approve it for 0.24, that way it
will be in the next
Great, I'll push that to trunk, and if nobody's CI complains, ask Justin to
include it in 0.24.
thanks for testing it.
-K
- Original Message -
From: Bill Freeman ke1g...@gmail.com
To: users users@qpid.apache.org
Sent: Friday, July 26, 2013 11:07:09 AM
Subject: Re: Telling v1
We are trying to run the Qpid C++ broker on Fedora 18, but when we increase
the number of connections to Qpid topics we get a tremendous number of
these messages in the log:
Jul 26 12:09:36 jackson qpidd[31823]: 2013-07-26 18:09:36 [System] error
Could not accept socket: Too many open files
I'm certainly not sure about your case, but here are some points from our
knowledge:
Make sure that /proc/sys/fs/file-max (total number of files that can be opened
by all users) is large enough. To check, you can: cat /proc/sys/fs/file-max
If you need to increase it, modify /etc/sysctl.conf and
