Re: Runaway producer: Proper way to clean up a topic?

Sounds like a very interesting usecase. A network of brokers might help - depending on more of the specifics; for example, depending on the cause of lost connection to the broker, the amount of time for the client to reconnect can vary. I can think of other approaches to achieve what you've descr

Re: Runaway producer: Proper way to clean up a topic?

I have not reproduced the issue that I regionally experienced sadly. If I do, I will attempt to capture it in a unit test as you suggest. Interesting pont about the short timeout; if we indeed need such a short timeout then persistence is pointless indeed. My requirements are atypical it seems:

Re: Runaway producer: Proper way to clean up a topic?

Thanks for the advice. I do not really want to blindly delete all messages at startup, though; just the expired ones. -- View this message in context: http://activemq.2283324.n4.nabble.com/Runaway-producer-Proper-way-to-clean-up-a-topic-tp4677644p4677672.html Sent from the ActiveMQ - User mail

Re: NMS SSL Client Settings

Correct - accepting invalid certs is not secure. Your client will connect to any broker using ssl regardless of cert validity in that case. Note I sm being a little vague because I am not certain of the NMS settings. You want the ssl url without the transport.acceptInvalidBrokerCert=true setti

Re: NMS SSL Client Settings

Should this work? (removing the transport) with a valid certificate? From: ssl://localhost:61617?transport.acceptInvalidBrokerCert=true TO: ssl://localhost:61617 I'm concerned that the transport.acceptInvalidBrokerCert=true is not "secure" Thanks -- View this message in context: http://acti

Re: rebalanceClusterClients , failover and transactions

Try this on the broker transport conntector. updateClusterFilter=nosuchthing Let me know if it does not work and I will double-check the setting. Sent from my iPhone > On Feb 8, 2014, at 10:08 AM, "Enrico Olivelli [via ActiveMQ]" > wrote: > > Hi, > I'm facing a problem in my system due t

Re: NMS SSL Client Settings

Are you looking for howto info? To make server cert checking work, the client must trust the server's cert. That means either get a server (broker) cert signed by a known trusted Certificate Authority (CA) or add the CA that did sign the cert to the client's trusted CA list. Sent from my iPho

NMS SSL Client Settings

>From article by Tim Bish I was able to use the following client config settings: ssl://localhost:61617?transport.acceptInvalidBrokerCert=true Currently it won't work without the transport setting.. I need to make this more secure (i.e. not accept invalid Broker) Thanks -- View this message i

Re: Urgent - Broker version 5.8.0 doesn't work with multicast

Also make sure bridges are setup in both directions. Sent from my iPhone > On Feb 9, 2014, at 8:56 AM, "1gnition [via ActiveMQ]" > wrote: > > Hello, > > This is very urgent. I'd appreciate if you can help me quickly. > > I have a configuration of two machines with a single broker on each

Re: Urgent - Broker version 5.8.0 doesn't work with multicast

Check the bridges using the webconsole and jmx. It sounds like they are just not there. Perhaps turning up logging on the networking code will help to. org.apache.activemq.network=DEBUG That's from memory, so it may need checking. Sent from my iPhone > On Feb 9, 2014, at 8:56 AM, "1gnition

Urgent - Broker version 5.8.0 doesn't work with multicast

Hello, This is very urgent. I'd appreciate if you can help me quickly. I have a configuration of two machines with a single broker on each one. The brokers are connected in a network using multicast. This is the relevant section of the activemq.xml: I run a consumer on each of the two machines