[jira] [Created] (AMQ-7325) Upgrade to derby 10.15.1.3
Jean-Baptiste Onofré created AMQ-7325: - Summary: Upgrade to derby 10.15.1.3 Key: AMQ-7325 URL: https://issues.apache.org/jira/browse/AMQ-7325 Project: ActiveMQ Issue Type: Task Components: Broker Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 5.16.0, 5.15.11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMQ-7324) Upgrade to commons-dbcp/commons-pool 2.7.0
Jean-Baptiste Onofré created AMQ-7324: - Summary: Upgrade to commons-dbcp/commons-pool 2.7.0 Key: AMQ-7324 URL: https://issues.apache.org/jira/browse/AMQ-7324 Project: ActiveMQ Issue Type: Task Components: Broker Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 5.16.0, 5.15.11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMQ-7323) Upgrade to rome 1.12.2
Jean-Baptiste Onofré created AMQ-7323: - Summary: Upgrade to rome 1.12.2 Key: AMQ-7323 URL: https://issues.apache.org/jira/browse/AMQ-7323 Project: ActiveMQ Issue Type: Task Components: Broker Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 5.16.0, 5.15.11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMQ-7068) Advisory messages are empty when received with a AMQP subscription
[ https://issues.apache.org/jira/browse/AMQ-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-7068: - Assignee: Jean-Baptiste Onofré > Advisory messages are empty when received with a AMQP subscription > -- > > Key: AMQ-7068 > URL: https://issues.apache.org/jira/browse/AMQ-7068 > Project: ActiveMQ > Issue Type: New Feature > Components: AMQP, Transport >Affects Versions: 5.15.6 > Environment: ActiveMQ 5.15.6, JDK 1.8.0_161, Windows 10, AMQPNetLite > 2.1.4 >Reporter: Johannes Baeurle >Assignee: Jean-Baptiste Onofré >Priority: Minor > Attachments: issueamq.PNG, issueamq2.PNG, issueamq3.PNG > > > We are currently moving from OpenWire to AMQP with .NET Library amqpnetlite > ([https://github.com/Azure/amqpnetlite)] to communicate. So far most things > work fine, but we actively used and need the advisory messages in order to > recognize if other clients disconnect for example. > Accessing the advisory messages through the topic is not the problem, but the > body is null for the ActiveMQ.Advisory.Connection topic. There are some > properties set, but no body set and I'm not able to find any important > information, like the RemoveInfo. I attached a few screenshots from debugger. > To be honest, I don't know if this is the desired behavior, but I think if > there are messages on the advisory topic they should be useful. > I know that a byte representation wouldn't be that useful, but you could > present the information in json or xml format, like in Stomp? > (https://issues.apache.org/jira/browse/AMQ-2098) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMQ-7068) Advisory messages are empty when received with a AMQP subscription
[ https://issues.apache.org/jira/browse/AMQ-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7068: -- Fix Version/s: 5.15.11 5.16.0 > Advisory messages are empty when received with a AMQP subscription > -- > > Key: AMQ-7068 > URL: https://issues.apache.org/jira/browse/AMQ-7068 > Project: ActiveMQ > Issue Type: New Feature > Components: AMQP, Transport >Affects Versions: 5.15.6 > Environment: ActiveMQ 5.15.6, JDK 1.8.0_161, Windows 10, AMQPNetLite > 2.1.4 >Reporter: Johannes Baeurle >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 5.16.0, 5.15.11 > > Attachments: issueamq.PNG, issueamq2.PNG, issueamq3.PNG > > > We are currently moving from OpenWire to AMQP with .NET Library amqpnetlite > ([https://github.com/Azure/amqpnetlite)] to communicate. So far most things > work fine, but we actively used and need the advisory messages in order to > recognize if other clients disconnect for example. > Accessing the advisory messages through the topic is not the problem, but the > body is null for the ActiveMQ.Advisory.Connection topic. There are some > properties set, but no body set and I'm not able to find any important > information, like the RemoveInfo. I attached a few screenshots from debugger. > To be honest, I don't know if this is the desired behavior, but I think if > there are messages on the advisory topic they should be useful. > I know that a byte representation wouldn't be that useful, but you could > present the information in json or xml format, like in Stomp? > (https://issues.apache.org/jira/browse/AMQ-2098) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7118) KahaDB store limit can be exceeded with durable subscribers.
[ https://issues.apache.org/jira/browse/AMQ-7118?focusedWorklogId=330717&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330717 ] ASF GitHub Bot logged work on AMQ-7118: --- Author: ASF GitHub Bot Created on: 18/Oct/19 18:49 Start Date: 18/Oct/19 18:49 Worklog Time Spent: 10m Work Description: jbonofre commented on issue #326: AMQ-7118: fix issue with the unchanged acknowledgement map. URL: https://github.com/apache/activemq/pull/326#issuecomment-543885060 It has been already applied. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 330717) Remaining Estimate: 0h Time Spent: 10m > KahaDB store limit can be exceeded with durable subscribers. > > > Key: AMQ-7118 > URL: https://issues.apache.org/jira/browse/AMQ-7118 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.16.0, 5.15.8 > Environment: JDK 8 >Reporter: Jamie Mark Goodyear >Priority: Critical > Fix For: 5.16.0, 5.15.8 > > Attachments: kahaCommands.jpg > > Time Spent: 10m > Remaining Estimate: 0h > > KahaDB store limit can be exceeded with durable subscribers. > AMQ with store limit set, we can observe that the usage continues to increase > AFTER PFC is engaged. Given time, this growth stabilizes. The issue of having > exceeded the store limit remains. > See below output from KahaDB dump in attachments: > This appears to be caused by checkpointAckMessageFileMap. The log files are > not GC'd, and the KAHA_ACK_MESSAGE_FILE_MAP_COMMAND is replicated and the DB > log files continue to expand - this can become exponential. Side effect of > also not checking storage size in checkpoint update can cause the DB log > files to exceed any set limits. The real critical part is the duplicated and > leaking Kaha messages which appears to happen with durable subscribers. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7118) KahaDB store limit can be exceeded with durable subscribers.
[ https://issues.apache.org/jira/browse/AMQ-7118?focusedWorklogId=330718&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330718 ] ASF GitHub Bot logged work on AMQ-7118: --- Author: ASF GitHub Bot Created on: 18/Oct/19 18:49 Start Date: 18/Oct/19 18:49 Worklog Time Spent: 10m Work Description: jbonofre commented on pull request #326: AMQ-7118: fix issue with the unchanged acknowledgement map. URL: https://github.com/apache/activemq/pull/326 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 330718) Time Spent: 20m (was: 10m) > KahaDB store limit can be exceeded with durable subscribers. > > > Key: AMQ-7118 > URL: https://issues.apache.org/jira/browse/AMQ-7118 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.16.0, 5.15.8 > Environment: JDK 8 >Reporter: Jamie Mark Goodyear >Priority: Critical > Fix For: 5.16.0, 5.15.8 > > Attachments: kahaCommands.jpg > > Time Spent: 20m > Remaining Estimate: 0h > > KahaDB store limit can be exceeded with durable subscribers. > AMQ with store limit set, we can observe that the usage continues to increase > AFTER PFC is engaged. Given time, this growth stabilizes. The issue of having > exceeded the store limit remains. > See below output from KahaDB dump in attachments: > This appears to be caused by checkpointAckMessageFileMap. The log files are > not GC'd, and the KAHA_ACK_MESSAGE_FILE_MAP_COMMAND is replicated and the DB > log files continue to expand - this can become exponential. Side effect of > also not checking storage size in checkpoint update can cause the DB log > files to exceed any set limits. The real critical part is the duplicated and > leaking Kaha messages which appears to happen with durable subscribers. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7055) Small optimization on SequenceSet to prevent iterating through the whole set when a value bigger than the last value is added
[ https://issues.apache.org/jira/browse/AMQ-7055?focusedWorklogId=330709&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330709 ] ASF GitHub Bot logged work on AMQ-7055: --- Author: ASF GitHub Bot Created on: 18/Oct/19 18:45 Start Date: 18/Oct/19 18:45 Worklog Time Spent: 10m Work Description: jbonofre commented on issue #300: AMQ-7055 - Optimization on SequenceSet to prevent iterating through t… URL: https://github.com/apache/activemq/pull/300#issuecomment-543883392 This change has been already applied. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 330709) Remaining Estimate: 0h Time Spent: 10m > Small optimization on SequenceSet to prevent iterating through the whole set > when a value bigger than the last value is added > - > > Key: AMQ-7055 > URL: https://issues.apache.org/jira/browse/AMQ-7055 > Project: ActiveMQ > Issue Type: Improvement > Components: KahaDB >Affects Versions: 5.15.6 >Reporter: Alan Protasio >Assignee: Gary Tully >Priority: Minor > Fix For: 5.16.0, 5.15.7 > > Time Spent: 10m > Remaining Estimate: 0h > > When the index file has a huge number of free pages and the broker is > starting up (loading the index) we end up in a O(n2) loop. > This was causing the broker to use 100% cpu and not being able to start up > even after a long time (as i remember we had around 3 millions free page in > this case) > [https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/disk/page/PageFile.java#L428] > https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/disk/util/SequenceSet.java#L118 > I noticed that almost all the free pages was being added to the end of the > sequenceSet... So for any free page the broker had to necessity iterate > through all the Set (and after doing that for nothing add . the value to the > tail). > With this small change, the broker started up in less than 5 minutes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7055) Small optimization on SequenceSet to prevent iterating through the whole set when a value bigger than the last value is added
[ https://issues.apache.org/jira/browse/AMQ-7055?focusedWorklogId=330710&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330710 ] ASF GitHub Bot logged work on AMQ-7055: --- Author: ASF GitHub Bot Created on: 18/Oct/19 18:45 Start Date: 18/Oct/19 18:45 Worklog Time Spent: 10m Work Description: jbonofre commented on pull request #300: AMQ-7055 - Optimization on SequenceSet to prevent iterating through t… URL: https://github.com/apache/activemq/pull/300 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 330710) Time Spent: 20m (was: 10m) > Small optimization on SequenceSet to prevent iterating through the whole set > when a value bigger than the last value is added > - > > Key: AMQ-7055 > URL: https://issues.apache.org/jira/browse/AMQ-7055 > Project: ActiveMQ > Issue Type: Improvement > Components: KahaDB >Affects Versions: 5.15.6 >Reporter: Alan Protasio >Assignee: Gary Tully >Priority: Minor > Fix For: 5.16.0, 5.15.7 > > Time Spent: 20m > Remaining Estimate: 0h > > When the index file has a huge number of free pages and the broker is > starting up (loading the index) we end up in a O(n2) loop. > This was causing the broker to use 100% cpu and not being able to start up > even after a long time (as i remember we had around 3 millions free page in > this case) > [https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/disk/page/PageFile.java#L428] > https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/disk/util/SequenceSet.java#L118 > I noticed that almost all the free pages was being added to the end of the > sequenceSet... So for any free page the broker had to necessity iterate > through all the Set (and after doing that for nothing add . the value to the > tail). > With this small change, the broker started up in less than 5 minutes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMQ-7014) Separate Karaf integration from main ActiveMQ feature
[ https://issues.apache.org/jira/browse/AMQ-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7014: -- Fix Version/s: 5.15.11 > Separate Karaf integration from main ActiveMQ feature > - > > Key: AMQ-7014 > URL: https://issues.apache.org/jira/browse/AMQ-7014 > Project: ActiveMQ > Issue Type: Improvement > Components: karaf, OSGi/Karaf >Affects Versions: 5.15.4 >Reporter: Łukasz Dywicki >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 5.16.0, 5.15.11 > > > Currently activemq feature installs also karaf console integration. In some > cases it might be useful to separate these two so console integration is > optional and not crucial in all cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMQ-7312) virtualSelectorCacheBrokerPlugin fails on "browse" action
[ https://issues.apache.org/jira/browse/AMQ-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7312. --- Resolution: Fixed > virtualSelectorCacheBrokerPlugin fails on "browse" action > - > > Key: AMQ-7312 > URL: https://issues.apache.org/jira/browse/AMQ-7312 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.10 >Reporter: Dany LECOQ >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We have a VirtualTopic "VirtualTopic.multi_dest" and 2 consumers : > * Consumer.alpha.VirtualTopic.multi_dest > * Consumer.beta.VirtualTopic.multi_dest > Message producer send messages on that vTopic with various "tenant" header > value. > Each consumer use a selector to receive only desired data : > * tenant='alpha' for Consumer.alpha.VirtualTopic.multi_dest > * tenant='beta' for Consumer.beta.VirtualTopic.multi_dest > To avoid to get many pending message on each consumer queue, we activated > selectorAware="true" in broker settings. > To avoid to lose message on temporary consumer deconnection, we activated > virtualSelectorCacheBrokerPlugin plugin. > Steps to reproduce bug : > * launch message producer and both message consumers alpha and beta > * stop alpha consumer > * notice on console pending messages on alpha queue increase > * if we restart alpha consumer, all pending messages are consumed => ok, > only messages matching selector were in queue > * restop alpha consumer > * go on console and click on "Browse" link for alpha consumer queue > * restart alpha consumer => it will consume pending messages matching > selector > * notice there are other waiting messages that do not match selector, so the > consumer queue is fastly full of useless messages => ko > * even after broker restart, the alpha consumer queue continues to receive > message that do not match selectors => ko > > After code analysis, I notice "Browse" action create a new consumer on queue. > In virtualSelectorCacheBrokerPlugin, the addConsumer method update > "subSelectorCache" variable with 'TRUE' selector. > > A pull request is submitted to fix that issue > ([https://github.com/apache/activemq/pull/395]), could you merge it for the > next patch 5.15.11 ? > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7312) virtualSelectorCacheBrokerPlugin fails on "browse" action
[ https://issues.apache.org/jira/browse/AMQ-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954831#comment-16954831 ] ASF subversion and git services commented on AMQ-7312: -- Commit 1d8ae314bd8a18ed6ed3c0dea0ced08cadb6d1b8 in activemq's branch refs/heads/activemq-5.15.x from Dany LECOQ [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=1d8ae31 ] AMQ-7312 virtualSelectorCacheBrokerPlugin addConsumer issue (cherry picked from commit 86a069ac5db9742ae58e396e162a0b3e2bdc66c3) > virtualSelectorCacheBrokerPlugin fails on "browse" action > - > > Key: AMQ-7312 > URL: https://issues.apache.org/jira/browse/AMQ-7312 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.10 >Reporter: Dany LECOQ >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We have a VirtualTopic "VirtualTopic.multi_dest" and 2 consumers : > * Consumer.alpha.VirtualTopic.multi_dest > * Consumer.beta.VirtualTopic.multi_dest > Message producer send messages on that vTopic with various "tenant" header > value. > Each consumer use a selector to receive only desired data : > * tenant='alpha' for Consumer.alpha.VirtualTopic.multi_dest > * tenant='beta' for Consumer.beta.VirtualTopic.multi_dest > To avoid to get many pending message on each consumer queue, we activated > selectorAware="true" in broker settings. > To avoid to lose message on temporary consumer deconnection, we activated > virtualSelectorCacheBrokerPlugin plugin. > Steps to reproduce bug : > * launch message producer and both message consumers alpha and beta > * stop alpha consumer > * notice on console pending messages on alpha queue increase > * if we restart alpha consumer, all pending messages are consumed => ok, > only messages matching selector were in queue > * restop alpha consumer > * go on console and click on "Browse" link for alpha consumer queue > * restart alpha consumer => it will consume pending messages matching > selector > * notice there are other waiting messages that do not match selector, so the > consumer queue is fastly full of useless messages => ko > * even after broker restart, the alpha consumer queue continues to receive > message that do not match selectors => ko > > After code analysis, I notice "Browse" action create a new consumer on queue. > In virtualSelectorCacheBrokerPlugin, the addConsumer method update > "subSelectorCache" variable with 'TRUE' selector. > > A pull request is submitted to fix that issue > ([https://github.com/apache/activemq/pull/395]), could you merge it for the > next patch 5.15.11 ? > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7312) virtualSelectorCacheBrokerPlugin fails on "browse" action
[ https://issues.apache.org/jira/browse/AMQ-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954827#comment-16954827 ] ASF subversion and git services commented on AMQ-7312: -- Commit 86a069ac5db9742ae58e396e162a0b3e2bdc66c3 in activemq's branch refs/heads/master from Dany LECOQ [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=86a069a ] AMQ-7312 virtualSelectorCacheBrokerPlugin addConsumer issue > virtualSelectorCacheBrokerPlugin fails on "browse" action > - > > Key: AMQ-7312 > URL: https://issues.apache.org/jira/browse/AMQ-7312 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.10 >Reporter: Dany LECOQ >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We have a VirtualTopic "VirtualTopic.multi_dest" and 2 consumers : > * Consumer.alpha.VirtualTopic.multi_dest > * Consumer.beta.VirtualTopic.multi_dest > Message producer send messages on that vTopic with various "tenant" header > value. > Each consumer use a selector to receive only desired data : > * tenant='alpha' for Consumer.alpha.VirtualTopic.multi_dest > * tenant='beta' for Consumer.beta.VirtualTopic.multi_dest > To avoid to get many pending message on each consumer queue, we activated > selectorAware="true" in broker settings. > To avoid to lose message on temporary consumer deconnection, we activated > virtualSelectorCacheBrokerPlugin plugin. > Steps to reproduce bug : > * launch message producer and both message consumers alpha and beta > * stop alpha consumer > * notice on console pending messages on alpha queue increase > * if we restart alpha consumer, all pending messages are consumed => ok, > only messages matching selector were in queue > * restop alpha consumer > * go on console and click on "Browse" link for alpha consumer queue > * restart alpha consumer => it will consume pending messages matching > selector > * notice there are other waiting messages that do not match selector, so the > consumer queue is fastly full of useless messages => ko > * even after broker restart, the alpha consumer queue continues to receive > message that do not match selectors => ko > > After code analysis, I notice "Browse" action create a new consumer on queue. > In virtualSelectorCacheBrokerPlugin, the addConsumer method update > "subSelectorCache" variable with 'TRUE' selector. > > A pull request is submitted to fix that issue > ([https://github.com/apache/activemq/pull/395]), could you merge it for the > next patch 5.15.11 ? > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7312) virtualSelectorCacheBrokerPlugin fails on "browse" action
[ https://issues.apache.org/jira/browse/AMQ-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954829#comment-16954829 ] ASF subversion and git services commented on AMQ-7312: -- Commit a5f06025057afb927d00c941412d1143c8614098 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=a5f0602 ] Merge pull request #395 from couclock/AMQ-7312 AMQ-7312 virtualSelectorCacheBrokerPlugin addConsumer issue > virtualSelectorCacheBrokerPlugin fails on "browse" action > - > > Key: AMQ-7312 > URL: https://issues.apache.org/jira/browse/AMQ-7312 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.10 >Reporter: Dany LECOQ >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We have a VirtualTopic "VirtualTopic.multi_dest" and 2 consumers : > * Consumer.alpha.VirtualTopic.multi_dest > * Consumer.beta.VirtualTopic.multi_dest > Message producer send messages on that vTopic with various "tenant" header > value. > Each consumer use a selector to receive only desired data : > * tenant='alpha' for Consumer.alpha.VirtualTopic.multi_dest > * tenant='beta' for Consumer.beta.VirtualTopic.multi_dest > To avoid to get many pending message on each consumer queue, we activated > selectorAware="true" in broker settings. > To avoid to lose message on temporary consumer deconnection, we activated > virtualSelectorCacheBrokerPlugin plugin. > Steps to reproduce bug : > * launch message producer and both message consumers alpha and beta > * stop alpha consumer > * notice on console pending messages on alpha queue increase > * if we restart alpha consumer, all pending messages are consumed => ok, > only messages matching selector were in queue > * restop alpha consumer > * go on console and click on "Browse" link for alpha consumer queue > * restart alpha consumer => it will consume pending messages matching > selector > * notice there are other waiting messages that do not match selector, so the > consumer queue is fastly full of useless messages => ko > * even after broker restart, the alpha consumer queue continues to receive > message that do not match selectors => ko > > After code analysis, I notice "Browse" action create a new consumer on queue. > In virtualSelectorCacheBrokerPlugin, the addConsumer method update > "subSelectorCache" variable with 'TRUE' selector. > > A pull request is submitted to fix that issue > ([https://github.com/apache/activemq/pull/395]), could you merge it for the > next patch 5.15.11 ? > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7312) virtualSelectorCacheBrokerPlugin fails on "browse" action
[ https://issues.apache.org/jira/browse/AMQ-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954828#comment-16954828 ] ASF subversion and git services commented on AMQ-7312: -- Commit a5f06025057afb927d00c941412d1143c8614098 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=a5f0602 ] Merge pull request #395 from couclock/AMQ-7312 AMQ-7312 virtualSelectorCacheBrokerPlugin addConsumer issue > virtualSelectorCacheBrokerPlugin fails on "browse" action > - > > Key: AMQ-7312 > URL: https://issues.apache.org/jira/browse/AMQ-7312 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.10 >Reporter: Dany LECOQ >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We have a VirtualTopic "VirtualTopic.multi_dest" and 2 consumers : > * Consumer.alpha.VirtualTopic.multi_dest > * Consumer.beta.VirtualTopic.multi_dest > Message producer send messages on that vTopic with various "tenant" header > value. > Each consumer use a selector to receive only desired data : > * tenant='alpha' for Consumer.alpha.VirtualTopic.multi_dest > * tenant='beta' for Consumer.beta.VirtualTopic.multi_dest > To avoid to get many pending message on each consumer queue, we activated > selectorAware="true" in broker settings. > To avoid to lose message on temporary consumer deconnection, we activated > virtualSelectorCacheBrokerPlugin plugin. > Steps to reproduce bug : > * launch message producer and both message consumers alpha and beta > * stop alpha consumer > * notice on console pending messages on alpha queue increase > * if we restart alpha consumer, all pending messages are consumed => ok, > only messages matching selector were in queue > * restop alpha consumer > * go on console and click on "Browse" link for alpha consumer queue > * restart alpha consumer => it will consume pending messages matching > selector > * notice there are other waiting messages that do not match selector, so the > consumer queue is fastly full of useless messages => ko > * even after broker restart, the alpha consumer queue continues to receive > message that do not match selectors => ko > > After code analysis, I notice "Browse" action create a new consumer on queue. > In virtualSelectorCacheBrokerPlugin, the addConsumer method update > "subSelectorCache" variable with 'TRUE' selector. > > A pull request is submitted to fix that issue > ([https://github.com/apache/activemq/pull/395]), could you merge it for the > next patch 5.15.11 ? > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7312) virtualSelectorCacheBrokerPlugin fails on "browse" action
[ https://issues.apache.org/jira/browse/AMQ-7312?focusedWorklogId=330657&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330657 ] ASF GitHub Bot logged work on AMQ-7312: --- Author: ASF GitHub Bot Created on: 18/Oct/19 17:09 Start Date: 18/Oct/19 17:09 Worklog Time Spent: 10m Work Description: jbonofre commented on pull request #395: AMQ-7312 virtualSelectorCacheBrokerPlugin addConsumer issue URL: https://github.com/apache/activemq/pull/395 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 330657) Time Spent: 20m (was: 10m) > virtualSelectorCacheBrokerPlugin fails on "browse" action > - > > Key: AMQ-7312 > URL: https://issues.apache.org/jira/browse/AMQ-7312 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.10 >Reporter: Dany LECOQ >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We have a VirtualTopic "VirtualTopic.multi_dest" and 2 consumers : > * Consumer.alpha.VirtualTopic.multi_dest > * Consumer.beta.VirtualTopic.multi_dest > Message producer send messages on that vTopic with various "tenant" header > value. > Each consumer use a selector to receive only desired data : > * tenant='alpha' for Consumer.alpha.VirtualTopic.multi_dest > * tenant='beta' for Consumer.beta.VirtualTopic.multi_dest > To avoid to get many pending message on each consumer queue, we activated > selectorAware="true" in broker settings. > To avoid to lose message on temporary consumer deconnection, we activated > virtualSelectorCacheBrokerPlugin plugin. > Steps to reproduce bug : > * launch message producer and both message consumers alpha and beta > * stop alpha consumer > * notice on console pending messages on alpha queue increase > * if we restart alpha consumer, all pending messages are consumed => ok, > only messages matching selector were in queue > * restop alpha consumer > * go on console and click on "Browse" link for alpha consumer queue > * restart alpha consumer => it will consume pending messages matching > selector > * notice there are other waiting messages that do not match selector, so the > consumer queue is fastly full of useless messages => ko > * even after broker restart, the alpha consumer queue continues to receive > message that do not match selectors => ko > > After code analysis, I notice "Browse" action create a new consumer on queue. > In virtualSelectorCacheBrokerPlugin, the addConsumer method update > "subSelectorCache" variable with 'TRUE' selector. > > A pull request is submitted to fix that issue > ([https://github.com/apache/activemq/pull/395]), could you merge it for the > next patch 5.15.11 ? > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7130) bug tracking link is pointing to wrong url
[ https://issues.apache.org/jira/browse/AMQ-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954826#comment-16954826 ] ASF subversion and git services commented on AMQ-7130: -- Commit 506ededc32d968a0fcd5560d2d9f27d97b66ebda in activemq's branch refs/heads/activemq-5.15.x from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=506eded ] AMQ-7130 Update AMQ doap (cherry picked from commit d525096cac444189c2d233e1de47342f1916c82d) > bug tracking link is pointing to wrong url > -- > > Key: AMQ-7130 > URL: https://issues.apache.org/jira/browse/AMQ-7130 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 5.15.8 > Environment: MacOS High Sierra, 10.13.6 > Processor: 2.8 GHz Intel Core i7 > Memory: 16 GB 2133 MHz LPDDR3 > Graphics: Intel HD Graphics 630 1536 MB > > >Reporter: Shubham Gupta >Assignee: Jean-Baptiste Onofré >Priority: Minor > Labels: documentation > Fix For: 5.x > > Original Estimate: 168h > Time Spent: 20m > Remaining Estimate: 167h 40m > > Hello, > I was browsing through the documentation. I landed up in the page-> > [https://projects.apache.org/project.html?activemq|https://projects.apache.org/project.html?activemq.] > In the Bug-Tracking: [http://issues.apache.org/activemq/browse/AMQ] , URL is > wrong, it gives 404 Page Not Found. I think the correct would be > [https://issues.apache.org/jira/projects/AMQ] > I can take up this task, if someone point to the git location or any other > pointers would be good. > Thanks! > Regards, > Shubham Gupta > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMQ-7130) bug tracking link is pointing to wrong url
[ https://issues.apache.org/jira/browse/AMQ-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7130. --- Resolution: Fixed > bug tracking link is pointing to wrong url > -- > > Key: AMQ-7130 > URL: https://issues.apache.org/jira/browse/AMQ-7130 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 5.15.8 > Environment: MacOS High Sierra, 10.13.6 > Processor: 2.8 GHz Intel Core i7 > Memory: 16 GB 2133 MHz LPDDR3 > Graphics: Intel HD Graphics 630 1536 MB > > >Reporter: Shubham Gupta >Assignee: Jean-Baptiste Onofré >Priority: Minor > Labels: documentation > Fix For: 5.x > > Original Estimate: 168h > Time Spent: 20m > Remaining Estimate: 167h 40m > > Hello, > I was browsing through the documentation. I landed up in the page-> > [https://projects.apache.org/project.html?activemq|https://projects.apache.org/project.html?activemq.] > In the Bug-Tracking: [http://issues.apache.org/activemq/browse/AMQ] , URL is > wrong, it gives 404 Page Not Found. I think the correct would be > [https://issues.apache.org/jira/projects/AMQ] > I can take up this task, if someone point to the git location or any other > pointers would be good. > Thanks! > Regards, > Shubham Gupta > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7130) bug tracking link is pointing to wrong url
[ https://issues.apache.org/jira/browse/AMQ-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954824#comment-16954824 ] ASF subversion and git services commented on AMQ-7130: -- Commit dc2f69d96ac59df26e64fc9b5da3577c741d4cee in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=dc2f69d ] Merge pull request #399 from coheigea/doap.rdf AMQ-7130 Update AMQ doap > bug tracking link is pointing to wrong url > -- > > Key: AMQ-7130 > URL: https://issues.apache.org/jira/browse/AMQ-7130 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 5.15.8 > Environment: MacOS High Sierra, 10.13.6 > Processor: 2.8 GHz Intel Core i7 > Memory: 16 GB 2133 MHz LPDDR3 > Graphics: Intel HD Graphics 630 1536 MB > > >Reporter: Shubham Gupta >Assignee: Jean-Baptiste Onofré >Priority: Minor > Labels: documentation > Fix For: 5.x > > Original Estimate: 168h > Time Spent: 20m > Remaining Estimate: 167h 40m > > Hello, > I was browsing through the documentation. I landed up in the page-> > [https://projects.apache.org/project.html?activemq|https://projects.apache.org/project.html?activemq.] > In the Bug-Tracking: [http://issues.apache.org/activemq/browse/AMQ] , URL is > wrong, it gives 404 Page Not Found. I think the correct would be > [https://issues.apache.org/jira/projects/AMQ] > I can take up this task, if someone point to the git location or any other > pointers would be good. > Thanks! > Regards, > Shubham Gupta > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7130) bug tracking link is pointing to wrong url
[ https://issues.apache.org/jira/browse/AMQ-7130?focusedWorklogId=330655&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330655 ] ASF GitHub Bot logged work on AMQ-7130: --- Author: ASF GitHub Bot Created on: 18/Oct/19 17:05 Start Date: 18/Oct/19 17:05 Worklog Time Spent: 10m Work Description: jbonofre commented on pull request #399: AMQ-7130 Update AMQ doap URL: https://github.com/apache/activemq/pull/399 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 330655) Remaining Estimate: 167h 40m (was: 167h 50m) Time Spent: 20m (was: 10m) > bug tracking link is pointing to wrong url > -- > > Key: AMQ-7130 > URL: https://issues.apache.org/jira/browse/AMQ-7130 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 5.15.8 > Environment: MacOS High Sierra, 10.13.6 > Processor: 2.8 GHz Intel Core i7 > Memory: 16 GB 2133 MHz LPDDR3 > Graphics: Intel HD Graphics 630 1536 MB > > >Reporter: Shubham Gupta >Assignee: Jean-Baptiste Onofré >Priority: Minor > Labels: documentation > Fix For: 5.x > > Original Estimate: 168h > Time Spent: 20m > Remaining Estimate: 167h 40m > > Hello, > I was browsing through the documentation. I landed up in the page-> > [https://projects.apache.org/project.html?activemq|https://projects.apache.org/project.html?activemq.] > In the Bug-Tracking: [http://issues.apache.org/activemq/browse/AMQ] , URL is > wrong, it gives 404 Page Not Found. I think the correct would be > [https://issues.apache.org/jira/projects/AMQ] > I can take up this task, if someone point to the git location or any other > pointers would be good. > Thanks! > Regards, > Shubham Gupta > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7130) bug tracking link is pointing to wrong url
[ https://issues.apache.org/jira/browse/AMQ-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954823#comment-16954823 ] ASF subversion and git services commented on AMQ-7130: -- Commit d525096cac444189c2d233e1de47342f1916c82d in activemq's branch refs/heads/master from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=d525096 ] AMQ-7130 Update AMQ doap > bug tracking link is pointing to wrong url > -- > > Key: AMQ-7130 > URL: https://issues.apache.org/jira/browse/AMQ-7130 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 5.15.8 > Environment: MacOS High Sierra, 10.13.6 > Processor: 2.8 GHz Intel Core i7 > Memory: 16 GB 2133 MHz LPDDR3 > Graphics: Intel HD Graphics 630 1536 MB > > >Reporter: Shubham Gupta >Assignee: Jean-Baptiste Onofré >Priority: Minor > Labels: documentation > Fix For: 5.x > > Original Estimate: 168h > Time Spent: 20m > Remaining Estimate: 167h 40m > > Hello, > I was browsing through the documentation. I landed up in the page-> > [https://projects.apache.org/project.html?activemq|https://projects.apache.org/project.html?activemq.] > In the Bug-Tracking: [http://issues.apache.org/activemq/browse/AMQ] , URL is > wrong, it gives 404 Page Not Found. I think the correct would be > [https://issues.apache.org/jira/projects/AMQ] > I can take up this task, if someone point to the git location or any other > pointers would be good. > Thanks! > Regards, > Shubham Gupta > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
[ https://issues.apache.org/jira/browse/AMQ-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-7322. --- Resolution: Fixed > Add HTTPOnly flag to the webconsole + REST API Cookies > -- > > Key: AMQ-7322 > URL: https://issues.apache.org/jira/browse/AMQ-7322 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Reporter: Colm O hEigeartaigh >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
[ https://issues.apache.org/jira/browse/AMQ-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954821#comment-16954821 ] ASF subversion and git services commented on AMQ-7322: -- Commit 59c441d4de126d1cab817744c903d21d4abbc4b4 in activemq's branch refs/heads/activemq-5.15.x from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=59c441d ] AMQ-7322 - Add HTTPOnly flag to the webconsole + REST API Cookies (cherry picked from commit 63b1238c4d1a0e10bd99ec9f3e6d2ee51b10c03d) > Add HTTPOnly flag to the webconsole + REST API Cookies > -- > > Key: AMQ-7322 > URL: https://issues.apache.org/jira/browse/AMQ-7322 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Reporter: Colm O hEigeartaigh >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMQ-7130) bug tracking link is pointing to wrong url
[ https://issues.apache.org/jira/browse/AMQ-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-7130: - Assignee: Jean-Baptiste Onofré > bug tracking link is pointing to wrong url > -- > > Key: AMQ-7130 > URL: https://issues.apache.org/jira/browse/AMQ-7130 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 5.15.8 > Environment: MacOS High Sierra, 10.13.6 > Processor: 2.8 GHz Intel Core i7 > Memory: 16 GB 2133 MHz LPDDR3 > Graphics: Intel HD Graphics 630 1536 MB > > >Reporter: Shubham Gupta >Assignee: Jean-Baptiste Onofré >Priority: Minor > Labels: documentation > Fix For: 5.x > > Original Estimate: 168h > Time Spent: 10m > Remaining Estimate: 167h 50m > > Hello, > I was browsing through the documentation. I landed up in the page-> > [https://projects.apache.org/project.html?activemq|https://projects.apache.org/project.html?activemq.] > In the Bug-Tracking: [http://issues.apache.org/activemq/browse/AMQ] , URL is > wrong, it gives 404 Page Not Found. I think the correct would be > [https://issues.apache.org/jira/projects/AMQ] > I can take up this task, if someone point to the git location or any other > pointers would be good. > Thanks! > Regards, > Shubham Gupta > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
[ https://issues.apache.org/jira/browse/AMQ-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-7322: -- Component/s: webconsole > Add HTTPOnly flag to the webconsole + REST API Cookies > -- > > Key: AMQ-7322 > URL: https://issues.apache.org/jira/browse/AMQ-7322 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Reporter: Colm O hEigeartaigh >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.16.0, 5.15.11 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
[ https://issues.apache.org/jira/browse/AMQ-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-7322: - Assignee: Jean-Baptiste Onofré > Add HTTPOnly flag to the webconsole + REST API Cookies > -- > > Key: AMQ-7322 > URL: https://issues.apache.org/jira/browse/AMQ-7322 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.16.0, 5.15.11 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
[ https://issues.apache.org/jira/browse/AMQ-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954819#comment-16954819 ] ASF subversion and git services commented on AMQ-7322: -- Commit 830a4c0391a49092860a6139cc23890f778a30b8 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=830a4c0 ] Merge pull request #400 from coheigea/AMQ-7322 AMQ-7322 - Add HTTPOnly flag to the webconsole + REST API Cookies > Add HTTPOnly flag to the webconsole + REST API Cookies > -- > > Key: AMQ-7322 > URL: https://issues.apache.org/jira/browse/AMQ-7322 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Reporter: Colm O hEigeartaigh >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
[ https://issues.apache.org/jira/browse/AMQ-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954818#comment-16954818 ] ASF subversion and git services commented on AMQ-7322: -- Commit 63b1238c4d1a0e10bd99ec9f3e6d2ee51b10c03d in activemq's branch refs/heads/master from Colm O hEigeartaigh [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=63b1238 ] AMQ-7322 - Add HTTPOnly flag to the webconsole + REST API Cookies > Add HTTPOnly flag to the webconsole + REST API Cookies > -- > > Key: AMQ-7322 > URL: https://issues.apache.org/jira/browse/AMQ-7322 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Reporter: Colm O hEigeartaigh >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
[ https://issues.apache.org/jira/browse/AMQ-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954820#comment-16954820 ] ASF subversion and git services commented on AMQ-7322: -- Commit 830a4c0391a49092860a6139cc23890f778a30b8 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=830a4c0 ] Merge pull request #400 from coheigea/AMQ-7322 AMQ-7322 - Add HTTPOnly flag to the webconsole + REST API Cookies > Add HTTPOnly flag to the webconsole + REST API Cookies > -- > > Key: AMQ-7322 > URL: https://issues.apache.org/jira/browse/AMQ-7322 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Reporter: Colm O hEigeartaigh >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
[ https://issues.apache.org/jira/browse/AMQ-7322?focusedWorklogId=330651&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330651 ] ASF GitHub Bot logged work on AMQ-7322: --- Author: ASF GitHub Bot Created on: 18/Oct/19 17:03 Start Date: 18/Oct/19 17:03 Worklog Time Spent: 10m Work Description: jbonofre commented on pull request #400: AMQ-7322 - Add HTTPOnly flag to the webconsole + REST API Cookies URL: https://github.com/apache/activemq/pull/400 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 330651) Time Spent: 20m (was: 10m) > Add HTTPOnly flag to the webconsole + REST API Cookies > -- > > Key: AMQ-7322 > URL: https://issues.apache.org/jira/browse/AMQ-7322 > Project: ActiveMQ > Issue Type: Improvement > Components: webconsole >Reporter: Colm O hEigeartaigh >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.16.0, 5.15.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
[ https://issues.apache.org/jira/browse/AMQ-7322?focusedWorklogId=330598&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330598 ] ASF GitHub Bot logged work on AMQ-7322: --- Author: ASF GitHub Bot Created on: 18/Oct/19 16:19 Start Date: 18/Oct/19 16:19 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #400: AMQ-7322 - Add HTTPOnly flag to the webconsole + REST API Cookies URL: https://github.com/apache/activemq/pull/400 We should add the HTTPOnly flag to the webconsole + REST API Cookies This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 330598) Remaining Estimate: 0h Time Spent: 10m > Add HTTPOnly flag to the webconsole + REST API Cookies > -- > > Key: AMQ-7322 > URL: https://issues.apache.org/jira/browse/AMQ-7322 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: 5.16.0, 5.15.11 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMQ-7322) Add HTTPOnly flag to the webconsole + REST API Cookies
Colm O hEigeartaigh created AMQ-7322: Summary: Add HTTPOnly flag to the webconsole + REST API Cookies Key: AMQ-7322 URL: https://issues.apache.org/jira/browse/AMQ-7322 Project: ActiveMQ Issue Type: Improvement Reporter: Colm O hEigeartaigh Fix For: 5.16.0, 5.15.11 We should add the HTTPOnly flag to the webconsole + REST API Cookies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7168) ActiveMQ Karaf Features Install SNAPSHOT Karaf Bundles
[
https://issues.apache.org/jira/browse/AMQ-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954469#comment-16954469
]
Colm O hEigeartaigh commented on AMQ-7168:
--
This issue is fixed in Karaf 4.2.4 - I think by this Jira -
https://issues.apache.org/jira/browse/KARAF-6151
This Jira can be closed.
> ActiveMQ Karaf Features Install SNAPSHOT Karaf Bundles
> --
>
> Key: AMQ-7168
> URL: https://issues.apache.org/jira/browse/AMQ-7168
> Project: ActiveMQ
> Issue Type: Bug
> Components: OSGi/Karaf
>Affects Versions: 5.15.8
>Reporter: James Carman
>Priority: Major
>
> When installing the activemq-client 5.15.8 feature in a fresh install of
> Apache Karaf 4.2.3, the following SNAPSHOT bundles show up:
> * Apache Karaf :: JAAS :: Boot - 4.3.0.SNAPSHOT
> * Apache Karaf :: Shell :: Console - 4.3.0.SNAPSHOT
> * Apache Karaf :: Shell :: Table - 4.3.0.SNAPSHOT
>
> Here's a log of what I did:
> {noformat}
> karaf@root()> mifarjcarman-m1:apache-karaf-4.2.3 jcarman$ rm -fR data
> mifarjcarman-m1:apache-karaf-4.2.3 jcarman$ bin/karaf
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.2.3)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> feature:repo-add activemq 5.15.8
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.8/xml/features
> karaf@root()> feature:install activemq-client
> karaf@root()> list -t 0
> START LEVEL 100 , List Threshold: 0
> ID │ State│ Lvl │ Version │ Name
> ───┼──┼─┼──┼───
> 0 │ Active │ 0 │ 5.6.12 │ System Bundle, Fragments: 1
> 1 │ Resolved │ 1 │ 4.2.3│ Apache Karaf :: Features ::
> Extension, Hosts: 0
> 2 │ Active │ 5 │ 1.2.2│ Apache Felix Metatype Service
> 3 │ Active │ 5 │ 4.2.3│ Apache Karaf :: OSGi Services ::
> EventAdmin
> 4 │ Active │ 5 │ 2.6.1│ OPS4J Pax Url - mvn:
> 5 │ Active │ 8 │ 1.17.1 │ jansi
> 6 │ Active │ 8 │ 1.10.1 │ OPS4J Pax Logging - API
> 7 │ Active │ 8 │ 1.10.1 │ OPS4J Pax Logging - Log4j v2
> 8 │ Active │ 9 │ 1.0.2│ Apache Felix Coordinator Service
> 9 │ Active │ 10 │ 1.9.10 │ Apache Felix Configuration Admin
> Service
> 10 │ Active │ 11 │ 3.6.4│ Apache Felix File Install
> 11 │ Active │ 15 │ 4.2.3│ Apache Karaf :: Features :: Core
> 12 │ Active │ 30 │ 2.9.0│ Apache ServiceMix :: Specs ::
> Activation API 1.4
> 13 │ Active │ 30 │ 1.1.5│ Apache Aries JMX API
> 14 │ Active │ 30 │ 1.1.8│ Apache Aries JMX Core
> 15 │ Active │ 30 │ 1.2.0│ Apache Aries Whiteboard support for
> JMX DynamicMBean services
> 16 │ Active │ 20 │ 1.1.3│ Apache Aries Util
> 17 │ Active │ 30 │ 4.2.3│ Apache Karaf :: Bundle :: Core
> 18 │ Active │ 30 │ 4.2.3│ Apache Karaf :: ConfigAdmin :: Core
> 19 │ Active │ 26 │ 4.2.3│ Apache Karaf :: Deployer :: Features
> 20 │ Active │ 24 │ 4.2.3│ Apache Karaf :: Deployer :: Karaf
> Archive (.kar)
> 21 │ Active │ 24 │ 4.2.3│ Apache Karaf :: Deployer :: Wrap Non
> OSGi Jar
> 22 │ Active │ 30 │ 4.2.3│ Apache Karaf :: Diagnostic :: Core
> 23 │ Active │ 80 │ 4.2.3│ Apache Karaf :: OSGi Services ::
> Event
> 24 │ Active │ 30 │ 4.2.3│ Apache Karaf :: Features :: Command
> 25 │ Active │ 30 │ 4.2.3│ Apache Karaf :: Instance :: Core
> 26 │ Active │ 30 │ 4.2.3│ Apache Karaf :: JAAS :: Command
> 27 │ Active │ 30 │ 4.2.3│ Apache Karaf :: JAAS :: Config
> 28 │ Active │ 30 │ 4.2.3│ Apache Karaf :: JAAS :: Modules
> 29 │ Active │ 30 │ 4.2.3│ Apache Karaf :: KAR :: Core
> 30 │ Active │ 30 │ 4.2.3│ Apache Karaf :: Log :: Core
> 31 │ Active │ 30 │ 4.2.3│ Apache Karaf :: Management
> 32 │ Active │ 30 │ 4.2.3│ Apache Karaf :: Package :: Core
> 33 │ Active │ 30 │ 4.2.3│ Apache Karaf :: Service :: Core
> 34 │ Active │ 30 │ 4.2.3│ Apache Karaf :: Shell :: Various
> Commands
> 35 │ Active │ 30 │ 4.2.3
[jira] [Work logged] (AMQ-7130) bug tracking link is pointing to wrong url
[ https://issues.apache.org/jira/browse/AMQ-7130?focusedWorklogId=330386&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330386 ] ASF GitHub Bot logged work on AMQ-7130: --- Author: ASF GitHub Bot Created on: 18/Oct/19 09:27 Start Date: 18/Oct/19 09:27 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #399: AMQ-7130 Update AMQ doap URL: https://github.com/apache/activemq/pull/399 https://issues.apache.org/jira/browse/AMQ-7130 is caused by the fact that our doap JIRA link is incorrect. Once this PR is merged then https://projects.apache.org/project.html?activemq will need to be updated to point to git instead of svn. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 330386) Remaining Estimate: 167h 50m (was: 168h) Time Spent: 10m > bug tracking link is pointing to wrong url > -- > > Key: AMQ-7130 > URL: https://issues.apache.org/jira/browse/AMQ-7130 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 5.15.8 > Environment: MacOS High Sierra, 10.13.6 > Processor: 2.8 GHz Intel Core i7 > Memory: 16 GB 2133 MHz LPDDR3 > Graphics: Intel HD Graphics 630 1536 MB > > >Reporter: Shubham Gupta >Priority: Minor > Labels: documentation > Fix For: 5.x > > Original Estimate: 168h > Time Spent: 10m > Remaining Estimate: 167h 50m > > Hello, > I was browsing through the documentation. I landed up in the page-> > [https://projects.apache.org/project.html?activemq|https://projects.apache.org/project.html?activemq.] > In the Bug-Tracking: [http://issues.apache.org/activemq/browse/AMQ] , URL is > wrong, it gives 404 Page Not Found. I think the correct would be > [https://issues.apache.org/jira/projects/AMQ] > I can take up this task, if someone point to the git location or any other > pointers would be good. > Thanks! > Regards, > Shubham Gupta > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMQ-7160) Use secure repository URL
[ https://issues.apache.org/jira/browse/AMQ-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954393#comment-16954393 ] Colm O hEigeartaigh commented on AMQ-7160: -- This Jira can be closed, as it's been fixed already (see comment on the PR). > Use secure repository URL > - > > Key: AMQ-7160 > URL: https://issues.apache.org/jira/browse/AMQ-7160 > Project: ActiveMQ > Issue Type: Task >Reporter: Olaf Flebbe >Priority: Major > > See github pull request 347 > Use secure uri for sprint repo -- This message was sent by Atlassian Jira (v8.3.4#803005)
