But the real problem is that a client in a tcp connection doesn't properly
(usually not at all) close down the connection.
If you don't have control over clients (eg in a public network), lowering the
time_wait interval is the only solution, but otherwise, look for missing
close() calls at the
Check out http://www.unix.com/solaris/12257-time-wait-interval.html
On Tue, Apr 30, 2013 at 12:05 AM, lacigas wrote:
> Sorry if this has been asked before, I have seen several posts, but none of
> them helped.
>
> I'm running AMQ 5.8 on linux 64bit. Camel routes generated by Talend ESB.
>
> As
Hi forum,
I have upgraded AMQ-CPP consumer from Ver 2.2.2 to 3.5.0 on Windows.
Everything worked fine prior to the upgrade.
Now, when the consumer is launched - it is able to draw all *existing
*messages in queue.
However, *new *messages are not delivered.
I can see it in JConsole that queueSize
Hello Ladies and Gentlemen,
Having a problem using the failover protocol to connect to another broker
when the connection to the current broker dies. The client is taking a long
time about 1min and 15 seconds to failover to another known broker. Is
there are configuration options i can use to imp
Sorry if this has been asked before, I have seen several posts, but none of
them helped.
I'm running AMQ 5.8 on linux 64bit. Camel routes generated by Talend ESB.
As a test I have one pooled connection factory (default values) and one jms
consumer.
The jms consumer is configured with cacheLevelNa
Updated...
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-CPP-consumer-exitMonitor-throws-Thread-is-not-the-owner-of-this-monitor-tp4666392p4666515.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Your solution seems like Virtual Topic and you may take a look at
http://activemq.apache.org/virtual-destinations.html
With Virtual Topic you do not need move events from the topic to the
subscription queues manually.
At 2013-05-01 00:38:40,deepak_a wrote:
>All,
>
>For a Topic with multiple c
