Re: [artemis 2.1.0] taking 30+ minutes to boot & failover

2018-07-19 Thread Clebert Suconic
n them. i will also share > the fasthread.io links for each file. (i was struggling getting > fastthread to do a combo report with the threads in the correct order) > > artemis04-20180719-1525 https://goo.gl/d88azU > artemis04-20180719-1530 https://goo.gl/G78qn3 > artemis04-2

Re: ActiveMQ 5.11.0: Out Of Memory, caused by PageFile object tree filling up heap

2018-07-19 Thread Tom Hall
Are you really limiting ram to 300 mb? Why so low if you are on a 8G box? Thanks, Tom > On Jul 19, 2018, at 7:13 AM, art.licis wrote: > > Dear community, > > We've been evaluation AMQ which is based on version 5.11.0. Several tests in > staging environments which would have a big number of

ActiveMQ compatibility

2018-07-19 Thread sfleisher
I have been tasked with researching the compatibility of the following three products: 1) IBM WebSphere MQ for z/OS V8.0.0 (runs on a mainframe) 2) MQ IBM MQ for Linux versions v7508, v8002, v9001 3) IIB - (IBM Integartion Bus)

Re: ActiveMQ compatibility

2018-07-19 Thread Justin Bertram
Can you be more specific? What kind of compatibility are you looking for? Also, are you talking about the ActiveMQ 5.x or Artemis broker? Justin On Thu, Jul 19, 2018 at 10:36 AM, sfleisher wrote: > I have been tasked with researching the compatibility of the following > three > products: >

ActiveMQ 5.11.0: Out Of Memory, caused by PageFile object tree filling up heap

2018-07-19 Thread art.licis
Dear community, We've been evaluation AMQ which is based on version 5.11.0. Several tests in staging environments which would have a big number of producers and consumers ended up with OutOfMemory: GC Overhead Limit exceeded exception. However, it looks like it's just one slow consumer that is

close listener session without rolling back active message

2018-07-19 Thread jahlborn
So, one thing we recently realized about activemq is that if you have a message listener actively processing a message, and you close that session (e.g. the jvm is shutting down), the transaction for the message will end up rolling back (although the listener will continue happily until