Any 1.5.x release is just a maintenance release at this point for users who
may have already deployed 1.5.x already and want to stay there to avoid any
potential disruption a move to 2.x might cause.
The 2.x releases are the current latest and greatest. They have all the
latest features and bug f
The ActiveMQ Artemis download page lists 2 versions of current releases as
below
- ActiveMQ Artemis 2.4.0
- ActiveMQ Artemis 1.5.5
What are the differences between the 2 releases and are their
guidelines/recommendations for choosing one over the other?
Thanks.
--
Sent from: http://activemq.228
Joachim, would you mind submitting a bug report in JIRA for this issue?
On Jan 4, 2018 7:05 AM, "Gary Tully" wrote:
> that looks like a bug, the default configuration should be consistent
> across the start scripts
>
> On Wed, 3 Jan 2018 at 13:41 alprausch77 wrote:
>
> > Hello.
> >
> > The docu
> Does i need to have any change in address settings for the messages to
have faster process of acknowledgement.
How quickly messages are acknowledged is largely dependent on the your
consumers. There's not much which can be done on the broker to speed
acknowledgement.
> yes, i have configured w
1. I have been facing the paging issue earlier with this configuration
-1
104857600
Most of the messages goes into paging with this configuration.
2 .I have overcome the paging issue by changing the address setting
configuration with
104857600
10485760
1073741824
> I have been facing issues with paging earlier, by changing the
configuration with max-size-bytes to 100mb and page-size-bytes to 10mb and
global max-size-bytes to 1 gig.
Are you saying that you have overcome the issue with paging by changing
these settings? Please clarify.
> Still there is no
Thanks Justin for the response. But please correct me if i am wrong, I added
the following to management.xml file
I put in the queue as DLQ and access method as anything and assigned no
roles to it. Is this the right way to do it?
If not could you please guide me the right way.
Hi,
i have been using Apache-artemis 1.5.3 version with cluster connectivity on
AWS instances.
I have been facing issues with paging earlier, by changing the configuration
with max-size-bytes to 100mb and page-size-bytes to 10mb and global
max-size-bytes to 1 gig.
>Still there is no stability b
> We are experiencing intermittent connectivity issues with Artemis server.
Can you be any more specific about this? Are you seeing general slowness
or particular errors?
> Our consumer is Informatica and the Informatica workflow will run every
minute and pickup only one message. So more message
that looks like a bug, the default configuration should be consistent
across the start scripts
On Wed, 3 Jan 2018 at 13:41 alprausch77 wrote:
> Hello.
>
> The documentation
> (
> http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html
> )
> states that the D
10 matches
Mail list logo
