[GitHub] activemq pull request: Improved filename sanitization

[dfj]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq pull request: Improved filename sanitization

[dfj]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq pull request: Improved filename sanitization

[dfj]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq pull request: https://issues.apache.org/jira/browse/AMQ-6...

[sobkowiak]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq pull request: https://issues.apache.org/jira/browse/AMQ-6...

[sobkowiak]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request: new logging.properties and trace fo...

[asfgit]

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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request: Text fixes + CLI improvement

[asfgit]

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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request: adding 2 links to the examples chap...

[asfgit]

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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request: Text fixes + CLI improvement

[jbertram]

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 can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/529.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #529


commit 76f6c9c3bda35f918865bc273672e12021efcaf6
Author: jbertram 
Date:   2016-05-19T16:49:51Z

Make a few tests more robust

commit 643fa22d05046c74aae2052807b92a955c89fda4
Author: jbertram 
Date:   2016-05-20T16:24:37Z

ARTEMIS-530 acceptor CLI config




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request: adding 2 links to the examples chap...

[pgfox]

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 by running:

$ git pull https://github.com/pgfox/activemq-artemis fixing_links

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/528.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #528


commit ceb2c32ba184fba73dd2391e7709357dc948df89
Author: Pat Fox 
Date:   2016-05-20T16:06:01Z

adding 2 links to the examples chapter




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Artemis Replication before acknowledgement

[Justin Bertram]

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 Message -
From: "aclayton" 
To: dev@activemq.apache.org
Sent: Friday, May 20, 2016 9:42:39 AM
Subject: Artemis Replication before acknowledgement

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 cluster with replication
the broker will acknowledge a message before the message is successfully
replicated.  The problem that this generates is that if the broker dies
before it is replicated, but after the acknowledgement, the message is
essentially lost.  Is there any plan to add this functionality in order to
ensure zero message loss during failover without using a shared store?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-Replication-before-acknowledgement-tp4712215.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Artemis Replication before acknowledgement

[aclayton]

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 cluster with replication
the broker will acknowledge a message before the message is successfully
replicated.  The problem that this generates is that if the broker dies
before it is replicated, but after the acknowledgement, the message is
essentially lost.  Is there any plan to add this functionality in order to
ensure zero message loss during failover without using a shared store?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Artemis-Replication-before-acknowledgement-tp4712215.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

More attention to - Apache ActiveMQ Github PRs

[Claus Ibsen]

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 the project if people can get PRs merged, and makes
the project better.

Yeah its a bit more work on us, but its "the game we play in".

There is likely some more hardcode PRs in there which needs more the
core team to take a look at. And there is some old ones that need
--rebase or to be closed if the user has gone.

And when you apply a PR from github you can do this easiest by

Grabbing that line of text that is sent in the @dev mail when a PR is open.
And then *remember* to rebase on top of the branch eg after that do

git pull --rebase

Then the PR is played on top of the current code. Otherwise we get
those ugly and irritation git branches in our master branch. We do
like that at Apache Camel.




-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

[GitHub] activemq pull request: AMQ-6298: Fixed Spring Import-Package wildc...

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [HEADSUP] Artemis 1.3.0 release preparation

[Martyn Taylor]

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
manual, though I can see that this is slightly outdated (we've since added
large message support).  I'll ensure it's updated before cutting any RC.

Cheers.

> 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.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 of the replication HA
> > functionality and many other bug fixes.
> >
> > I'm going to start preparing a 1.3.0 RC and should have something with
> you
> > all in the next week or so.  If you have any work you'd like to get in
> > before the release, now would be a good time.
> >
> > Regards
> > Martyn
> >
>

Raise JMS messages to all the nodes in cluster

[Dignesh Goyal]

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 configuration to acheive this usings Topic




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Raise-JMS-messages-to-all-the-nodes-in-cluster-tp4712202.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [HEADSUP] Artemis 1.3.0 release preparation

[John D. Ament]

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.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 of the replication HA
> functionality and many other bug fixes.
>
> I'm going to start preparing a 1.3.0 RC and should have something with you
> all in the next week or so.  If you have any work you'd like to get in
> before the release, now would be a good time.
>
> Regards
> Martyn
>

[GitHub] activemq-artemis pull request: [ARTEMIS-506] PagingTest#testDelete...

[gaol]

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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request: [ARTEMIS-506] PagingTest#testDelete...

[gaol]

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/3e2adf123b96c3dfade3d1584ea0ddf65a876941#diff-0f3a0fc675330f6da3b510a9428b6470R196)
 in your last changes fixed the issue.

I thought there maybe something to do within this method but not realized 
that the PagingStore can be used that way. :+1: 

I think this PR can be closed now.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq pull request: AMQ-6298: Fixed Spring Import-Package wildc...

[soleger]

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.apache.org/jira/browse/AMQ-6298

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/soleger/activemq AMQ-6298

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/186.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #186


commit 8b7632cb4f6aaa0d7d7c2febab5e60b6abcf3dff
Author: Seth Leger 
Date:   2016-05-20T08:57:51Z

AMQ-6298: Moved Spring Import-Package wildcard below other Spring
imports.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[HEADSUP] Artemis 1.3.0 release preparation

[Martyn Taylor]

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 of the replication HA
functionality and many other bug fixes.

I'm going to start preparing a 1.3.0 RC and should have something with you
all in the next week or so.  If you have any work you'd like to get in
before the release, now would be a good time.

Regards
Martyn

Re: New ActiveMQ Artemis Release

[Martyn Taylor]

+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.
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>