It works, after building packages from 1.x branch ( 1.6.0-SNAPSHOT )
I was able to recover the 50K missing messages.
Thanks a lot for that.
On the same instance I had an NPE without stack trace.
Can someone explain me what happens, or what can be the cause
of the following messages logs :
GitHub user michaelandrepearce opened a pull request:
https://github.com/apache/activemq-artemis/pull/1093
ARTEMIS-994 Support Netty Native Epoll on Linux
The following changes are made to support Epoll.
* Refactored SharedNioEventLoopGroup into renamed SharedEventLoopGroup
Let's make the links 2.x and 1.x. Immutable links makes it easier on
google?
On Mon, Mar 13, 2017 at 4:47 PM Timothy Bish wrote:
> On 03/13/2017 04:44 PM, Clebert Suconic wrote:
> > Right now we have 10. And going up.
> >
> > 1.0, 1.1, 1.5.0 1.5.11.5.4. 2.0
>
> I
On 03/13/2017 04:44 PM, Clebert Suconic wrote:
Right now we have 10. And going up.
1.0, 1.1, 1.5.0 1.5.11.5.4. 2.0
I think John is saying the same thing I said earlier, only keep 1.5.4
and 2.0.0 as those are the latest supported releases, when 1.5.5 ships
then drop 1.5.4 ...
Right now we have 10. And going up.
1.0, 1.1, 1.5.0 1.5.11.5.4. 2.0
On Mon, Mar 13, 2017 at 4:37 PM Timothy Bish wrote:
> On 03/13/2017 04:07 PM, Clebert Suconic wrote:
> > Sure. Latest 1.x and latest 2.x.
> >
> >
> >
> > Just that it seems too much now.
>
>
On 03/13/2017 04:07 PM, Clebert Suconic wrote:
Sure. Latest 1.x and latest 2.x.
Just that it seems too much now.
Isn't that just two instances? That doesn't seem like to much.
On Mon, Mar 13, 2017 at 1:42 PM Jiri Danek wrote:
On Mon, Mar 13, 2017 at 6:27 PM,
I played around with it a bit, nice work! It was faster than I thought
it'd be to export a largish store which is nice. I think an initial
release is not a bad idea, gets you something out that people can kick
the tires on for sure. Once the 2.0.0 release is done I'd go for it.
On
Sure. Latest 1.x and latest 2.x.
Just that it seems too much now.
On Mon, Mar 13, 2017 at 1:42 PM Jiri Danek wrote:
> On Mon, Mar 13, 2017 at 6:27 PM, Clebert Suconic <
> clebert.suco...@gmail.com>
> wrote:
>
> > I was wondering if we could / should update the docs
GitHub user gstraube opened a pull request:
https://github.com/apache/activemq/pull/229
Introduce method to add a single trusted package
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gstraube/activemq master
Alternatively you
On 03/13/2017 01:27 PM, Clebert Suconic wrote:
this made sense at first (at least I think it did), but now that We
will have 10 versions (and counting) of Artemis... this seems a bit
too much...
http://activemq.apache.org/artemis/docs.html
I was wondering if we could / should update the docs
I created a branch for the previous work and named it deprecated-impl
(for want of a better name) and pushed it upstream. Should be clear now
to start on any new development of this client as folks see fit.
On 02/14/2017 02:32 PM, Duane Pauls wrote:
Hello,
I'm relatively new to the ActiveMQ
+1
Just reducing all the 1.x.y docs to the latest 1.x + the latest 2.0 would be
great and will help the users leaving only common uses choices simpler.
And as Clebert pointed, it will help web robots too...
--
View this message in context:
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/1092
NO-JIRA fix race in TopicControlClusterTest
Test didn't account for "remote" queue bindings from other cluster
member which caused a race condition.
You can merge this pull request
On Mon, Mar 13, 2017 at 6:27 PM, Clebert Suconic
wrote:
> I was wondering if we could / should update the docs page to only
> include the latest version (that is 2.0.0)... The docs are still
> maintained at the git, so you can always refer to the doc of the
> version
this made sense at first (at least I think it did), but now that We
will have 10 versions (and counting) of Artemis... this seems a bit
too much...
http://activemq.apache.org/artemis/docs.html
I was wondering if we could / should update the docs page to only
include the latest version (that is
Just to close the loop here, the AMQP NMS client repo is now migrated to
Git and mirrored on Github here:
https://github.com/apache/activemq-nms-amqp
We should probably create a branch of the old client work before pushing
any rework PRs in, I'll take care of that a bit later today.
On
Great. Thanks for all the work you've put in to making this happen, I
know it was much more involved than expected or it would have been in
the past, since it turns out that infra recently stopped doing these
migrations on our behalf locally and you instead had to migrate them
yourself remotely.
I've completed work on moving the SVN repositories for the NMS API and
clients over to Git repositories and tested that the svngit2jira
linkages have been setup properly. The old SVN repos are left intact
but have been made read only.
The new Git Repositories are as follows
NMS API ->
Should be merged now on master and 1.x branches.
Justin
- Original Message -
From: "Clebert Suconic"
To: dev@activemq.apache.org
Sent: Monday, March 13, 2017 10:25:40 AM
Subject: Re: Artemis 1.5.2 - AMQ224000: Failure in initialisation:
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/1090
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
It hasn't been merged yet... give me some time.
On Mon, Mar 13, 2017 at 11:02 AM, Mohamed Badri wrote:
> Thanks a lot,
> I'll apply this patch on the 1.5.4 release.
>
>
>
> On 13 March 2017 at 13:09, Clebert Suconic
> wrote:
>
>> You will have to
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/1089
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/1088
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/1091
NO-JIRA STOMP doc updates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis stompDoc
Alternatively you can
Thanks a lot,
I'll apply this patch on the 1.5.4 release.
On 13 March 2017 at 13:09, Clebert Suconic
wrote:
> You will have to patch the server to be able to restart that server:
>
> https://github.com/apache/activemq-artemis/pull/1089
>
>
>
>
> On Mon, Mar 13, 2017
GitHub user andytaylor opened a pull request:
https://github.com/apache/activemq-artemis/pull/1090
ARTEMIS-1034 - non-durable subscription queue not ended on link close
https://issues.apache.org/jira/browse/ARTEMIS-1034
You can merge this pull request into a Git repository by
Hi Everyone,
With the release of Apache Artemis 2.0.0 coming this week I wanted to get
some feedback on the KahaDB Export tool before tagging version 0.1.0. I'm
calling it version 0.1.0 for now as I would still consider it beta quality
and don't want to promote it to a version 1.0.0 until it has
On Mon, Mar 13, 2017 at 12:55 PM, John D. Ament
wrote:
> On Mon, Mar 13, 2017 at 8:37 AM Timothy Bish wrote:
>
> > On 03/13/2017 06:02 AM, Martyn Taylor wrote:
> > > John,
> > >
> > > The release artifacts have been uploaded dist.apache.org. It'll
>
On Mon, Mar 13, 2017 at 8:55 AM, John D. Ament wrote:
> On Mon, Mar 13, 2017 at 8:37 AM Timothy Bish wrote:
>
>> On 03/13/2017 06:02 AM, Martyn Taylor wrote:
>> > John,
>> >
>> > The release artifacts have been uploaded dist.apache.org. It'll
>>
You will have to patch the server to be able to restart that server:
https://github.com/apache/activemq-artemis/pull/1089
On Mon, Mar 13, 2017 at 5:42 AM, Mohamed Badri wrote:
> Hi,
>
> I'm using Artemis 1.5.2
> and after a problem due to load on the artemis server
> I
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/1089
ARTEMIS-1033 Fixing NPE on PageTX and reload
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis
On Mon, Mar 13, 2017 at 8:37 AM Timothy Bish wrote:
> On 03/13/2017 06:02 AM, Martyn Taylor wrote:
> > John,
> >
> > The release artifacts have been uploaded dist.apache.org. It'll
> probably
> > take a couple of days for the mirrors to catch up.
>
> 24 hours is usually
On 03/13/2017 06:02 AM, Martyn Taylor wrote:
John,
The release artifacts have been uploaded dist.apache.org. It'll probably
take a couple of days for the mirrors to catch up.
24 hours is usually more than enough time.
Thanks
On Sat, Mar 11, 2017 at 5:44 PM, Clebert Suconic
Hi,
I'm using Artemis 1.5.2
and after a problem due to load on the artemis server
I had to restart one instance.
Then, when the instance with the following errors :
===
07:35:12,021 WARN [org.apache.activemq.artemis.journal] AMQ142015:
John,
The release artifacts have been uploaded dist.apache.org. It'll probably
take a couple of days for the mirrors to catch up.
Thanks
On Sat, Mar 11, 2017 at 5:44 PM, Clebert Suconic
wrote:
> Nice one.
>
>
> Please do not send the Announce until the mirrors
35 matches
Mail list logo