[GitHub] activemq-artemis pull request #1036: ARTEMIS-981 OpenWire can't receive empt...

GitHub user gaohoward opened a pull request: https://github.com/apache/activemq-artemis/pull/1036 ARTEMIS-981 OpenWire can't receive empty ObjectMessage When sending an empty ObjectMessage, broker doesn't write a 'length' field to the message buffer. In delivery the broker tr

Memory leak when undeploying webapp with ActiveMQ client - AMQ-6602

I have created ticket with patch. AMQ-6602 -- View this message in context: http://activemq.2283324.n4.nabble.com/Memory-leak-when-undeploying-webapp-with-ActiveMQ-client-AMQ-6602-tp4722312.html Sent from the ActiveMQ - Dev mailing list archiv

[GitHub] activemq-artemis pull request #1035: Couple of random fixes

Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/1035 --- 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 feat

[GitHub] activemq-artemis pull request #1034: ARTEMIS-980 Openwire can't send message...

Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/1034 --- 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 feat

Re: [DISCUSS] Move Apache.NMS project to Git

> So, that's a "Yes, it does duplicate the entire repository (which can be > quite sizeable) in order to have multiple branches checked out > simultaneously." Got it. Clearly a disadvantage. I give up!!! We should probably migrate Artemis and AMQ5 to SVN as well. Pretty horrible disadvantage to h

Re: [DISCUSS] Move Apache.NMS project to Git

On Tue, Feb 21, 2017 at 5:07 PM Clebert Suconic wrote: > > Yes, I think a Vote is a good idea. Makes it very clear, and follows > > established Apache process, and gives a definite cut-off point. > > > Ok, but so far you are the only one to be convinced. > It wouldn't matter if no one needed to

Re: [DISCUSS] Move Apache.NMS project to Git

> I see that it has advantages, > but it also has disadvantages. I/You haven't found one yet.

Re: [DISCUSS] Move Apache.NMS project to Git

> Yes, I think a Vote is a good idea. Makes it very clear, and follows > established Apache process, and gives a definite cut-off point. > Ok, but so far you are the only one to be convinced. > Does that duplicate the entire Git repository? It kind of looks like it > does. Git is very light. i

Re: [DISCUSS] Move Apache.NMS project to Git

On Tue, Feb 21, 2017 at 4:31 PM Clebert Suconic wrote: > On Tue, Feb 21, 2017 at 7:09 PM, Jim Gomes wrote: > > As well as call a vote. A Discussion is only a discussion. It takes a > Vote > > to enable action. > > I really didn't think it would be needed.. you are the only one > against it so fa

Re: [DISCUSS] Move Apache.NMS project to Git

On Tue, Feb 21, 2017 at 7:09 PM, Jim Gomes wrote: > As well as call a vote. A Discussion is only a discussion. It takes a Vote > to enable action. I really didn't think it would be needed.. you are the only one against it so far. I think we are have votes on this thread.. do you need it to be f

Re: [DISCUSS] Move Apache.NMS project to Git

As well as call a vote. A Discussion is only a discussion. It takes a Vote to enable action. And as far as my technical concerns go, perhaps someone more experienced with Git can help me solve them. They are: 1. I am unable to have multiple branches checked out on the machine at the same time, w

Re: [DISCUSS] Move Apache.NMS project to Git

On 02/21/2017 05:23 PM, Clebert Suconic wrote: I suggest you start with adding the current version there, you make progress... later you cherry-pick the commits or rebase against the new repo. This makes a lot more sense to convert it to git then. If I don't get any -1 in 2 days, I will assume

Re: [DISCUSS] Rework NMS.AMQP

I think u still need to fill a contributors agreement PR is a good way to start. But since your PRs will be likely substantial I would recommend the agreement filled from the guys involved. Someone with more legal background can probably help with additional information. On Tue, Feb 21, 2017

Re: [DISCUSS] Rework NMS.AMQP

In parallel with getting this proposal ready, we went ahead and created a github repo to get started: https://github.com/SolaceLabs/nms-amqp It's basically empty, but work has just kicked off in a fork: https://github.com/cjwmorgan-sol-sys/nms-amqp/ As this proposal would indicate, our intent is

Re: [DISCUSS] Move Apache.NMS project to Git

I suggest you start with adding the current version there, you make progress... later you cherry-pick the commits or rebase against the new repo. This makes a lot more sense to convert it to git then. If I don't get any -1 in 2 days, I will assume lazy consensus and open the JIRA on infra. On Tu

Re: [DISCUSS] Move Apache.NMS project to Git

For the NMS AMQP rework, we've created a github repo as a starting point: https://github.com/SolaceLabs/nms-amqp It's rather empty at the moment, but the work has been kicked off in a fork: https://github.com/cjwmorgan-sol-sys/nms-amqp/ There isn't much there yet, but migrating to a git repositor

Re: [DISCUSS] Move Apache.NMS project to Git

For me is a +1! -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-Move-Apache-NMS-project-to-Git-tp4722085p4722285.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [DISCUSS] Move Apache.NMS project to Git

So, do we have a consensus then? Should I just open a JIRA on Infra to make the conversion? On Thu, Feb 16, 2017 at 11:27 AM, Christopher Shannon wrote: > +1 to move the repo to Git for the same reasons already listed by others. > > On Thu, Feb 16, 2017 at 10:39 AM, Robbie Gemmell > wrote: > >>

[GitHub] activemq-artemis issue #983: ARTEMIS-936 - make amqp transformers configurab...

Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/983 @jbertram this will probably be closed without merging... it won't be needed with what I'm doing... AMQP Messages are always raw on my branch.. they only get converted w

Re: Artemis MQTT durable messages and Topics

FWIW, if a queue isn't marked as durable then it doesn't matter if a message on that is durable as it will be lost on restart. Only durable messages on durable queues survive a broker restart. Justin - Original Message - From: "fabio72" To: dev@activemq.apache.org Sent: Tuesday, Febr

Re: Artemis MQTT durable messages and Topics

Hi Fabio, Right now there is no way to specify the durability of just the Retained messages. It's something we can easily add as a new feature. Please open a JIRA and we'll look to get it implemented. Regards Martyn On Tue, Feb 21, 2017 at 10:08 AM, fabio72 wrote: > hi Justin, > after connec

Re: Artemis MQTT durable messages and Topics

hi Justin, after connecting via jmx we saw that all topics are durable (indipendently from qos); analyzing the journal (using artemis data print) we can see that all messages with qos>0 are durable . We think that this behaviour may depends from following code: for topics(from MQTTSubscriptionMana

Re: MQTT Durable Messages and Topic

If you set your QoS=0 then it should be a normal topic sub and not a durable. The documentation is on http://activemq.apache.org/mqtt.html "ActiveMQ is a JMS broker in its core, so there needs to be some mapping between MQTT subscriptions and JMS semantics. Subscriptions with QoS=0 (At Most Once)

Re: [VOTE] Release ActiveMQ-CPP v3.9.4

+1 On Mon, Feb 20, 2017 at 5:09 PM, Jim Gomes wrote: > +1 > > On Mon, Feb 20, 2017 at 9:40 AM Claus Ibsen wrote: > > > +1 > > > > On Mon, Feb 20, 2017 at 6:23 PM, Timothy Bish > wrote: > > > New vote open for ActiveMQ-CPP v3.9.4 > > > > > > This is a new patch release of the ActiveMQ-CPP clien

[GitHub] activemq-artemis pull request #1035: NO-JIRA fix possible STOMP NPE

GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/1035 NO-JIRA fix possible STOMP NPE You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis master_work Alternatively