RE: JMS messages replication

2018-01-26 Thread Tim Bain
On Jan 26, 2018 2:42 PM, "COURTAULT Francois" < francois.courta...@gemalto.com> wrote: Hello, @Tim: should I consider that no solution to my problem exists using ActiveMQ 5.x ? If the answer is yes at the previous question, does a solution to my issue exists in Artemis ? If yes cou

RE: JMS messages replication

2018-01-26 Thread Tim Bain
Each message exists on one and only one node at a time in a network of brokers, and is forwarded from broker to broker based on demand. If you're looking for replication, for example to protect you from messages being unavailable if a broker goes offline, a NoB won't give you that. And replicated

Re: partially durable queue?

2018-01-26 Thread Tim Bain
It'll only throw away unconsumed messages. So a single event like a whole-house power failure won't lose many messages, because the consumer will probably be up to date and there won't be any messages on the broker. You're only at risk of data loss if there are multiple failures separated by a sign

Hawtio service destroyed on slave after master server restart

2018-01-26 Thread ravirake
Hi, We have master and slave failover configuration. So when master goes down the slave pick up but In a particular case when master is back online after the failure, the slave hands over and in this case hawtio service is being destroyed as seen in the logs below. Therefore the hawtio console doe

Hawtio service destroyed on slave after master server restart

2018-01-26 Thread ravirake
Hi, We have master and slave failover configuration. So when master goes down the slave pick up but In a particular case when master is back online after the failure, the slave hands over and in this case hawtio service is being destroyed as seen in the logs below. Therefore the hawtio console doe

Hawtio service destroyed on slave after master server restart

2018-01-26 Thread ravirake
Hi, We have master and slave failover configuration. So when master goes down the slave pick up but In a particular case when master is back online after the failure, the slave hands over and in this case hawtio service is being destroyed as seen in the logs below. Therefore the hawtio console doe

RE: JMS messages replication

2018-01-26 Thread COURTAULT Francois
Hello, @Tim: should I consider that no solution to my problem exists using ActiveMQ 5.x ? If the answer is yes at the previous question, does a solution to my issue exists in Artemis ? If yes could you please provide me some information (pointer, explanations, ...) ?

Re: partially durable queue?

2018-01-26 Thread Clebert Suconic
It will work with artemis. It will start to steam to disk when beyond configured limit. On Fri, Jan 26, 2018 at 2:12 PM Noel Grandin wrote: > On 26 January 2018 at 20:58, Clebert Suconic > wrote: > > > With artemis you can simply disable syncs on producer and you would get > > similar performan

Re: partially durable queue?

2018-01-26 Thread Noel Grandin
On 26 January 2018 at 20:58, Clebert Suconic wrote: > With artemis you can simply disable syncs on producer and you would get > similar performance numbers. Usually people turn of persistence to gain > Ah, it's not perf I'm after, think of this as a kind of IOT/sensor device, I want to preserve

Re: partially durable queue?

2018-01-26 Thread Clebert Suconic
With artemis you can simply disable syncs on producer and you would get similar performance numbers. Usually people turn of persistence to gain some performance. With artemis you can just always persist and increase perf by batching multiple writes. SyncOnDurable=false on the connection factory.

RE: JMS messages replication

2018-01-26 Thread Jonathan Gallimore
Hey Francois, I have successfully managed to get TomEE going with Artemis, but it isn't very user friendly, and I'm sure the integration could be better. If you're up for some hacking on that, let me know and I'd be happy to give you some pointers. Cheers Jon On 26 Jan 2018 17:29, "COURTAULT F

Re: partially durable queue?

2018-01-26 Thread Noel Grandin
On Fri, 26 Jan 2018 at 19:22, Tim Bain wrote: > > 5.x can also do in-memory-till-full-then-spool-to-disk when using > non-persistent messages (which go to the memory store and then to the temp > store if the memory store is full). > That’s useful info thanks. But non persistent means that the br

RE: JMS messages replication

2018-01-26 Thread COURTAULT Francois
Hello, As we are using TomEE, I think ActiveMQ 5.x is quite mandatory. I don't know so much about the TomEE roadmap but, for the TomEE Java EE 8 compliant version, they will perhaps use Artemis BTW, using ActiveMQ 5.x and digging further in the ActiveMQ documentation, could the Networks of

Re: partially durable queue?

2018-01-26 Thread Tim Bain
This mailing list is for the two ActiveMQ forks: 5.x and Artemis (which is expected to become 6.x). RabbitMQ and all other message brokers are unrelated products. 5.x can also do in-memory-till-full-then-spool-to-disk when using non-persistent messages (which go to the memory store and then to the

Re: JMS messages replication

2018-01-26 Thread Tim Bain
Have you considered using Artemis rather than ActiveMQ 5.x? Tim On Jan 26, 2018 10:02 AM, "COURTAULT Francois" < francois.courta...@gemalto.com> wrote: > Hello, > > I have looked at Replicated LevelDB Store page on ActiveMQ web site, even > if LevelDB store has been replaced by KahaDB, in order

RE: JMS messages replication

2018-01-26 Thread COURTAULT Francois
Hello, Digging further in the ActiveMQ documentation, could the Networks of Brokers a solution ? Best Regards. -Original Message- From: COURTAULT Francois [mailto:francois.courta...@gemalto.com] Sent: vendredi 26 janvier 2018 18:02 To: users@activemq.apache.org Subject: [+SPAM+]: JMS me

JMS messages replication

2018-01-26 Thread COURTAULT Francois
Hello, I have looked at Replicated LevelDB Store page on ActiveMQ web site, even if LevelDB store has been replaced by KahaDB, in order to see if it can solve the technical issue I have. But, as far as I have understood this solution won't solve my problem. Let me describe it, in order to reall

Re: partially durable queue?

2018-01-26 Thread Noel Grandin
On Fri, 26 Jan 2018 at 17:59, Justin Bertram wrote: > > If you're asking about ActiveMQ, can you clarify if you're asking about the > 5.x or Artemis broker? > I’ve only just started looking at tech options, so I don’t even know what those are. I assume different forks of active mq?

Re: partially durable queue?

2018-01-26 Thread Clebert Suconic
You can do that with Artemis and Paging.. I'm not sure about Rabbit :) On Fri, Jan 26, 2018 at 10:15 AM, Noel Grandin wrote: > > Hi > > I have a need for a queue that operates purely in-memory until the > consumer(s) can't keep up, and only then starts spooling to disk. > I'm ok with losing some

Re: partially durable queue?

2018-01-26 Thread Justin Bertram
Are you asking about RabbitMQ? If so, the ActiveMQ user list might not be the best place to get answers about RabbitMQ. If you're asking about ActiveMQ, can you clarify if you're asking about the 5.x or Artemis broker? Justin On Fri, Jan 26, 2018 at 9:15 AM, Noel Grandin wrote: > > Hi > > I

partially durable queue?

2018-01-26 Thread Noel Grandin
Hi I have a need for a queue that operates purely in-memory until the consumer(s) can't keep up, and only then starts spooling to disk. I'm ok with losing some messages in the event of a hardware or software crash. Is there such a configuration in RabbitMQ? If not, could one be created with a

Re: [ARTEMIS] Messages with same group-id are received by multiple consumers

2018-01-26 Thread Miroslav Novak
Hi Ognjen, I believe the issue is that messages are sent to Artemis first and then consumers connect, right? In this case first consumer will get all or most of the message groups assigned. Could you try to first connect consumers and then send messages? I think that ActiveMQ 5.x had better lo

[ARTEMIS] Messages with same group-id are received by multiple consumers

2018-01-26 Thread Ogi
I have two deployed apps, one on my local machine and one on the server and both apps are communicating through the same Artemis client which is installed on the server. Artemis version is 1.5.5. Problem occurs when I execute simple test that sends 1000 messages divided into multiple groups, in thi

Re: [ARTEMIS] Server doesn't start if JDBC store is used and table NODE_MANAGER_STORE is empty

2018-01-26 Thread Francesco Nigro
> BTW: I currenty own the required grants since oracle is running on my own laptop. But I know that this will cause trouble when installing Artemis in our production environment. Probably it could be a latency issue too: there are several configuration properties

Re: Artemis 2.1.0 compatibility with 1.5.x

2018-01-26 Thread hcrobison
We really need the backwards comparability. Please let me know whether and how I can create a jira for this issue. Thanks. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: [ARTEMIS] Server doesn't start if JDBC store is used and table NODE_MANAGER_STORE is empty

2018-01-26 Thread Archibald
And I can see that the broker is holding a lock on that table. So it tries to insert something which fails but does not properly rollback... -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: [ARTEMIS] Server doesn't start if JDBC store is used and table NODE_MANAGER_STORE is empty

2018-01-26 Thread Archibald
Hi Franz, to your questions: 1) Oracle Database 12c Standard Edition Release 12.2.0.1.0 - 64bit Production 2) not more is being written to the log (not even in debug) 3) no I haven't tried the latest master. But since I do not find a related issue in JIRA I assume that it still exist. BTW: I cur

Re: Artemis Connection failure has been detected

2018-01-26 Thread Raul Valdoleiros
Hi, Thanks for your help :) 2018-01-26 9:10 GMT+00:00 Francesco Nigro : > Hi, > > as Miroslav said, that warnings aren't a sign of any lost message, but I > agree that they are somehow scary :) > Maybe could worth to lower the log level to INFO. > > Thanks, > Franz > > > Il giorno ven 26 gen 201

Re: [ARTEMIS] Server doesn't start if JDBC store is used and table NODE_MANAGER_STORE is empty

2018-01-26 Thread Francesco Nigro
I understand; to help i need a couple of other things too: 1) which DB vendor has been used 2) a more verbose log of the error, if possible 3) have you tried the last master too? All these 3 questions obviously will fall if you could raise the privileges of the DB user :) Cheers, Franz Il gi

Re: [ARTEMIS] Server doesn't start if JDBC store is used and table NODE_MANAGER_STORE is empty

2018-01-26 Thread Archibald
Thanks Franz, the other tables do work pretty well if they already exist but are empty. It is just the NODE_MANAGE_STORE which somehow "picky"... Br, Archibald -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Security

2018-01-26 Thread Lionel van den Berg
What is recommended to use with ActiveMQ (5.14/5.15) for security? We've started dabling with the authentication, which seems fine, but we would also like to consider encryption. Will we lose the ability to use XML filters if encrypted? Thanks Lionel.

Re: Artemis Connection failure has been detected

2018-01-26 Thread Francesco Nigro
Hi, as Miroslav said, that warnings aren't a sign of any lost message, but I agree that they are somehow scary :) Maybe could worth to lower the log level to INFO. Thanks, Franz Il giorno ven 26 gen 2018 alle ore 09:28 Miroslav Novak ha scritto: > Hi, > > those messages are normal when server

Re: [ARTEMIS] Server doesn't start if JDBC store is used and table NODE_MANAGER_STORE is empty

2018-01-26 Thread Francesco Nigro
Hi! AFAIK that table is part of the effort to provide HA Shared Store feature when a JDBC Journal is configured, hence I suppose that the same issue would be likely to happen for the other JDBC Journal tables as well. The solutions I see are: 1 - have the user granted to create/modify schema in o

[ARTEMIS] Server doesn't start if JDBC store is used and table NODE_MANAGER_STORE is empty

2018-01-26 Thread Archibald
Hi all, 2.4.0 introduced a new table NODE_MANAGER_STORE. This table is being created on startup if it doesn't exist. But if it does exist but is empty server fails to start (seen on a oracle database) with 08:43:20,510 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting

Re: Artemis Connection failure has been detected

2018-01-26 Thread Miroslav Novak
Hi, those messages are normal when server in Artemis cluster is shutdown. You will not loose messages if you start the broker again. Note that messages are usually load-balanced (distributed) to all nodes in cluster in round robin fashion. So shutting down node in cluster (without proper scale