Re: [DISCUSS} HornetQ & ActiveMQ's next generation

2015-04-09 6:50 GMT+02:00 Chris Mattmann : > Hi Guillaume, > > > -Original Message- > From: Guillaume Nodet > Reply-To: > Date: Wednesday, April 8, 2015 at 3:44 PM > To: > Subject: Re: [DISCUSS} HornetQ & ActiveMQ's next generation > > >>[..snip..] > >> > >> The talk about no one wantin

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

2015-04-09 3:59 GMT+02:00 James Carman : > I am trying to understand the picture that has been painted for us thus > far. Maybe you can help me. First of all, the argument for why we need to > start from the HornetQ code base is because the current core broker is in > such disrepair that we can'

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

Hi Guillaume, -Original Message- From: Guillaume Nodet Reply-To: Date: Wednesday, April 8, 2015 at 3:44 PM To: Subject: Re: [DISCUSS} HornetQ & ActiveMQ's next generation >>[..snip..] >> >> The talk about no one wanting to develop ActiveMQ 5 isn’t backed >> by the data. It doesn’t sup

Re: Naming Suggestions?

Nice, Dan! ArtemisMQ! I like it. On Wed, Apr 8, 2015 at 1:41 PM, Daniel Kulp wrote: > > > On Apr 8, 2015, at 4:23 PM, Hiram Chirino > wrote: > > > > Naming things is hard. If we gave the hornetq code grant a code name > > other than HornetQ or ActiveMQ 6, I think we would be avoid lots of TM >

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

I am trying to understand the picture that has been painted for us thus far. Maybe you can help me. First of all, the argument for why we need to start from the HornetQ code base is because the current core broker is in such disrepair that we can't fix it (and some feel that we should thank our l

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

See Guillaume, it is precisely this attitude that created the problem in the first place. One of the first things developers learn in the incubator is that it's not their project any longer, it's an ASF project. And the ASF has some very clear values, backed by years of experience. One of them

Re: Naming Suggestions?

I believe nest is trademarked already. Is it cold in here? ;) On Wednesday, April 8, 2015, Clebert Suconic wrote: > *If* we have to rename anything, I liked the name "Nest" as the > ActiveMQ Nest broker > > On Wed, Apr 8, 2015 at 4:23 PM, Hiram Chirino > wrote: > > Naming things is hard. If w

Re: Naming Suggestions?

I vote for ActiveMQ-RS. Four reasons: 1. RS stands for Research. 2. RS is alphabetically sequential after Q, and it's fun to say. 3. Seriously doubt it'll clash with a trademarked name. 4. Fits with our other existing sub-project naming conventions (ActiveMQ-NMS, ActiveMQ-CPP, etc.). On Apr 8, 20

Re: Naming Suggestions?

*If* we have to rename anything, I liked the name "Nest" as the ActiveMQ Nest broker On Wed, Apr 8, 2015 at 4:23 PM, Hiram Chirino wrote: > Naming things is hard. If we gave the hornetq code grant a code name > other than HornetQ or ActiveMQ 6, I think we would be avoid lots of TM > confusion.

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

I think most of the code has been written over the years by James, Rob, Hiram, Garry, Dejan and Tim. I can't speak for them, but I don't recall having read anything from them that could lead me to believe they were in any way reluctant about replacing the activemq broker with the one from the horn

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

exaclty my point also - when i read chris' response... no offend, but contribution like this is ... - Period. (imho it even contributes to "flame war") On Thu, Apr 9, 2015 at 12:44 AM, Guillaume Nodet wrote: > 2015-04-08 22:52 GMT+02:00 Chris Mattmann : > > > This isn’t a flame war, and you

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

2015-04-08 22:52 GMT+02:00 Chris Mattmann : > This isn’t a flame war, and you continue to state things about > what’s going to be maintained and what’s not, and it’s not backed > by fact. Some comments below: > > > [...] > > >[..] > >In this very case, I think this is a technical decision, and my

Re: Naming Suggestions?

On Wed, Apr 08, 2015 at 05:34:37PM -0400, Daniel Kulp wrote: >... > That said, since what we are talking about is a code name and not a > name of a *Project* SHOULD be easier (but again, we'll verify with > trademarks@ when we've decided on name). The name should always > be referred to as "Apac

Re: Naming Suggestions?

Chris, Calm down… *At this point* I don’t see any reason for include trademarks@ in this. Once we have some ideas to present to trademarks@, then yes. We definitely need to include them and make sure whatever we select is acceptable. Are we supposed to just send a note that says somethin

Re: Naming Suggestions?

Good point +1 Artemis > On 8 Apr 2015, at 21:52, James Carman wrote: > > http://activemq.apache.org/hermes-jms.html > >> On Wednesday, April 8, 2015, Rob Davies wrote: >> +1 Hermes >> >>> Daniel Kulp 8 April 2015 21:41 > On Apr 8, 2015, at 4:23 PM, Hiram Chirino wrote: > >>

Re: Naming Suggestions?

See: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH For a framework on what to answer about names. Realize as well that despite my repeatedly telling you guys you need to include trademarks@ in this discussion b/c you are bypassing the traditional way of bringing projects into Apache by

Re: Naming Suggestions?

Apache incubating has a very nice ring to it On Wednesday, April 8, 2015, Hiram Chirino wrote: > Naming things is hard. If we gave the hornetq code grant a code name > other than HornetQ or ActiveMQ 6, I think we would be avoid lots of TM > confusion. Anybody have any suggestion what would be

Re: Naming Suggestions?

i'm still fine with amq-6 :) but if it has to be changed, my vote is of course "hades" :P what ever name - lets get going! On Wed, Apr 8, 2015 at 10:42 PM, Rob Davies wrote: > +1 Hermes > > Daniel Kulp > 8 April 2015 21:41 > > On Apr 8, 2015, at 4:23 PM, Hiram Chirino > wrote: > > Namin

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

This isn’t a flame war, and you continue to state things about what’s going to be maintained and what’s not, and it’s not backed by fact. Some comments below: -Original Message- From: Guillaume Nodet Reply-To: "bo...@apache.org" Date: Wednesday, April 8, 2015 at 12:52 PM To: "bo...@apa

Re: Naming Suggestions?

Hermes JMS (http://www.hermesjms.com) is a product in the same area. Although it’s a dead project, it still widely used as it’s bundled with the popular Soap UI product. A name collision could lead to confusion. Just a thought. Petter Från: Rob Davies mailto:rajdav

Re: Naming Suggestions?

http://activemq.apache.org/hermes-jms.html On Wednesday, April 8, 2015, Rob Davies wrote: > +1 Hermes > > Daniel Kulp > 8 April 2015 21:41 > > On Apr 8, 2015, at 4:23 PM, Hiram Chirino > wrote: > > Naming things is hard. If we gave the hornetq code grant a code name > other than HornetQ

Re: Naming Suggestions?

Hermes is already taken by Hermes JMS.. I wouldn't want to clash with that name: http://www.hermesjms.com/confluence/display/HJMS/Home On Wed, Apr 8, 2015 at 4:42 PM, Rob Davies wrote: > +1 Hermes > > Daniel Kulp > 8 April 2015 21:41 > > On Apr 8, 2015, at 4:23 PM, Hiram Chirino > wrote

Re: Naming Suggestions?

+1 Hermes Daniel Kulp 8 April 2015 21:41 On Apr 8, 2015, at 4:23 PM, Hiram Chirino wrote: Naming things is hard. If we gave the hornetq code grant a code name other than HornetQ or ActiveMQ 6, I think we would be avoid lots of TM confusion. Anybody have any suggest

Re: Naming Suggestions?

> On Apr 8, 2015, at 4:23 PM, Hiram Chirino wrote: > > Naming things is hard. If we gave the hornetq code grant a code name > other than HornetQ or ActiveMQ 6, I think we would be avoid lots of TM > confusion. Anybody have any suggestion what would be a good name to > give it? Hermes?That

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

Who are in the 90% club and are they really all on board with the new broker? > On Apr 8, 2015, at 3:52 PM, Guillaume Nodet wrote: > > In this very case, I think this is a technical decision, and my trust > clearly goes to the ones that know and wrote 90% of the code, and when they > all seem t

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

> On Apr 8, 2015, at 3:52 PM, Guillaume Nodet wrote: > > Actually, all those concerns looks a bit weird when I think about it, given > everything was done openly : the code has been accepted, the git repo has > been named "activemq-6" and all the commits lead to messages on the mailing > list st

Naming Suggestions?

Naming things is hard. If we gave the hornetq code grant a code name other than HornetQ or ActiveMQ 6, I think we would be avoid lots of TM confusion. Anybody have any suggestion what would be a good name to give it? -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

+1 Can I add a point into that: there was a lot of hard at the docs as well, to give it a nice apache ActiveMQ looks: http://people.apache.org/~martyntaylor/docs/10.0.0-M1/index.html We reworked the docs, rebranded, improved... it's beyond in quality to any work I had previously been part in

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

2015-04-08 18:33 GMT+02:00 Chris Mattmann : > Hi Guillaume, > > > -Original Message- > From: Guillaume Nodet > Reply-To: > Date: Wednesday, April 8, 2015 at 9:28 AM > To: , > Subject: Re: [DISCUSS} HornetQ & ActiveMQ's next generation > > >My understanding is the following: > > * the us

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

On Wed, Apr 8, 2015 at 2:14 PM, David Nalley wrote: >... > That's interesting, thanks for the clarification. > My confusion is from on the one hand seeing statements about HornetQ > being the future of ActiveMQ[1], yet seemingly no mention of ActiveMQ > at all on the HornetQ project's site. In fa

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

that's because every communication. any website update is in wait mode now. I'm asking someone to either update or take that page down. So whatever is written at [1] is "Lorem Ipsum" text. and was supposed to be there for a period so short that nobody would have noticed it if the release happene

[jira] [Commented] (AMQ-5712) Broker can deadlock when using queues while producers wait on disk space

[ https://issues.apache.org/jira/browse/AMQ-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485861#comment-14485861 ] Christopher L. Shannon commented on AMQ-5712: - [~tabish121], sounds good. I don

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

On Wed, Apr 8, 2015 at 2:46 PM, Clebert Suconic wrote: >> .. while it seems that the >> HornetQ open source project and community are continuing to develop >> that same codebase and community external to the ASF as well as inside >> the ASF (often by the same people working in both communities.) >

[jira] [Commented] (AMQ-5712) Broker can deadlock when using queues while producers wait on disk space

[ https://issues.apache.org/jira/browse/AMQ-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485840#comment-14485840 ] Timothy Bish commented on AMQ-5712: --- I general it's a good idea to add some unit tests tha

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

strong +1 On Wed, Apr 8, 2015 at 8:08 PM, Tracy Snell wrote: > My understanding is that there’s a raging debate on this topic in the > private mailing list. This seems entirely against the community ethos of > Apache. Does the PMC get to debate this in private and make a decision on > the future

[jira] [Commented] (AMQ-5712) Broker can deadlock when using queues while producers wait on disk space

[ https://issues.apache.org/jira/browse/AMQ-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485821#comment-14485821 ] Christopher L. Shannon commented on AMQ-5712: - I just submitted a pull request:

[jira] [Commented] (AMQ-5712) Broker can deadlock when using queues while producers wait on disk space

[ https://issues.apache.org/jira/browse/AMQ-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485804#comment-14485804 ] ASF GitHub Bot commented on AMQ-5712: - GitHub user cshannon opened a pull request:

[GitHub] activemq pull request: Modified StoreQueueCursor to prevent a brok...

GitHub user cshannon opened a pull request: https://github.com/apache/activemq/pull/84 Modified StoreQueueCursor to prevent a broker deadlock Modified StoreQueueCursor to properly implement tryAddMessageLast so that the message lock can be released during a timeout when the temporar

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

> .. while it seems that the > HornetQ open source project and community are continuing to develop > that same codebase and community external to the ASF as well as inside > the ASF (often by the same people working in both communities.) there are no developments or features being done at the ho

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

On Wed, Apr 8, 2015 at 12:28 PM, Guillaume Nodet wrote: > My understanding is the following: > * the use of "HornetQ" in all the conversations so far were referring to > the "HornetQ code donation to the Apache ActiveMQ project". > * the HornetQ trademarks were not transferred to the ASF > * th

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

I’m investigating this right now, Tracy. Can you please reveal where you heard this? -Original Message- From: Tracy Snell Reply-To: Date: Wednesday, April 8, 2015 at 11:08 AM To: Cc: Subject: Re: [DISCUSS} HornetQ & ActiveMQ's next generation >My understanding is that there’s a ragi

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

My understanding is that there’s a raging debate on this topic in the private mailing list. This seems entirely against the community ethos of Apache. Does the PMC get to debate this in private and make a decision on the future of the project without the rest of us in the community even seeing t

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

Inline. Hadrian On 04/01/2015 06:47 AM, oliverd wrote: Hi, as a user of ActiveMQ running it productively I can only stress the importance of introducing a new scalable broker core. Challenges like cloud, IoT cry for scalability and that's where other brokers like RabbitMQ create a lot of momen

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

Hi Guillaume, -Original Message- From: Guillaume Nodet Reply-To: Date: Wednesday, April 8, 2015 at 9:28 AM To: , Subject: Re: [DISCUSS} HornetQ & ActiveMQ's next generation >My understanding is the following: > * the use of "HornetQ" in all the conversations so far were referring to >

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

My understanding is the following: * the use of "HornetQ" in all the conversations so far were referring to the "HornetQ code donation to the Apache ActiveMQ project". * the HornetQ trademarks were not transferred to the ASF * the "HornetQ" references in the donation have been removed in the git

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

> The IP clearance does not appear to be completed: > > http://incubator.apache.org/ip-clearance/hornetq.html > The first release (6.0.0.M1) was supposed to finish that part as part of the donation process. We cleared all the CAT-x and the first release was supposed to accomplish/finish the IP cle

[jira] [Updated] (AMQ-5498) Scheduled messages not saved to LevelDB backing

[ https://issues.apache.org/jira/browse/AMQ-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5498: -- Issue Type: New Feature (was: Bug) > Scheduled messages not saved to LevelDB backing > --

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

Hi Gary, Thanks. Well, we have a major problem then - see the subject of this email thread, and much of the discussion the last month. The discussion is one of these options: 1. Apache ActiveMQ has multiple products with multiple versions: a. ActiveMQ - (version 5.x.x) b. HornetQ - (which som

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

On Wed, Apr 8, 2015 at 11:56 AM, Gary Tully wrote: > Hi Chris, > on 1) there may be a misunderstanding here. The code grant is just > that, code. there is no trademark grant. There is no intention of > having apache hornetq, that is not an option with the code grant that > we have. Part of ip clea

[jira] [Commented] (AMQ-5568) Deleting lock file on broker shut down can take a master broker down

[ https://issues.apache.org/jira/browse/AMQ-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485443#comment-14485443 ] clebert suconic commented on AMQ-5568: -- I just sent a fix that could be related to this

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

Hi Chris, on 1) there may be a misunderstanding here. The code grant is just that, code. there is no trademark grant. There is no intention of having apache hornetq, that is not an option with the code grant that we have. Part of ip clearance and cleanup was to remove all references to hornetq. 2(3

Re: LockFile race

Proposed fix: https://github.com/clebertsuconic/activemq/commit/ab8f54b0661755a3b5d8afbd18341e15ab4fe38c On Wed, Apr 8, 2015 at 11:05 AM, Clebert Suconic wrote: > Actually the race could happen in production. > > the real race is because LockFile will have true to remove file when > unlocking.

Re: LockFile race

Actually the race could happen in production. the real race is because LockFile will have true to remove file when unlocking. The other server could eventually lock the file before it was removed and then it would not be locked later. you could have a server not eventually waking up because of t

Re: [DISCUSS} HornetQ & ActiveMQ's next generation

Hi Everyone, These are my following concerns as an ASF director that the ActiveMQ community needs to address. 1. RH has a product, called HornetQ, which includes a website; branding, etc. http://hornetq.jboss.org/ At a minimum this is an extreme branding confusion if this is ActiveMQ 6 and even

[jira] [Commented] (AMQ-5714) Issue with pathCanonical() method within activemq startup for installation paths that consist of directories with a single character or 2 characters

[ https://issues.apache.org/jira/browse/AMQ-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485270#comment-14485270 ] ASF GitHub Bot commented on AMQ-5714: - GitHub user spurin opened a pull request: ht

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

GitHub user spurin opened a pull request: https://github.com/apache/activemq/pull/83 https://issues.apache.org/jira/browse/AMQ-5714 You can merge this pull request into a Git repository by running: $ git pull https://github.com/spurin/activemq AMQ-5714 Alternatively you can r

[jira] [Updated] (AMQ-5714) Issue with pathCanonical() method within activemq startup for installation paths that consist of directories with a single character or 2 characters

[ https://issues.apache.org/jira/browse/AMQ-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5714: -- Component/s: (was: AMQP) > Issue with pathCanonical() method within activemq startup for installation

Re: [PROPOSAL] Pluggable Brokers...

I guess if this would help the ActiveMQ developer by reducing code debt and making maintenance simpler, it's a Good Thing. Pluggable architectures have a certain amount of overhead, though. I don't want to discourage interesting and new areas of architecture. The original message said the pluggabl

[jira] [Updated] (AMQ-5714) Issue with pathCanonical() method within activemq startup

[ https://issues.apache.org/jira/browse/AMQ-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Spurin updated AMQ-5714: -- Description: The pathCanonical method does not work as expected for directories that contain either singl

[jira] [Updated] (AMQ-5714) Issue with pathCanonical() method within activemq startup for installation paths that consist of directories with a single character or 2 characters

[ https://issues.apache.org/jira/browse/AMQ-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Spurin updated AMQ-5714: -- Summary: Issue with pathCanonical() method within activemq startup for installation paths that consist of

[jira] [Updated] (AMQ-5714) Issue with pathCanonical() method within activemq startup

[ https://issues.apache.org/jira/browse/AMQ-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Spurin updated AMQ-5714: -- Description: The pathCanonical method does not work as expected for directories that contain either singl

[jira] [Updated] (AMQ-5714) Issue with pathCanonical() method within activemq startup

[ https://issues.apache.org/jira/browse/AMQ-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Spurin updated AMQ-5714: -- Description: The pathCanonical method does not work as expected for directories that contain either singl

[jira] [Updated] (AMQ-5709) Logging of "Database ... is locked" should be done on level DEBUG

[ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5709: -- Fix Version/s: (was: 5.x) (was: 6.0.0) 5.12.0 > Logging of "

[jira] [Created] (AMQ-5714) Issue with pathCanonical() method within activemq startup

James Spurin created AMQ-5714: - Summary: Issue with pathCanonical() method within activemq startup Key: AMQ-5714 URL: https://issues.apache.org/jira/browse/AMQ-5714 Project: ActiveMQ Issue Type:

[jira] [Closed] (AMQ-5635) logging not configureable in activemq-client-api

[ https://issues.apache.org/jira/browse/AMQ-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5635. - Resolution: Incomplete Cannot reproduce, no config files attached to check users side. > logging not conf

[jira] [Commented] (AMQ-5665) memory store is broken in 5.11.0 for advisories (and probably other issues as well)

[ https://issues.apache.org/jira/browse/AMQ-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485218#comment-14485218 ] Timothy Bish commented on AMQ-5665: --- Would recommend you try and create a small unit test

Re: [DISCUSS] dev mailing list is cluttered

+0 Mail filters working fine here, but if you do this please ensure it is properly announced and documented on the Wiki so folks can find the new mailing list. On Tue, Apr 7, 2015 at 10:43 AM, artnaseef wrote: > Using Nabble, as I do, to keep up with the dev mailing list, this is what > it > lo

[jira] [Updated] (AMQ-5713) doHandleReplyTo cannot be set in activemq.xml

[ https://issues.apache.org/jira/browse/AMQ-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praful Tarkar updated AMQ-5713: --- Component/s: (was: Broker) networkbridge > doHandleReplyTo cannot be set in activem

[jira] [Updated] (AMQ-5713) doHandleReplyTo cannot be set in activemq.xml

[ https://issues.apache.org/jira/browse/AMQ-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praful Tarkar updated AMQ-5713: --- Description: While configuring the bridges, if we try to set the doHandleReplyTo parameter in the activ

[jira] [Updated] (AMQ-5713) doHandleReplyTo cannot be set in activemq.xml

[ https://issues.apache.org/jira/browse/AMQ-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praful Tarkar updated AMQ-5713: --- Description: While configuring the bridges, if we try to set the doHandleReplyTo parameter in the activ

[jira] [Updated] (AMQ-5713) doHandleReplyTo cannot be set in activemq.xml

[ https://issues.apache.org/jira/browse/AMQ-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praful Tarkar updated AMQ-5713: --- Attachment: activemq.log > doHandleReplyTo cannot be set in activemq.xml > -

[jira] [Created] (AMQ-5713) doHandleReplyTo cannot be set in activemq.xml

Praful Tarkar created AMQ-5713: -- Summary: doHandleReplyTo cannot be set in activemq.xml Key: AMQ-5713 URL: https://issues.apache.org/jira/browse/AMQ-5713 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (ACTIVEMQ6-19) Disable Server Side Load Balancing on message routing

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485075#comment-14485075 ] Andy Taylor commented on ACTIVEMQ6-19: -- Im currently looking at https://issues.apac

Re: [DISCUSS] dev mailing list is cluttered

+1 On 08/04/15 11:09, Martyn Taylor wrote: +1 for separate JIRA list. iss...@activemq.apache.org makes sense to me. On 08/04/15 10:46, Dejan Bosanac wrote: +1 for separate lists Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://se

Re: [DISCUSS] dev mailing list is cluttered

+1 for separate JIRA list. iss...@activemq.apache.org makes sense to me. On 08/04/15 10:46, Dejan Bosanac wrote: +1 for separate lists Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.man

Re: [DISCUSS] dev mailing list is cluttered

+1 for separate lists Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Tue, Apr 7, 2015 at 11:56 PM, Jim Gomes wrote: > +1 for lazy consensus. > > On Tue, Apr 7, 201

Re: [PROPOSAL] Pluggable Brokers...

So I haven't had the time to research this - but as lack of instant feedback is interpreted as ignoring, I believe this has merit - but will require some in depth investigation. James Carman 8 April 2015 08:13 Pluggable *within* ActiveMQ. That is what doesn'

Re: [PROPOSAL] Pluggable Brokers...

Pluggable *within* ActiveMQ. That is what doesn't exist. The idea is that the underlying engine could be optimized on a case-by-case basis. For instance, you may be able to streamline the implementation of a broker that doesn't require persistence at all. Right now, we have one implementation t