>
> As part of the roadmap discussion, we must also decide if one of the goals
> for Artemis is still to be a drop-in replacement for ActiveMQ. I know that
> at one time this was the goal, i.e., allow current ActiveMQ users to drop
> in Artemis and have everything just continue to work. Is there st
Artemis 2.9.0. (as well as 2.6.3 where I first was testing).
I've got a working master / backup cluster, using static connectors. My
server broker.xml has these components:
tcp://activemqmaster:61616
tcp://activemqbackup:61616
tcp://0.0.0.0:61616?tcpSendBufferSi
Thanks Tim. It solved the issue we were facing.
Best
Sumit
On Thu, Jul 11, 2019 at 6:05 PM Tim Bain wrote:
> To me this sounds like https://activemq.apache.org/jmstemplate-gotchas
> rather than AMQ-6700. If you're not using a pooled connection factory, you
> definitely need to.
>
> Tim
>
> On W
Dev list got dropped so adding back in (really this probably only belongs
the dev list anyways)
On Thu, Jul 11, 2019 at 12:08 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> Many of those pull requests are years old. Furthermore no one is saying
> there is no interest in a pro
Many of those pull requests are years old. Furthermore no one is saying
there is no interest in a project. But there is a huge difference from
supporting 5.x in terms of bug fixes and small features than talking about
doing something like adding new protocols or JMS 2.0 support. For example
the
Can you provide steps to reproduce this behavior?
Justin
On Thu, Jul 11, 2019 at 10:55 AM rakesh wrote:
> @nigro_franz, I still face the problem with 2.9.0. I'm using stomp protocol
> and have set the min-large-message-size to 430080 and journal-buffer-size
> remain default (490 KiB). The mess
@nigro_franz, I still face the problem with 2.9.0. I'm using stomp protocol
and have set the min-large-message-size to 430080 and journal-buffer-size
remain default (490 KiB). The messages are published to a topic having large
backlog and there also exists a route or a divert from this topic to
ano
(Reposting in this roadmap discussion)
I agree that we must define a clear roadmap. We should create a new wiki
page for an overall ActiveMQ project roadmap that includes info for all the
ActiveMQ components (ActiveMQ, ActiveMQ Artemis, ActiveMQ NMS and ActiveMQ
CMS). There is already an ActiveMQ
> despite the documentation I managed...
Is there something wrong with the documentation? If so, please elaborate so
it can get fixed.
> But I can't find out how to configure artemis-rest to use a truststore
when pushing to my REST service.
I don't see any way to set a truststore specifically fo
I'm curious, why would you use the REST API from a Java client rather than
using the Java-native JMS API, which doesn't have edge cases such as the
need to keep the connection alive and the challenges with messages getting
stranded in prefetch buffers?
Tim
On Wed, Jul 10, 2019, 10:27 AM Luigi Sua
To me this sounds like https://activemq.apache.org/jmstemplate-gotchas
rather than AMQ-6700. If you're not using a pooled connection factory, you
definitely need to.
Tim
On Wed, Jul 10, 2019, 9:05 AM Sumit Bhardwaj
wrote:
> Hi,
>
> We are using ActiveMQ version 5.15.8, We are connecting to it u
Its about having clear direction as a project. Im not saying it has to be
artemis im not saying it has to be classic
But there does have to be a single and very clear direction so end users have a
clear understanding in the long term direction.
Having ever changing direction is worse tha
12 matches
Mail list logo
