[jira] [Commented] (ACTIVEMQ6-97) Change HQ to AMQ for properties/headers/doc
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494342#comment-14494342 ] Justin Bertram commented on ACTIVEMQ6-97: - As I understand it, the idea with the code donation was to *merge* communities, not necessarily to abandon one in favor of the other. That means support for both old HornetQ clients and old ActiveMQ clients. > Change HQ to AMQ for properties/headers/doc > --- > > Key: ACTIVEMQ6-97 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-97 > Project: Apache ActiveMQ 6 > Issue Type: Improvement >Reporter: Jeff Genender > > Change HQ to AMQ for properties/headers/doc. Remove as much *HQ* as possible > and change to AMQ to make this close to the ActiveMQ project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-96) Implement administrative limit for the maximum client connections allowed
Justin Bertram created ACTIVEMQ6-96: --- Summary: Implement administrative limit for the maximum client connections allowed Key: ACTIVEMQ6-96 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-96 Project: Apache ActiveMQ 6 Issue Type: Sub-task Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 6.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (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=14484050#comment-14484050 ] Justin Bertram edited comment on ACTIVEMQ6-19 at 4/8/15 2:41 AM: - How about we replace the option on the with a option that can be one of three options: * OFF (new behavior not available today - default) * STRICT (behave like today when forward-when-no-consumers = true) * ON_DEMAND (behave like today when forward-when-no-consumers = false) Thoughts? was (Author: jbertram): How about we replace the option on the with a option that can be one of three options: * OFF (new behavior not available today - default) * STRICT (behave like today when forward-when-no-consumers = true) * CONSUMERS (behave like today when forward-when-no-consumers = false) Thoughts? > Disable Server Side Load Balancing on message routing > - > > Key: ACTIVEMQ6-19 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-19 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: clebert suconic >Assignee: Justin Bertram > Fix For: 6.1.0 > > > It should be possible to disable server side load balancing on message > producers with a configuration option. > Once we introduce this configuration the default should be off (meaning > server side load balancing = no) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (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=14484050#comment-14484050 ] Justin Bertram edited comment on ACTIVEMQ6-19 at 4/7/15 10:15 PM: -- How about we replace the option on the with a option that can be one of three options: * OFF (new behavior not available today - default) * STRICT (behave like today when forward-when-no-consumers = true) * CONSUMERS (behave like today when forward-when-no-consumers = false) Thoughts? was (Author: jbertram): How about we replace the option on the with a option that can be one of three options: * OFF (new behavior not available today - default) * STRICT (behave like today when forward-when-no-consumers = true) * CONSUMERS (behave like today when forward-when-no-consumers = false) Thoughts? > Disable Server Side Load Balancing on message routing > - > > Key: ACTIVEMQ6-19 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-19 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: clebert suconic >Assignee: Justin Bertram > Fix For: 6.1.0 > > > It should be possible to disable server side load balancing on message > producers with a configuration option. > Once we introduce this configuration the default should be off (meaning > server side load balancing = no) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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=14484050#comment-14484050 ] Justin Bertram commented on ACTIVEMQ6-19: - How about we replace the option on the with a option that can be one of three options: * OFF (new behavior not available today - default) * STRICT (behave like today when forward-when-no-consumers = true) * CONSUMERS (behave like today when forward-when-no-consumers = false) Thoughts? > Disable Server Side Load Balancing on message routing > - > > Key: ACTIVEMQ6-19 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-19 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: clebert suconic > Fix For: 6.1.0 > > > It should be possible to disable server side load balancing on message > producers with a configuration option. > Once we introduce this configuration the default should be off (meaning > server side load balancing = no) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (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:all-tabpanel ] Justin Bertram reassigned ACTIVEMQ6-19: --- Assignee: Justin Bertram > Disable Server Side Load Balancing on message routing > - > > Key: ACTIVEMQ6-19 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-19 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: clebert suconic >Assignee: Justin Bertram > Fix For: 6.1.0 > > > It should be possible to disable server side load balancing on message > producers with a configuration option. > Once we introduce this configuration the default should be off (meaning > server side load balancing = no) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-87) Strip @author tags from Java source
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-87. - Resolution: Fixed https://github.com/apache/activemq-6/pull/171 > Strip @author tags from Java source > --- > > Key: ACTIVEMQ6-87 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-87 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Affects Versions: 6.0.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.1.0 > > > Way back in 2004 [the Apache Board officially discouraged the use of 'author' > tags|http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt] > in source code. They are not _banned_, but merely discouraged. However, I > think it's probably a good idea to strip them from our source all the same. > Other projects (e.g. > [Camel|https://issues.apache.org/jira/browse/CAMEL-1812]) have done the same. > Here are a few other reasons to remove them (taken from > [here|https://issues.jboss.org/browse/JBRULES-2895]): > The author tags in the java files are a maintenance nightmare: > - A large percentage is wrong, incomplete or inaccurate. > - Most of the time, it only contains the original author. Many files are > completely refactored/expanded by other authors. > - Git is accurate, that is the canonical source to find the correct author. > To find the correct author of a piece of code, you always have to double > check with git, you cannot suppose the author on the author tag alone. > - Author tags promote "code ownership", which is bad in the long run. > - If people work on a piece they perceive as being owned by someone else, > they tend to: > -- only fix what they are assigned to fix, not everything that's broken. > -- discard responsibility if that code doesn't work properly. > -- be scared of stepping of the feet of the owner > - Instead of "code ownership", we need "module leadership" and "peer reviews". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-87) Strip @author tags from Java source
Justin Bertram created ACTIVEMQ6-87: --- Summary: Strip @author tags from Java source Key: ACTIVEMQ6-87 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-87 Project: Apache ActiveMQ 6 Issue Type: Bug Affects Versions: 6.0.0 Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 6.1.0 Way back in 2004 [the Apache Board officially discouraged the use of 'author' tags|http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt] in source code. They are not _banned_, but merely discouraged. However, I think it's probably a good idea to strip them from our source all the same. Other projects (e.g. [Camel|https://issues.apache.org/jira/browse/CAMEL-1812]) have done the same. Here are a few other reasons to remove them (taken from [here|https://issues.jboss.org/browse/JBRULES-2895]): The author tags in the java files are a maintenance nightmare: - A large percentage is wrong, incomplete or inaccurate. - Most of the time, it only contains the original author. Many files are completely refactored/expanded by other authors. - Git is accurate, that is the canonical source to find the correct author. To find the correct author of a piece of code, you always have to double check with git, you cannot suppose the author on the author tag alone. - Author tags promote "code ownership", which is bad in the long run. - If people work on a piece they perceive as being owned by someone else, they tend to: -- only fix what they are assigned to fix, not everything that's broken. -- discard responsibility if that code doesn't work properly. -- be scared of stepping of the feet of the owner - Instead of "code ownership", we need "module leadership" and "peer reviews". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-86) Backup announcement may fail
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-86. - Resolution: Fixed https://github.com/apache/activemq-6/pull/146 > Backup announcement may fail > > > Key: ACTIVEMQ6-86 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-86 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Affects Versions: 6.0.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.1.0 > > > When a live and backup server are both started at or near the same moment > there is a small window where the live server's acceptors have been started > but the server's state != STARTED. During this window if the backup sends its > announcement the announcement will fail and the backup will shutdown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-86) Backup announcement may fail
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-86: Fix Version/s: 6.1.0 > Backup announcement may fail > > > Key: ACTIVEMQ6-86 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-86 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Affects Versions: 6.0.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.1.0 > > > When a live and backup server are both started at or near the same moment > there is a small window where the live server's acceptors have been started > but the server's state != STARTED. During this window if the backup sends its > announcement the announcement will fail and the backup will shutdown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-86) Backup announcement may fail
Justin Bertram created ACTIVEMQ6-86: --- Summary: Backup announcement may fail Key: ACTIVEMQ6-86 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-86 Project: Apache ActiveMQ 6 Issue Type: Bug Affects Versions: 6.0.0 Reporter: Justin Bertram Assignee: Justin Bertram When a live and backup server are both started at or near the same moment there is a small window where the live server's acceptors have been started but the server's state != STARTED. During this window if the backup sends its announcement the announcement will fail and the backup will shutdown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-77) Implement automatic creation of JMS queues on send or receive when using AMQP
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338656#comment-14338656 ] Justin Bertram commented on ACTIVEMQ6-77: - https://github.com/apache/activemq-6/pull/92 > Implement automatic creation of JMS queues on send or receive when using AMQP > - > > Key: ACTIVEMQ6-77 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-77 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-77) Implement automatic creation of JMS queues on send or receive when using AMQP
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-77. - Resolution: Implemented > Implement automatic creation of JMS queues on send or receive when using AMQP > - > > Key: ACTIVEMQ6-77 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-77 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-82) start script limitations
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333493#comment-14333493 ] Justin Bertram commented on ACTIVEMQ6-82: - [~scoopex], I think maybe you are commenting under the impression that this issue was filed against ActiveMQ 5.x. However, it is filed against ActiveMQ 6 so I don't think your comment (or link) is germane to this issue. > start script limitations > > > Key: ACTIVEMQ6-82 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-82 > Project: Apache ActiveMQ 6 > Issue Type: Bug > Environment: UNIX >Reporter: Daniel Pocock > > This issue concerns the start script: > ./distribution/activemq/src/main/resources/bin/activemq > There are various issues with JAVA_ARGS at the bottom: > a) memory parameters are hard-coded in the script and can't be overridden > without modifying the script > b) data.dir is hardcoded in the script and can't be overridden without > modifying the script > Problem (a) was also present in HornetQ while problem (b) was not there. > With HornetQ 2.3, it was possible to override the data.dir and also add other > properties or JMXetric to the JVM command line by setting the CLUSTER_PROPS > variable in a local wrapper script. However, setting heap parameters in > CLUSTER_PROPS was ineffective because the HornetQ run.sh would then set them > to other values later on the command line. > JBoss / Wildfly seems to do a better job of splitting the logic and > configuration, they have a script called bin/standalone.sh that contains the > logic and a separate file, bin/standalone.conf that can be customized with > environment variables. I think this would be a good model for ActiveMQ 6 to > follow. Is there already any discussion about refactoring the script? > This is important for various reasons: > - people deploying the broker in production environments don't like to modify > the scripts supplied by a vendor, they usually prefer to have a configuration > file of their own > - when upgrading, it is an extra hassle to merge changes into the scripts if > they have been modified locally > - some people may want to run multiple instances using the same installation > directory, same scripts and just using different data and log directories -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-77) Implement automatic creation of JMS queues on send or receive when using AMQP
Justin Bertram created ACTIVEMQ6-77: --- Summary: Implement automatic creation of JMS queues on send or receive when using AMQP Key: ACTIVEMQ6-77 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-77 Project: Apache ActiveMQ 6 Issue Type: New Feature Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-76) Implement automatic creation of JMS queues on send or subscribe when using STOMP
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-76: Summary: Implement automatic creation of JMS queues on send or subscribe when using STOMP (was: Implement automatic creation of queues on send or subscribe when using STOMP) > Implement automatic creation of JMS queues on send or subscribe when using > STOMP > > > Key: ACTIVEMQ6-76 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-76 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-76) Implement automatic creation of queues on send or subscribe when using STOMP
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-76. - Resolution: Implemented https://github.com/apache/activemq-6/pull/90 > Implement automatic creation of queues on send or subscribe when using STOMP > > > Key: ACTIVEMQ6-76 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-76 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-76) Implement automatic creation of queues on send or subscribe when using STOMP
Justin Bertram created ACTIVEMQ6-76: --- Summary: Implement automatic creation of queues on send or subscribe when using STOMP Key: ACTIVEMQ6-76 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-76 Project: Apache ActiveMQ 6 Issue Type: New Feature Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-52) Graceful Shutdown
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296987#comment-14296987 ] Justin Bertram commented on ACTIVEMQ6-52: - [~jmesnil], in the case where you want to have a different timeout you should simply be able to invoke org.apache.activemq.core.server.ActiveMQServer.getConfiguration().setGracefulShutdownTimeout(long) and then invoke org.apache.activemq.core.server.ActiveMQServer.stop(boolean). Is that not sufficient for your needs? > Graceful Shutdown > - > > Key: ACTIVEMQ6-52 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-52 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: clebert suconic >Assignee: Justin Bertram > Fix For: 6.0.0 > > > We should provide a way for the system to gracefully shutdown connections > allowing them to finish their work before the server is going out. > This could be done by issuing a close from Server to client on all the > connections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-72) Create additional tests for graceful shutdown scenarios
Justin Bertram created ACTIVEMQ6-72: --- Summary: Create additional tests for graceful shutdown scenarios Key: ACTIVEMQ6-72 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-72 Project: Apache ActiveMQ 6 Issue Type: Task Affects Versions: 6.0.0 Reporter: Justin Bertram Fix For: 6.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-52) Graceful Shutdown
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-52. - Resolution: Done > Graceful Shutdown > - > > Key: ACTIVEMQ6-52 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-52 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: clebert suconic >Assignee: Justin Bertram > Fix For: 6.0.0 > > > We should provide a way for the system to gracefully shutdown connections > allowing them to finish their work before the server is going out. > This could be done by issuing a close from Server to client on all the > connections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-52) Graceful Shutdown
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-52: Fix Version/s: (was: 6.1.0) 6.0.0 > Graceful Shutdown > - > > Key: ACTIVEMQ6-52 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-52 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: clebert suconic >Assignee: Justin Bertram > Fix For: 6.0.0 > > > We should provide a way for the system to gracefully shutdown connections > allowing them to finish their work before the server is going out. > This could be done by issuing a close from Server to client on all the > connections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-52) Graceful Shutdown
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-52: Fix Version/s: (was: 6.0.0) 6.1.0 > Graceful Shutdown > - > > Key: ACTIVEMQ6-52 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-52 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: clebert suconic >Assignee: Justin Bertram > Fix For: 6.1.0 > > > We should provide a way for the system to gracefully shutdown connections > allowing them to finish their work before the server is going out. > This could be done by issuing a close from Server to client on all the > connections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ACTIVEMQ6-52) Graceful Shutdown
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ACTIVEMQ6-52: --- Assignee: Justin Bertram > Graceful Shutdown > - > > Key: ACTIVEMQ6-52 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-52 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: clebert suconic >Assignee: Justin Bertram > Fix For: 6.0.0 > > > We should provide a way for the system to gracefully shutdown connections > allowing them to finish their work before the server is going out. > This could be done by issuing a close from Server to client on all the > connections. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-11) Fix the distribution build
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280520#comment-14280520 ] Justin Bertram commented on ACTIVEMQ6-11: - Is there anything left to do on the distribution or can this be resolved? > Fix the distribution build > --- > > Key: ACTIVEMQ6-11 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-11 > Project: Apache ActiveMQ 6 > Issue Type: Improvement >Reporter: Martyn Taylor >Assignee: Andy Taylor > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-12) Compare and Contrast ActiveMQ6 and ActiveMQ 5.X embedability.
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-12: Summary: Compare and Contrast ActiveMQ6 and ActiveMQ 5.X embedability. (was: Compare and Contract ActiveMQ6 and ActiveMQ 5.X embedability.) > Compare and Contrast ActiveMQ6 and ActiveMQ 5.X embedability. > - > > Key: ACTIVEMQ6-12 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-12 > Project: Apache ActiveMQ 6 > Issue Type: Task >Reporter: Martyn Taylor > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-43) Replace License Headers on codebase
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280389#comment-14280389 ] Justin Bertram commented on ACTIVEMQ6-43: - Isn't this one done, Howard? > Replace License Headers on codebase > --- > > Key: ACTIVEMQ6-43 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-43 > Project: Apache ActiveMQ 6 > Issue Type: Task >Reporter: clebert suconic >Assignee: Howard Gao >Priority: Critical > Fix For: 6.0.0 > > > The code was relicensed / donated to Apache, hence we need to replace the old > license headers. > I suggest we use this one, taken / copied from Apollo... I think it's a no > brainer and nobody would object it.. but if anyone objects is please let us > know here: > /** > * Licensed to the Apache Software Foundation (ASF) under one or more > * contributor license agreements. See the NOTICE file distributed with > * this work for additional information regarding copyright ownership. > * The ASF licenses this file to You under the Apache License, Version 2.0 > * (the "License"); you may not use this file except in compliance with > * the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations under the License. > */ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-69) Remove all deprecated methods and configuration properties
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-69. - Resolution: Done > Remove all deprecated methods and configuration properties > -- > > Key: ACTIVEMQ6-69 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-69 > Project: Apache ActiveMQ 6 > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > > This is a "fresh start" for the HornetQ code-base so we should remove all > previously deprecated methods and configuration properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-69) Remove all deprecated methods and configuration properties
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280381#comment-14280381 ] Justin Bertram commented on ACTIVEMQ6-69: - https://github.com/apache/activemq-6/pull/64 > Remove all deprecated methods and configuration properties > -- > > Key: ACTIVEMQ6-69 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-69 > Project: Apache ActiveMQ 6 > Issue Type: Task >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > > This is a "fresh start" for the HornetQ code-base so we should remove all > previously deprecated methods and configuration properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-69) Remove all deprecated methods and configuration properties
Justin Bertram created ACTIVEMQ6-69: --- Summary: Remove all deprecated methods and configuration properties Key: ACTIVEMQ6-69 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-69 Project: Apache ActiveMQ 6 Issue Type: Task Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 6.0.0 This is a "fresh start" for the HornetQ code-base so we should remove all previously deprecated methods and configuration properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-13) Implement automatic creation of JMS queues on send or consume
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-13. - Resolution: Implemented > Implement automatic creation of JMS queues on send or consume > - > > Key: ACTIVEMQ6-13 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-13 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ACTIVEMQ6-13) Implement automatic creation of JMS queues on send or consume
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265030#comment-14265030 ] Justin Bertram edited comment on ACTIVEMQ6-13 at 1/13/15 11:15 PM: --- Requirements: * auto-create JMS queue on send or consume * auto-delete auto-created JMS queue if messageCount == 0 && consumerCount == 0 was (Author: jbertram): Requirements: * auto-create destination on send or subscribe * auto-delete destination after configurable amount of time if messageCount == 0 && consumerCount == 0 > Implement automatic creation of JMS queues on send or consume > - > > Key: ACTIVEMQ6-13 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-13 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-13) Implement automatic creation of JMS queues on send or consume
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-13: Summary: Implement automatic creation of JMS queues on send or consume (was: Investigate auto destination creation support) > Implement automatic creation of JMS queues on send or consume > - > > Key: ACTIVEMQ6-13 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-13 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-13) Investigate auto destination creation support
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265669#comment-14265669 ] Justin Bertram commented on ACTIVEMQ6-13: - At this point there's no intention of making auto-created destinations transient so I think you can rest easy about that. I still plan on implementing the ability to auto-delete the auto-created destinations in a configurable way. If you don't want to auto-delete your auto-created destinations then you'll have that choice. My plan here is based on feed-back I've received from developers who worked on ActiveMQ 5 who said this would be a good idea and because this has already been implemented in Apollo which was formerly going to be ActiveMQ 6. As far as whether or not javax.jms.Session.createQueue(String) is a no-op with regard to server communication, that may be implemented as part of this JIRA and it may not. It depends on how the implementation works out, and right now it's not a hard requirement. > Investigate auto destination creation support > - > > Key: ACTIVEMQ6-13 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-13 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-13) Investigate auto destination creation support
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265181#comment-14265181 ] Justin Bertram commented on ACTIVEMQ6-13: - This isn't quite the same as HORNETQ-302 since we're not trying to use the JMS API here to create the destination administratively. This JIRA is just to implement the requirements listed in my comment above. > Investigate auto destination creation support > - > > Key: ACTIVEMQ6-13 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-13 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-13) Investigate auto destination creation support
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265073#comment-14265073 ] Justin Bertram commented on ACTIVEMQ6-13: - Any consumer (including an MDB) attached to the queue would prevent deletion since the consumerCount would be > 0. > Investigate auto destination creation support > - > > Key: ACTIVEMQ6-13 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-13 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-13) Investigate auto destination creation support
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265030#comment-14265030 ] Justin Bertram commented on ACTIVEMQ6-13: - Requirements: * auto-create destination on send or subscribe * auto-delete destination after configurable amount of time if messageCount == 0 && consumerCount == 0 > Investigate auto destination creation support > - > > Key: ACTIVEMQ6-13 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-13 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ACTIVEMQ6-13) Investigate auto destination creation support
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ACTIVEMQ6-13: --- Assignee: Justin Bertram > Investigate auto destination creation support > - > > Key: ACTIVEMQ6-13 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-13 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-63) Add links to examples to website
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-63. - Resolution: Fixed https://github.com/apache/activemq-6/commit/1a5ea5a029bd55a99cbed92b8ef09170e302e5a3 > Add links to examples to website > > > Key: ACTIVEMQ6-63 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-63 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-62) Remove unneeded dependency on jackson
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-62. - Resolution: Fixed https://github.com/apache/activemq-6/commit/f0d18816675197fc51c8f424cada2b60621adf28 > Remove unneeded dependency on jackson > - > > Key: ACTIVEMQ6-62 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-62 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > Fix For: 6.0.0 > > > The dependency on jackson in the activemq-dto module looks unnecessary for > our purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-63) Add links to examples to website
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-63: Affects Version/s: (was: 6.0.0) > Add links to examples to website > > > Key: ACTIVEMQ6-63 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-63 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-63) Add links to examples to website
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-63: Fix Version/s: 6.0.0 > Add links to examples to website > > > Key: ACTIVEMQ6-63 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-63 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-63) Add links to examples to website
Justin Bertram created ACTIVEMQ6-63: --- Summary: Add links to examples to website Key: ACTIVEMQ6-63 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-63 Project: Apache ActiveMQ 6 Issue Type: Bug Affects Versions: 6.0.0 Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-62) Remove unneeded dependency on jackson
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-62: Fix Version/s: 6.0.0 > Remove unneeded dependency on jackson > - > > Key: ACTIVEMQ6-62 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-62 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > Fix For: 6.0.0 > > > The dependency on jackson in the activemq-dto module looks unnecessary for > our purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-62) Remove unneeded dependency on jackson
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-62: Description: The dependency on jackson in the activemq-dto module looks unnecessary for our purposes. (was: This dependency on jackson looks unnecessary for our purposes.) > Remove unneeded dependency on jackson > - > > Key: ACTIVEMQ6-62 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-62 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > > The dependency on jackson in the activemq-dto module looks unnecessary for > our purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-62) Remove unneeded dependency on jackson
Justin Bertram created ACTIVEMQ6-62: --- Summary: Remove unneeded dependency on jackson Key: ACTIVEMQ6-62 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-62 Project: Apache ActiveMQ 6 Issue Type: Bug Reporter: Justin Bertram Assignee: Justin Bertram Priority: Minor This dependency on jackson looks unnecessary for our purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-12) Compare and Contract ActiveMQ6 and ActiveMQ 5.X embedability.
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244889#comment-14244889 ] Justin Bertram commented on ACTIVEMQ6-12: - For reference I compared [HornetQ embeddability|http://docs.jboss.org/hornetq/2.4.0.Final/docs/user-manual/html/embedding-hornetq.html] and [ActiveMQ 5.x embeddability|http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-connection.html]. ActiveMQ 5.x has more options than HornetQ, e.g.: * BrokerFactory which can use a URI for configuration * Starting/configuring a broker in response to a connection That said, I'm not sure how popular each of these options is and whether or not it makes sense to reproduce them in ActiveMQ 6. The auto-creation of destinations probably the biggest win for embeddability and ease of use that I see at this point. > Compare and Contract ActiveMQ6 and ActiveMQ 5.X embedability. > - > > Key: ACTIVEMQ6-12 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-12 > Project: Apache ActiveMQ 6 > Issue Type: Task >Reporter: Martyn Taylor > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ACTIVEMQ6-12) Compare and Contract ActiveMQ6 and ActiveMQ 5.X embedability.
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243246#comment-14243246 ] Justin Bertram edited comment on ACTIVEMQ6-12 at 12/11/14 10:13 PM: What exactly is required for this task? Is this just for documentation purposes or do we want to change ActiveMQ 6 to be more like 5.x? was (Author: jbertram): What exactly is required for this task? > Compare and Contract ActiveMQ6 and ActiveMQ 5.X embedability. > - > > Key: ACTIVEMQ6-12 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-12 > Project: Apache ActiveMQ 6 > Issue Type: Task >Reporter: Martyn Taylor > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-12) Compare and Contract ActiveMQ6 and ActiveMQ 5.X embedability.
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243246#comment-14243246 ] Justin Bertram commented on ACTIVEMQ6-12: - What exactly is required for this task? > Compare and Contract ActiveMQ6 and ActiveMQ 5.X embedability. > - > > Key: ACTIVEMQ6-12 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-12 > Project: Apache ActiveMQ 6 > Issue Type: Task >Reporter: Martyn Taylor > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-41) Drop Java EE examples
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-41. - Resolution: Fixed > Drop Java EE examples > - > > Key: ACTIVEMQ6-41 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-41 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Affects Versions: 6.0.0 >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > > The Java EE examples should reside with individual application servers, not > with ActiveMQ. For example, Wildfly already has a set of quick-start > examples for JMS. Our existing examples can be ported there if necessary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-51) Fix how examples are bootstrapping the servers
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-51. - Resolution: Fixed > Fix how examples are bootstrapping the servers > -- > > Key: ACTIVEMQ6-51 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-51 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Howard Gao >Assignee: Justin Bertram > Fix For: 6.0.0 > > > ActiveMQ6 examples uses hornetq-maven-plugin to start/stop server, we need to > migrate this plugin over to apache. > https://github.com/hornetq/maven-hornetq-plugin > Find a place to host this project alongside amq6 repo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ACTIVEMQ6-51) Fix how examples are bootstrapping the servers
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ACTIVEMQ6-51: --- Assignee: Justin Bertram > Fix how examples are bootstrapping the servers > -- > > Key: ACTIVEMQ6-51 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-51 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Howard Gao >Assignee: Justin Bertram > Fix For: 6.0.0 > > > ActiveMQ6 examples uses hornetq-maven-plugin to start/stop server, we need to > migrate this plugin over to apache. > https://github.com/hornetq/maven-hornetq-plugin > Find a place to host this project alongside amq6 repo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACTIVEMQ6-14) Replace naming server with ActiveMQ client JNDI
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ACTIVEMQ6-14. - Resolution: Fixed https://github.com/apache/activemq-6/pull/34 > Replace naming server with ActiveMQ client JNDI > --- > > Key: ACTIVEMQ6-14 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-14 > Project: Apache ActiveMQ 6 > Issue Type: Improvement >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (ACTIVEMQ6-14) Replace naming server with ActiveMQ client JNDI
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ACTIVEMQ6-14 started by Justin Bertram. --- > Replace naming server with ActiveMQ client JNDI > --- > > Key: ACTIVEMQ6-14 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-14 > Project: Apache ActiveMQ 6 > Issue Type: Improvement >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ACTIVEMQ6-14) Replace naming server with ActiveMQ client JNDI
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ACTIVEMQ6-14: --- Assignee: Justin Bertram > Replace naming server with ActiveMQ client JNDI > --- > > Key: ACTIVEMQ6-14 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-14 > Project: Apache ActiveMQ 6 > Issue Type: Improvement >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-35) expose configuration to deploy web server
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218337#comment-14218337 ] Justin Bertram commented on ACTIVEMQ6-35: - Thought about using Undertow here? It is ASL 2.0. > expose configuration to deploy web server > - > > Key: ACTIVEMQ6-35 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-35 > Project: Apache ActiveMQ 6 > Issue Type: New Feature >Reporter: Andy Taylor >Assignee: Andy Taylor > > This will allow a web server to be deployed via the main configuration so we > can expose web apps and demos similar to ActiveMQ5. we will need this for > https://issues.apache.org/jira/browse/ACTIVEMQ6-15 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-41) Drop Java EE examples
Justin Bertram created ACTIVEMQ6-41: --- Summary: Drop Java EE examples Key: ACTIVEMQ6-41 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-41 Project: Apache ActiveMQ 6 Issue Type: Bug Affects Versions: 6.0.0 Reporter: Justin Bertram Assignee: Justin Bertram The Java EE examples should reside with individual application servers, not with ActiveMQ. For example, Wildfly already has a set of quick-start examples for JMS. Our existing examples can be ported there if necessary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACTIVEMQ6-9) Fix Documentation to remove any non ActiveMQ references / branding
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217310#comment-14217310 ] Justin Bertram commented on ACTIVEMQ6-9: https://github.com/apache/activemq-6/commit/e7a3e7d25b11b65b09dd33b927689984f9d63274 > Fix Documentation to remove any non ActiveMQ references / branding > -- > > Key: ACTIVEMQ6-9 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-9 > Project: Apache ActiveMQ 6 > Issue Type: Improvement >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ACTIVEMQ6-10) Remove JBoss 4 integration (hornetq-service-sar).
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ACTIVEMQ6-10. --- Resolution: Fixed https://github.com/apache/activemq-6/commit/079e4b24387c78ffbbcf52878949e6bf2bf1d506 > Remove JBoss 4 integration (hornetq-service-sar). > - > > Key: ACTIVEMQ6-10 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-10 > Project: Apache ActiveMQ 6 > Issue Type: Improvement >Reporter: Martyn Taylor >Assignee: Martyn Taylor > Fix For: 6.0.0 > > > The initial donation has some old JBoss code on it that we need to get rid of > as we move forward -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ACTIVEMQ6-9) Fix Documentation to remove any non ActiveMQ references / branding
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ACTIVEMQ6-9. -- Resolution: Fixed > Fix Documentation to remove any non ActiveMQ references / branding > -- > > Key: ACTIVEMQ6-9 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-9 > Project: Apache ActiveMQ 6 > Issue Type: Improvement >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-39) Rename all HornetQ* classes to ActiveMQ*
Justin Bertram created ACTIVEMQ6-39: --- Summary: Rename all HornetQ* classes to ActiveMQ* Key: ACTIVEMQ6-39 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-39 Project: Apache ActiveMQ 6 Issue Type: Bug Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ACTIVEMQ6-9) Fix Documentation to remove any non ActiveMQ references / branding
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ACTIVEMQ6-9: -- Assignee: Justin Bertram > Fix Documentation to remove any non ActiveMQ references / branding > -- > > Key: ACTIVEMQ6-9 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-9 > Project: Apache ActiveMQ 6 > Issue Type: Improvement >Reporter: Martyn Taylor >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ACTIVEMQ6-38) Overzealous logging for missing queue
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ACTIVEMQ6-38. --- Resolution: Fixed https://github.com/apache/activemq-6/commit/2d9125a7c61999ed2aaa7c14d0fd3fe2b9a5d19d > Overzealous logging for missing queue > - > > Key: ACTIVEMQ6-38 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-38 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACTIVEMQ6-38) Overzealous logging for missing queue
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ACTIVEMQ6-38: Affects Version/s: (was: 6.0.0) Fix Version/s: 6.0.0 > Overzealous logging for missing queue > - > > Key: ACTIVEMQ6-38 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-38 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ACTIVEMQ6-37) NoSuchMethodError during init
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ACTIVEMQ6-37. --- Resolution: Fixed https://github.com/apache/activemq-6/commit/8fcf81f5f7a59478a67d9a042c9456bffef58ca6 > NoSuchMethodError during init > - > > Key: ACTIVEMQ6-37 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-37 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > > When compiled by JDK 8 targeting Java 6 and then run on JDK 6 or 7 the > ConcurrentHashMap#keyset() method can fail because the return types changed > in Java 8. Using ConcurrentMap interface to resolve the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (ACTIVEMQ6-36) Disallow use of SSLv3 to protect against POODLE
[ https://issues.apache.org/jira/browse/ACTIVEMQ6-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ACTIVEMQ6-36. --- Resolution: Fixed https://github.com/apache/activemq-6/commit/36d86ffb00f6f152ed6daf7cf16f6f1556573ba7 > Disallow use of SSLv3 to protect against POODLE > --- > > Key: ACTIVEMQ6-36 > URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-36 > Project: Apache ActiveMQ 6 > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram > Fix For: 6.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-38) Overzealous logging for missing queue
Justin Bertram created ACTIVEMQ6-38: --- Summary: Overzealous logging for missing queue Key: ACTIVEMQ6-38 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-38 Project: Apache ActiveMQ 6 Issue Type: Bug Affects Versions: 6.0.0 Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-37) NoSuchMethodError during init
Justin Bertram created ACTIVEMQ6-37: --- Summary: NoSuchMethodError during init Key: ACTIVEMQ6-37 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-37 Project: Apache ActiveMQ 6 Issue Type: Bug Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 6.0.0 When compiled by JDK 8 targeting Java 6 and then run on JDK 6 or 7 the ConcurrentHashMap#keyset() method can fail because the return types changed in Java 8. Using ConcurrentMap interface to resolve the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ACTIVEMQ6-36) Disallow use of SSLv3 to protect against POODLE
Justin Bertram created ACTIVEMQ6-36: --- Summary: Disallow use of SSLv3 to protect against POODLE Key: ACTIVEMQ6-36 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-36 Project: Apache ActiveMQ 6 Issue Type: Bug Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 6.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
