Hi,
I use ActiveMQ 5.9.0 on FreeBSD with java 1.7.0_25-b15 and native
leveldb (default settings).
Four servers, fully meshed network of brokers, only two get effective load.
I publish from a small number of servers (around 30) to a virtual topic,
then consume the aggregated messages from one
rdware.
On Wed, Nov 6, 2013 at 3:37 AM, Attila Nagy wrote:
Hi,
AMQ 5.9.0, FreeBSD 9/amd64, openjdk version "1.7.0_25".
Publishing to a virtual topic, with one durable subscriber disconnected, 1
million small (160-300 bytes payload) messages, with some headers, then
consuming with on
Hi,
AMQ 5.9.0, FreeBSD 9/amd64, openjdk version "1.7.0_25".
Publishing to a virtual topic, with one durable subscriber disconnected,
1 million small (160-300 bytes payload) messages, with some headers,
then consuming with one client.
The queue has a 10MB memory limit, store cursor.
With kahad
13 21:58, Attila Nagy wrote:
Sure (python):
conn.send(data,
destination='/topic/VirtualTopic.radius',
headers={
'content-length':reclen,
'persistent':'true&#
to a topic with
different durable subscribers with selectors.
That's what I would like to know. :)
On 11/04/2013 09:31 PM, Johan Edstrom wrote:
Are you marking the message as persistent?
On Nov 4, 2013, at 1:08 PM, Attila Nagy wrote:
Even on activemq.org you can find the terms durab
so how is a queue durable? Perhaps you mean a queue with
persistent messages on it?
To have a durable consumer to a topic you need to create a durable
subscription, either through the console or by sending a client-id and
activemq.subscriptionName headers when connecting.
Attila Nagy writes:
Hi,
Hi,
I'm struggling with AMQ 5.9.0 to achieve my goals: durable virtual
topics with selectors on STOMP, with a network of four brokers
(connected with SSL connectors, with ACLs and certificate
authentication/authorization both on client and server side).
In english: I want to publish messages
atic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Thu, Oct 31, 2013 at 8:57 AM, Attila Nagy wrote:
Hi,
I must be overlooking something really trivial, because I can't log in on
the new (hawtio) console on a fresh installed activemq 5.9.0 with the
default configs.
The old conso
Hi,
I must be overlooking something really trivial, because I can't log in
on the new (hawtio) console on a fresh installed activemq 5.9.0 with the
default configs.
The old console is working nicely with the default admin/admin l/p, but
I can't login in with whatever I think hawtio could use
Hi,
I've the following:
- populateJMSXUserID=true in
- uri="ssl://0.0.0.0:61616?needClientAuth=true"/>
- a network of brokers with four machines (full mesh)
- the clients and brokers authenticate themselves with certificates and
connect with SSL
If I connect with client A (producer) to broke
10 matches
Mail list logo
