+1, we're definitely due a release. Let's get on it.
On Fri, May 20, 2016 at 5:31 AM, Claus Ibsen wrote:
> Hi
>
> Isn't it time to cut a new ActiveMQ Artemis release? The previous
> 1.2.0 release is 5 months ago. And since the 1.0 release 1 year ago,
> there has only be 1.1 and 1.2 releases.
>
Hi all,
It's been a while since we last had an Artemis release and I think we're
well overdue a 1.3.0.
Since 1.2.0 good progress has been made on Artemis, including; OpenWire
protocol improvements, support ActiveMQ 5.x JAAS plugins and an initial
implementation of a DB store as well as hardening
GitHub user soleger opened a pull request:
https://github.com/apache/activemq/pull/186
AMQ-6298: Fixed Spring Import-Package wildcard
The org.springframework wildcard is above the Spring-DM
org.springframework.osgi import, causing incorrect OSGi metadata.
https://issues.apa
Github user gaol commented on the pull request:
https://github.com/apache/activemq-artemis/pull/495#issuecomment-220559790
@clebertsuconic I think the 3 lines starts from:
[PageSubscriptionImpl#reloadPageCompletion()](https://github.com/apache/activemq-artemis/commit/3e2adf123b96c3dfad
Github user gaol closed the pull request at:
https://github.com/apache/activemq-artemis/pull/495
---
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 feature
I have been testing with local builds off and on. It's definitely working
quite well.
Have docs been update for the DB Journal?
On May 20, 2016 04:41, "Martyn Taylor" wrote:
> Hi all,
>
> It's been a while since we last had an Artemis release and I think we're
> well overdue a 1.3.0.
>
> Since
1. Hi we do have a requirement of jms messages raised to be processed by each
node in a cluster - Looks like topic does this by design. Is there any
documentation on how to configure this.
2. We also want some of the destinations to be not to processed by all the
nodes.- Is there any way we via co
On Fri, May 20, 2016 at 11:16 AM, John D. Ament
wrote:
> I have been testing with local builds off and on. It's definitely working
> quite well.
>
Great, good to hear.
>
> Have docs been update for the DB Journal?
>
There's a section on JDBC storage under the persistence section of the user
man
Github user asfgit closed the pull request at:
https://github.com/apache/activemq/pull/186
---
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 feature is en
Hi
We have about 40+ PRs on github and some of them are simple typo fixes
and the likes which I have applied some of them which I could just
find.
But I think the AMQ team needs to step up a bit and pay more attention
to the PRs and get them reviewed, merged or closed. It helps
contributions to t
I am attempting to build a highly available Artemis cluster with zero message
loss. Currently I am experimenting with a share nothing architecture, so
each broker in the cluster has its own independent store with replication in
between them.
As far as I can tell when you are running Artemis clus
As far as I'm aware the broker should not acknowledge a durable message before
it is replicated successfully specifically to avoid the problems you mention.
What is your exact use-case, and what are you doing to confirm the message is
being acked before replication?
Justin
- Original Mess
GitHub user pgfox opened a pull request:
https://github.com/apache/activemq-artemis/pull/528
adding 2 links to the examples chapter
added 2 links to the example chapter which were omitted
Best Regards
Pat
You can merge this pull request into a Git repository
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/529
Text fixes + CLI improvement
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis master_work
Alternatively you
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/528
---
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 featu
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/529
---
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 featu
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/523
---
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 featu
Github user sobkowiak closed the pull request at:
https://github.com/apache/activemq/pull/183
---
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 feature is
Github user sobkowiak closed the pull request at:
https://github.com/apache/activemq/pull/182
---
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 feature is
Github user dfj closed the pull request at:
https://github.com/apache/activemq/pull/79
---
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 feature is enable
Github user dfj closed the pull request at:
https://github.com/apache/activemq/pull/78
---
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 feature is enable
Github user dfj closed the pull request at:
https://github.com/apache/activemq/pull/77
---
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 feature is enable
22 matches
Mail list logo
