). I expected there
would be concurrent processing of messages, but looking in the
AMQPSessionCallback it uses a OrderedExecutor which implies it is ordered.
Are messages processed sequentially when published to an address? Can it be
configured?
best regards
Magnus
That is a problem
for us!
To sum it up
==
How can I display message content for "large messages" to some extent? I
understand that the console cannot show infinitely large messages, but maybe
up to some limit where it truncates.
Best regards
Magnus Johansson
CMJ Solutions AB
ht be that we
run a single broker in the end (at least to start with).
Thanks for the help!
best regards
Magnus
like the nodes in the cluster to be behind a
load-balancer to be able to scale the cluster seamlessly, but as I understand
it reading the documentation durable consumers need to be aware of the nodes in
the cluster (to solve the above question). Or am I misunderstanding something?
brgds
Magnus
!
Brgds
Magnus Andersson
S4 on Windows so this probably means
that we need to switch to Linux bases servers for Active MQ.
Since changing to Linux means a lot of work we would like to understand our
options before moving on.
Any info in this subject is appreciated!
Regards,
Magnus.
--
View this message in context:
Anyone that can share yajsw config files required to be able to register
ActiveMQ as a windows service under 64-bit windows?
Thanks in advance,
Magnus.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/wrapper-dll-for-64-bit-windows-platform-to-run-activemq
I see that AuthorizationBroker implements SecurityAdminMBean which leads me
to believe that I can administer roles etc. over JMX, is this correct? I am
unable to find anything remotely related to it when using jconsole but on
the other hand I have about 0 experience with JMX :)
If possible, could
If you don't have control over the web service endpoint one option could
be to relay messages using a Camel processor. ServiceMix could also be
an option -
http://www.exforsys.com/tutorials/java-soa/xbean-based-servicemix-http-binding.html
(a few pages in) reports that it can act as both a cons
As long as you do everything within the context of HTTP you will not be able
to keep a persistant connection to the broker. Comet circumvents this by
having long-running connections to the web server but this has never been
something that the protocol should support - realize that for every open
c
10 matches
Mail list logo