Hey all,
today I started trying out the websockets transport connector for our amq. I
first tried the 5.5.0 version, which gave me some null pointers when I
wanted to connect. I then learned that it may not understand the newest
websocket protocols, so i changed to the 5.6.-SNAPSHOT and the errors
The camel-jms component can be used to consume and produce msgs. But Camel
itself does not pool or cache anything. It depends on the underlying Spring
DefaultMessageListenerContainer and connection factory to provide pooling.
The Camel installation has a jms example in examples/camel-example-jms
Sure, take a look at
http://camel.apache.org/activemq.html
especially the part on connection pooling, which essential for efficient
usage of resources.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource
Hi,
Assuming you mean pure master slave setup
(http://activemq.apache.org/pure-master-slave.html)
As long as your slave broker acts as a slave you can't get any advisory nor any
other msgs from it. The slave won't start any transports, it will only connect
to the master broker.
Hope this help
The issue (with sparse selector match) still exists as selectors are
only run on messages in memory. It is possible to configure the
maxPageSize to ensure that all messages live in memory. But for memory
constrained systems, the problem still exists.
Virtual topics can provide an alternative soluti
In that case, the expectation from the broker is that disk io will
result in an IOException and the default behavior in that case is to
stop the broker. Look at:
http://activemq.apache.org/configurable-ioexception-handling.html
On restart, once the partition is available, the broker will recover
(
