Re: Static network of brokers with not all brokers running (expected)

2018-01-31 Thread pypen
Thank Tim. I thought maybe the way I phrased the questions came across offensive or something. And thanks for the clarification about the polling vs. broadcasting. I will have to see if we can maybe enable multicast. I don't see the "backup" property on the discovery transport though and I am not

Re: Static network of brokers with not all brokers running (expected)

2018-01-30 Thread pypen
Bad day? Relax Tim. Not trying to offend anyone here. It's not about me not wanting to tweak the log4j. I just didn't want to suppress the TransportDisposedIOException (or DemandForwardingBridgeSupport) if it happens for a different reason. And I was not clear enough about the previous versions: I

Re: Static network of brokers with not all brokers running (expected)

2018-01-30 Thread pypen
Figured out the problem with 2. The client had a network timeout of 30 seconds. Every producer and consumer creates its own connection and session and that caused the problems. Reducing the timeout solved issue 2. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Static network of brokers with not all brokers running (expected)

2018-01-30 Thread pypen
Hi, I have a network of 4 brokers, statically configured (). Each broker has a list if IPs, excluding its own. It is expected that not all brokers are running at the same time (they can, but don't have to). I have (java) clients that run on the same machines as the brokers and connect to their loca

Re: Message redelivery when producer broker killed (without persistence)

2017-10-23 Thread pypen
We actually use more than 2 nodes, but still an even amount. About the prime-time ready: A consultant told me that some functionality was missing. Maybe I will look into Artemis. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Message redelivery when producer broker killed (without persistence)

2017-10-23 Thread pypen
:) You are right. And you are wrong. I DON'T want persistent messaging via KhahaDB (or jdbc). I don't want to introduce a database, a NAS or shared folders (I'm on windows). I DO want in memory behavior similar to it, where two brokers share their messages (in memory) so that if both brokers die, m

Re: Message redelivery when producer broker killed (without persistence)

2017-10-17 Thread pypen
Thanks guys. I am a little hesitant since I heard that artemis is not really prime-time ready yet. But I might give it a shot. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Message redelivery when producer broker killed (without persistence)

2017-10-13 Thread pypen
Thank you both for your answers. Yes, Justin, that's what I meant (non-persistent messaging). I guess, I will have to look into different solutions. Is it for example possible to force messages to be always sent to a local consumer, if one exists, otherwise to a remote consumer (if one exists and

Message redelivery when producer broker killed (without persistence)

2017-10-12 Thread pypen
Hi, I am trying to solve a problem and I am wondering if Virtual Topics provide a solution for the problem. I have 2 brokers in a network of brokers. Broker A has a producer to VirtualTopic.Test and a local consumer Consumer.A.VirtualTopic.Test (lets call it consumer A). Broker B has a local consum