[jira] [Commented] (AMQ-8471) activemq stop command fails with no or outdated process id
[ https://issues.apache.org/jira/browse/AMQ-8471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493651#comment-17493651 ] shrihari commented on AMQ-8471: --- Hi [~jbonofre] Did you get a chance to check the AIX machine? > activemq stop command fails with no or outdated process id > -- > > Key: AMQ-8471 > URL: https://issues.apache.org/jira/browse/AMQ-8471 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.16.2 >Reporter: shrihari >Assignee: Jean-Baptiste Onofré >Priority: Major > Attachments: image-2022-02-07-10-21-19-913.png, > image-2022-02-07-10-21-39-782.png > > Time Spent: 10m > Remaining Estimate: 0h > > In some AIX/Linux environments, the activemq stop command fails with the > below error. > bash-4.4# ./activemq stop > INFO: Loading '/AMQ/message-broker/bin/env' > INFO: Using java '/usr/java8_64/bin/java' > ERROR: No or outdated process id in '/AMQ/message-broker//data/activemq.pid' > INFO: Removing /AMQ/message-broker//data/activemq.pid > > The fix provided in https://issues.apache.org/jira/browse/AMQ-8425 doesn't > work in such environments as the issue is not due to the user/terminal > instance. > > Workaround: > Some AIX/linux environments are highly sensitive to the *acute/backquot* > *character `* > Backquot character reference : > [https://www.computerhope.com/jargon/b/backquot.htm] > Update the file /message-broker/bin/activemq as below : > Change the line by removing backquot character : > RET="`ps -eo "pid,args" | grep "\s*$activemq_pid\s.java"`" to RET="ps -eo > "pid,args" | grep "\s$activemq_pid\s.*java"" > This will be inside checkRunning() function. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARTEMIS-3687) Bridges with concurrency > 1 can leak
Justin Bertram created ARTEMIS-3687: --- Summary: Bridges with concurrency > 1 can leak Key: ARTEMIS-3687 URL: https://issues.apache.org/jira/browse/ARTEMIS-3687 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Justin Bertram Assignee: Justin Bertram -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARTEMIS-3666) Update to PostgreSQL 42.3.3
[ https://issues.apache.org/jira/browse/ARTEMIS-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493531#comment-17493531 ] ASF subversion and git services commented on ARTEMIS-3666: -- Commit f0a96628b4056c95b0ed5be9ae0cc785edae6bc8 in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=f0a9662 ] ARTEMIS-3666: update to postgresql 42.3.3 > Update to PostgreSQL 42.3.3 > --- > > Key: ARTEMIS-3666 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3666 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.21.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Update to the latest PostgreSQL release, 42.3.3. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3666) Update to PostgreSQL 42.3.3
[ https://issues.apache.org/jira/browse/ARTEMIS-3666?focusedWorklogId=728564=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728564 ] ASF GitHub Bot logged work on ARTEMIS-3666: --- Author: ASF GitHub Bot Created on: 16/Feb/22 22:35 Start Date: 16/Feb/22 22:35 Worklog Time Spent: 10m Work Description: brusdev merged pull request #3958: URL: https://github.com/apache/activemq-artemis/pull/3958 -- 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. To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 728564) Time Spent: 20m (was: 10m) > Update to PostgreSQL 42.3.3 > --- > > Key: ARTEMIS-3666 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3666 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.21.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update to the latest PostgreSQL release, 42.3.3. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3679) Brokers with JDBC shared-store shutdown after daylight saving fall back
[
https://issues.apache.org/jira/browse/ARTEMIS-3679?focusedWorklogId=728538=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728538
]
ASF GitHub Bot logged work on ARTEMIS-3679:
---
Author: ASF GitHub Bot
Created on: 16/Feb/22 21:29
Start Date: 16/Feb/22 21:29
Worklog Time Spent: 10m
Work Description: franz1981 commented on a change in pull request #3950:
URL: https://github.com/apache/activemq-artemis/pull/3950#discussion_r808469313
##
File path:
artemis-server/src/test/java/org/apache/activemq/artemis/core/server/impl/jdbc/JdbcLeaseLockTest.java
##
@@ -116,6 +122,22 @@ public void dropLockTable() throws Exception {
jdbcSharedStateManager.close();
}
+ @Test
+ public void shouldStillHeldLockOnTimeZoneChange() {
+
Assume.assumeThat(PropertySQLProvider.Factory.identifyDialect(dbConf.getJdbcDriverClassName()),
CoreMatchers.is(PropertySQLProvider.Factory.SQLDialect.DERBY));
+ TimeZone.setDefault(TimeZone.getTimeZone(ZoneId.of("-1")));
+ final long expirationMillis = Duration.ofMinutes(30).toMillis();
+ final LeaseLock lock = lock(expirationMillis);
+ Assert.assertTrue("Must acquire the lock!", lock.tryAcquire());
+ TimeZone.setDefault(TimeZone.getTimeZone(ZoneId.of("+3")));
Review comment:
@fvaleri I still have to decide how to handle testing this :)
But I've decided to use specific UTC get time query per supported DBs
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 728538)
Time Spent: 1h 20m (was: 1h 10m)
> Brokers with JDBC shared-store shutdown after daylight saving fall back
> ---
>
> Key: ARTEMIS-3679
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3679
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.20.0
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
>Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> This is what happened on a two brokers JDBC shared-store setup after daylight
> savings change. This also causes the backup shutdown with the same critical
> IO error.
> {code:java}
> 2021-10-31 01:58:44,002 WARN
> [org.apache.activemq.artemis.core.server.impl.jdbc.JdbcLeaseLock] [LIVE]
> d5b17659-c4f6-4847-bfb2-6c5f209a0fb9 query currentTimestamp = 2021-10-31
> 01:58:43.27 on database should happen AFTER 2021-10-31 01:58:44.0 on
> broker 2021-10-31 02:59:00,217 WARN [org.apache.activemq.artemis.core.server]
> AMQ222010: Critical IO Error, shutting down the server. file=NULL,
> message=Lost NodeManager lock: java.io.IOException: lost lock at
> org.apache.activemq.artemis.core.server.impl.SharedStoreLiveActivation.lambda$registerActiveLockListener$0(SharedStoreLiveActivation.java:123)
> [artemis-server-2.16.0.redhat-00012.jar:2.16.0.redhat-00012] at
> org.apache.activemq.artemis.core.server.NodeManager.lambda$notifyLostLock$0(NodeManager.java:143)
> [artemis-server-2.16.0.redhat-00012.jar:2.16.0.redhat-00012] at
> java.base/java.lang.Iterable.forEach(Iterable.java:75) [java.base:] at
> org.apache.activemq.artemis.core.server.NodeManager.notifyLostLock(NodeManager.java:141)
> [artemis-server-2.16.0.redhat-00012.jar:2.16.0.redhat-00012] at
> org.apache.activemq.artemis.core.server.impl.jdbc.JdbcNodeManager.notifyLostLock(JdbcNodeManager.java:154)
> [artemis-server-2.16.0.redhat-00012.jar:2.16.0.redhat-00012] at
> org.apache.activemq.artemis.core.server.impl.jdbc.ActiveMQScheduledLeaseLock.run(ActiveMQScheduledLeaseLock.java:114)
> [artemis-server-2.16.0.redhat-00012.jar:2.16.0.redhat-00012] at
> org.apache.activemq.artemis.core.server.ActiveMQScheduledComponent.runForExecutor(ActiveMQScheduledComponent.java:313)
> [artemis-commons-2.16.0.redhat-00012.jar:2.16.0.redhat-00012] at
> org.apache.activemq.artemis.core.server.ActiveMQScheduledComponent.lambda$bookedRunForScheduler$2(ActiveMQScheduledComponent.java:320)
> [artemis-commons-2.16.0.redhat-00012.jar:2.16.0.redhat-00012] at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> [artemis-commons-2.16.0.redhat-00012.jar:2.16.0.redhat-00012] at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> [artemis-commons-2.16.0.redhat-00012.jar:2.16.0.redhat-00012] at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:65)
>
[jira] [Closed] (AMQ-2286) NetworkConnector PrefetchSize
[ https://issues.apache.org/jira/browse/AMQ-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich closed AMQ-2286. --- Resolution: Abandoned > NetworkConnector PrefetchSize > - > > Key: AMQ-2286 > URL: https://issues.apache.org/jira/browse/AMQ-2286 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.2.0 > Environment: Sun solaris 10 >Reporter: ying >Priority: Major > Fix For: 5.x > > > I have an issue which greatly reduces the quality of service of a network of > activemq brokers. > Here is what I have: > 1. 4 brokers( broker1, broker2, broker3, broker4) in a network by multicast > discovery > 2. i have 2 consumers of QueueA on broker1, 2 consumers of QueueA on broker2, > and consumer queuePrefetch=1, networkConnector prefetchSize=1. Queue is using > RoundRobinDispatchPolicy > 3. I publish to QueueA on broker3 with 100 msgs, 2 consumers on broker1 are > fast and they process fine but 2 consumers on broker2 are stuck. However, > with this config, msgs are still 50 goes to broker1, 50 goes to broker2, and > when consumers on broker2 get stuck, those 50 msgs are stuck on broker2. It > seems the prefetchSize=1 on networkConnector have no effect at all. > what I expect in this case will be that 98 msgs shall go to broker1, and only > 2 msgs stuck on broker2's consumers. I cannot lose a single msg so > ConstantPendingMessageLimit will not help. > Please help. Thanks -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-2286) NetworkConnector PrefetchSize
[ https://issues.apache.org/jira/browse/AMQ-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-2286: Labels: (was: close-pending) > NetworkConnector PrefetchSize > - > > Key: AMQ-2286 > URL: https://issues.apache.org/jira/browse/AMQ-2286 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.2.0 > Environment: Sun solaris 10 >Reporter: ying >Priority: Major > Fix For: 5.x > > > I have an issue which greatly reduces the quality of service of a network of > activemq brokers. > Here is what I have: > 1. 4 brokers( broker1, broker2, broker3, broker4) in a network by multicast > discovery > 2. i have 2 consumers of QueueA on broker1, 2 consumers of QueueA on broker2, > and consumer queuePrefetch=1, networkConnector prefetchSize=1. Queue is using > RoundRobinDispatchPolicy > 3. I publish to QueueA on broker3 with 100 msgs, 2 consumers on broker1 are > fast and they process fine but 2 consumers on broker2 are stuck. However, > with this config, msgs are still 50 goes to broker1, 50 goes to broker2, and > when consumers on broker2 get stuck, those 50 msgs are stuck on broker2. It > seems the prefetchSize=1 on networkConnector have no effect at all. > what I expect in this case will be that 98 msgs shall go to broker1, and only > 2 msgs stuck on broker2's consumers. I cannot lose a single msg so > ConstantPendingMessageLimit will not help. > Please help. Thanks -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (AMQ-5161) NullPointerException during async startup
[
https://issues.apache.org/jira/browse/AMQ-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich closed AMQ-5161.
---
Resolution: Not A Problem
> NullPointerException during async startup
> -
>
> Key: AMQ-5161
> URL: https://issues.apache.org/jira/browse/AMQ-5161
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.9.1
>Reporter: james
>Priority: Major
> Attachments: QueueService2Test.java
>
>
> I'm using an embedded broker with asynchronous startup enabled. My setup
> worked using 5.9.0. When i upgraded to 5.9.1, i started getting this
> exception on startup:
> {noformat}
> javax.jms.JMSException: java.lang.NullPointerException
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1408)
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1513)
> at
> org.apache.activemq.ActiveMQConnection.setClientID(ActiveMQConnection.java:417)
> at <...internal system startup stack trace...>
> Caused by: java.lang.NullPointerException
> at
> org.apache.activemq.broker.jmx.ManagedRegionBroker.addConnection(ManagedRegionBroker.java:232)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:91)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:97)
> at
> org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:759)
> at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
> at
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:291)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:145)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at
> org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:247)
> at
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
> at
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (AMQ-5161) NullPointerException during async startup
[
https://issues.apache.org/jira/browse/AMQ-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated AMQ-5161:
Labels: (was: close-pending)
> NullPointerException during async startup
> -
>
> Key: AMQ-5161
> URL: https://issues.apache.org/jira/browse/AMQ-5161
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.9.1
>Reporter: james
>Priority: Major
> Attachments: QueueService2Test.java
>
>
> I'm using an embedded broker with asynchronous startup enabled. My setup
> worked using 5.9.0. When i upgraded to 5.9.1, i started getting this
> exception on startup:
> {noformat}
> javax.jms.JMSException: java.lang.NullPointerException
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1408)
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1513)
> at
> org.apache.activemq.ActiveMQConnection.setClientID(ActiveMQConnection.java:417)
> at <...internal system startup stack trace...>
> Caused by: java.lang.NullPointerException
> at
> org.apache.activemq.broker.jmx.ManagedRegionBroker.addConnection(ManagedRegionBroker.java:232)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:91)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:97)
> at
> org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:759)
> at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
> at
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:291)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:145)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at
> org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:247)
> at
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
> at
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (AMQ-5161) NullPointerException during async startup
[
https://issues.apache.org/jira/browse/AMQ-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493501#comment-17493501
]
Matt Pavlovich commented on AMQ-5161:
-
This is most likely resolved in newer releases. If this is still an issue,
please re-open after testing with 5.16.4
> NullPointerException during async startup
> -
>
> Key: AMQ-5161
> URL: https://issues.apache.org/jira/browse/AMQ-5161
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.9.1
>Reporter: james
>Priority: Major
> Labels: close-pending
> Attachments: QueueService2Test.java
>
>
> I'm using an embedded broker with asynchronous startup enabled. My setup
> worked using 5.9.0. When i upgraded to 5.9.1, i started getting this
> exception on startup:
> {noformat}
> javax.jms.JMSException: java.lang.NullPointerException
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1408)
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1513)
> at
> org.apache.activemq.ActiveMQConnection.setClientID(ActiveMQConnection.java:417)
> at <...internal system startup stack trace...>
> Caused by: java.lang.NullPointerException
> at
> org.apache.activemq.broker.jmx.ManagedRegionBroker.addConnection(ManagedRegionBroker.java:232)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:91)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:97)
> at
> org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:759)
> at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
> at
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:291)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:145)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at
> org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:247)
> at
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
> at
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (AMQ-5161) NullPointerException during async startup
[
https://issues.apache.org/jira/browse/AMQ-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated AMQ-5161:
Labels: close-pending (was: )
> NullPointerException during async startup
> -
>
> Key: AMQ-5161
> URL: https://issues.apache.org/jira/browse/AMQ-5161
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.9.1
>Reporter: james
>Priority: Major
> Labels: close-pending
> Attachments: QueueService2Test.java
>
>
> I'm using an embedded broker with asynchronous startup enabled. My setup
> worked using 5.9.0. When i upgraded to 5.9.1, i started getting this
> exception on startup:
> {noformat}
> javax.jms.JMSException: java.lang.NullPointerException
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1408)
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1513)
> at
> org.apache.activemq.ActiveMQConnection.setClientID(ActiveMQConnection.java:417)
> at <...internal system startup stack trace...>
> Caused by: java.lang.NullPointerException
> at
> org.apache.activemq.broker.jmx.ManagedRegionBroker.addConnection(ManagedRegionBroker.java:232)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:91)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92)
> at
> org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:97)
> at
> org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:759)
> at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
> at
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:291)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:145)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at
> org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:247)
> at
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
> at
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (AMQ-5154) amq.js regression - old version in activemq-web, latest version in activemq-web-demo
[
https://issues.apache.org/jira/browse/AMQ-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich reassigned AMQ-5154:
---
Assignee: Matt Pavlovich
> amq.js regression - old version in activemq-web, latest version in
> activemq-web-demo
>
>
> Key: AMQ-5154
> URL: https://issues.apache.org/jira/browse/AMQ-5154
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.9.1
>Reporter: CW
>Assignee: Matt Pavlovich
>Priority: Major
> Labels: ajax, amq.js, javascript
>
> According to [http://activemq.apache.org/ajax.html], the javascript client
> {{amq.js}} should use one of three adapters (for _jQuery_, _Prototype_, or
> _Dojo_) named {{amq_*_adapter.js}}. These files do not exist in the 5.9.1
> {{activemq-web}} Maven artifact.
> On further research, the version of {{amq.js}} that *is* included in 5.9.1
> appears to be an old version. How old, I'm not sure, but it pre-dates the
> fix for this JIRA issue: [https://issues.apache.org/jira/browse/AMQ-1377]
> The correct version of {{amq.js}}, as well as the three missing
> {{amq_*_adapter.js}} adapter files can all be found in the
> {{activemq-web-demo}} source tree (see
> [https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/src/main/webapp/js/]).
> Not sure what the best workaround is... perhaps download the amq.js and
> respective adapter files separately rather than use the {{activemq-web}}
> release?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling
[ https://issues.apache.org/jira/browse/AMQ-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5536: Labels: bug jdbc (was: bug close-pending jdbc) > Inconsistent Behavior for Duplicate Message Handling > > > Key: AMQ-5536 > URL: https://issues.apache.org/jira/browse/AMQ-5536 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.9.1, 5.10.1 > Environment: OS X Yosemite, jdk 1.7 >Reporter: Michael Rimov >Assignee: Matt Pavlovich >Priority: Major > Labels: bug, jdbc > Attachments: ActiveMQ-Tests.zip > > > Unlike Kahia, JDBC Persistence adapters allow duplicate ID's into the dead > letter queue. I've included a test showing the difference between Kahia and > two different jdbc persistence stores. (MySQL and H2) > In JDBC persistence environments this eventually shows up as errors asking if > the audit cursor is enabled, and in older versions (5.9.1, 5.10.0) can cause > deadlocks. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling
[ https://issues.apache.org/jira/browse/AMQ-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich closed AMQ-5536. --- Resolution: Abandoned > Inconsistent Behavior for Duplicate Message Handling > > > Key: AMQ-5536 > URL: https://issues.apache.org/jira/browse/AMQ-5536 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.9.1, 5.10.1 > Environment: OS X Yosemite, jdk 1.7 >Reporter: Michael Rimov >Assignee: Matt Pavlovich >Priority: Major > Labels: bug, jdbc > Attachments: ActiveMQ-Tests.zip > > > Unlike Kahia, JDBC Persistence adapters allow duplicate ID's into the dead > letter queue. I've included a test showing the difference between Kahia and > two different jdbc persistence stores. (MySQL and H2) > In JDBC persistence environments this eventually shows up as errors asking if > the audit cursor is enabled, and in older versions (5.9.1, 5.10.0) can cause > deadlocks. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling
[ https://issues.apache.org/jira/browse/AMQ-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reopened AMQ-5536: - > Inconsistent Behavior for Duplicate Message Handling > > > Key: AMQ-5536 > URL: https://issues.apache.org/jira/browse/AMQ-5536 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.9.1, 5.10.1 > Environment: OS X Yosemite, jdk 1.7 >Reporter: Michael Rimov >Assignee: Matt Pavlovich >Priority: Major > Labels: bug, close-pending, jdbc > Attachments: ActiveMQ-Tests.zip > > > Unlike Kahia, JDBC Persistence adapters allow duplicate ID's into the dead > letter queue. I've included a test showing the difference between Kahia and > two different jdbc persistence stores. (MySQL and H2) > In JDBC persistence environments this eventually shows up as errors asking if > the audit cursor is enabled, and in older versions (5.9.1, 5.10.0) can cause > deadlocks. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (AMQ-5569) activemq broker was blocked on log4j call appender
[ https://issues.apache.org/jira/browse/AMQ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reopened AMQ-5569: - > activemq broker was blocked on log4j call appender > -- > > Key: AMQ-5569 > URL: https://issues.apache.org/jira/browse/AMQ-5569 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Transport >Affects Versions: 5.9.1 > Environment: ubuntu 12.04 >Reporter: Anuj Maurice >Assignee: Matt Pavlovich >Priority: Major > Labels: close-pending > > activemq broker was blocked on log4j call appender. Full stack trace in > comment -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (AMQ-5569) activemq broker was blocked on log4j call appender
[ https://issues.apache.org/jira/browse/AMQ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich closed AMQ-5569. --- Resolution: Abandoned > activemq broker was blocked on log4j call appender > -- > > Key: AMQ-5569 > URL: https://issues.apache.org/jira/browse/AMQ-5569 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Transport >Affects Versions: 5.9.1 > Environment: ubuntu 12.04 >Reporter: Anuj Maurice >Assignee: Matt Pavlovich >Priority: Major > > activemq broker was blocked on log4j call appender. Full stack trace in > comment -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling
[ https://issues.apache.org/jira/browse/AMQ-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493499#comment-17493499 ] Matt Pavlovich commented on AMQ-5536: - This is being closed for inactivity. > Inconsistent Behavior for Duplicate Message Handling > > > Key: AMQ-5536 > URL: https://issues.apache.org/jira/browse/AMQ-5536 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.9.1, 5.10.1 > Environment: OS X Yosemite, jdk 1.7 >Reporter: Michael Rimov >Assignee: Matt Pavlovich >Priority: Major > Labels: bug, close-pending, jdbc > Attachments: ActiveMQ-Tests.zip > > > Unlike Kahia, JDBC Persistence adapters allow duplicate ID's into the dead > letter queue. I've included a test showing the difference between Kahia and > two different jdbc persistence stores. (MySQL and H2) > In JDBC persistence environments this eventually shows up as errors asking if > the audit cursor is enabled, and in older versions (5.9.1, 5.10.0) can cause > deadlocks. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-5569) activemq broker was blocked on log4j call appender
[ https://issues.apache.org/jira/browse/AMQ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5569: Labels: (was: close-pending) > activemq broker was blocked on log4j call appender > -- > > Key: AMQ-5569 > URL: https://issues.apache.org/jira/browse/AMQ-5569 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Transport >Affects Versions: 5.9.1 > Environment: ubuntu 12.04 >Reporter: Anuj Maurice >Assignee: Matt Pavlovich >Priority: Major > > activemq broker was blocked on log4j call appender. Full stack trace in > comment -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling
[ https://issues.apache.org/jira/browse/AMQ-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich closed AMQ-5536. --- Resolution: Abandoned > Inconsistent Behavior for Duplicate Message Handling > > > Key: AMQ-5536 > URL: https://issues.apache.org/jira/browse/AMQ-5536 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.9.1, 5.10.1 > Environment: OS X Yosemite, jdk 1.7 >Reporter: Michael Rimov >Assignee: Matt Pavlovich >Priority: Major > Labels: bug, close-pending, jdbc > Attachments: ActiveMQ-Tests.zip > > > Unlike Kahia, JDBC Persistence adapters allow duplicate ID's into the dead > letter queue. I've included a test showing the difference between Kahia and > two different jdbc persistence stores. (MySQL and H2) > In JDBC persistence environments this eventually shows up as errors asking if > the audit cursor is enabled, and in older versions (5.9.1, 5.10.0) can cause > deadlocks. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (AMQ-5569) activemq broker was blocked on log4j call appender
[ https://issues.apache.org/jira/browse/AMQ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich closed AMQ-5569. --- Resolution: Abandoned > activemq broker was blocked on log4j call appender > -- > > Key: AMQ-5569 > URL: https://issues.apache.org/jira/browse/AMQ-5569 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Transport >Affects Versions: 5.9.1 > Environment: ubuntu 12.04 >Reporter: Anuj Maurice >Assignee: Matt Pavlovich >Priority: Major > Labels: close-pending > > activemq broker was blocked on log4j call appender. Full stack trace in > comment -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (AMQ-5569) activemq broker was blocked on log4j call appender
[ https://issues.apache.org/jira/browse/AMQ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493498#comment-17493498 ] Matt Pavlovich commented on AMQ-5569: - Closing due to inactivity. > activemq broker was blocked on log4j call appender > -- > > Key: AMQ-5569 > URL: https://issues.apache.org/jira/browse/AMQ-5569 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Transport >Affects Versions: 5.9.1 > Environment: ubuntu 12.04 >Reporter: Anuj Maurice >Assignee: Matt Pavlovich >Priority: Major > Labels: close-pending > > activemq broker was blocked on log4j call appender. Full stack trace in > comment -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-5625) Allow AbortSlowConsumerStrategy to specify a fixed number of pending messages to consider a consumer slow
[ https://issues.apache.org/jira/browse/AMQ-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-5625: Fix Version/s: 5.17.1 > Allow AbortSlowConsumerStrategy to specify a fixed number of pending messages > to consider a consumer slow > - > > Key: AMQ-5625 > URL: https://issues.apache.org/jira/browse/AMQ-5625 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Affects Versions: 5.8.0 >Reporter: Tim Bain >Priority: Major > Fix For: 5.17.1 > > > Currently, the AbortSlowConsumerStrategy considers a consumer to be slow when > the broker has a number of pending messages equal to the consumer's prefetch > buffer size. > It would be useful to be able to specify directly the number of messages that > must be pending to consider the consumer slow, irrespective of the consumer's > prefetch size. > This would be especially useful for consumers with a very small prefetch size > (e.g. 1), to allow them to meaningfully use the AbortSlowConsumerStrategy > instead of being forced to use the AbortSlowAckConsumerStrategy (which > protects against a very different kind of problem). But it would also be > useful for consumers with larger prefetch buffers if we want to consider the > consumer slow sooner than the point where there are an additional prefetch > buffer worth of pending message; this is especially true for anyone using the > default prefetch size of 32k messages for non-persistent topics. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (AMQ-5625) Allow AbortSlowConsumerStrategy to specify a fixed number of pending messages to consider a consumer slow
[ https://issues.apache.org/jira/browse/AMQ-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493497#comment-17493497 ] Matt Pavlovich commented on AMQ-5625: - Bringing this forward for review in 5.17.1 > Allow AbortSlowConsumerStrategy to specify a fixed number of pending messages > to consider a consumer slow > - > > Key: AMQ-5625 > URL: https://issues.apache.org/jira/browse/AMQ-5625 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Affects Versions: 5.8.0 >Reporter: Tim Bain >Priority: Major > Fix For: 5.17.1 > > > Currently, the AbortSlowConsumerStrategy considers a consumer to be slow when > the broker has a number of pending messages equal to the consumer's prefetch > buffer size. > It would be useful to be able to specify directly the number of messages that > must be pending to consider the consumer slow, irrespective of the consumer's > prefetch size. > This would be especially useful for consumers with a very small prefetch size > (e.g. 1), to allow them to meaningfully use the AbortSlowConsumerStrategy > instead of being forced to use the AbortSlowAckConsumerStrategy (which > protects against a very different kind of problem). But it would also be > useful for consumers with larger prefetch buffers if we want to consider the > consumer slow sooner than the point where there are an additional prefetch > buffer worth of pending message; this is especially true for anyone using the > default prefetch size of 32k messages for non-persistent topics. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8486) ActiveMQ 5.17.0 Release Plans and Change notes
[ https://issues.apache.org/jira/browse/AMQ-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-8486: Description: Current plans for the release: * Apache Camel removal * Log4j2 support * JMS 2.0 preview support * KahaDB metrics update to use (micro or nanoseconds) * Make a pass at removing deprecated methods * Wrapper conf now align with other startup scripts for dedicatedTaskRunner and min heap memory * Dependency updates Breaking changes: * Apache Camel removal (developers impated) * sendDuplicateFromStoreToDLQ (logging and DLQ processors impacted) * KahaDB metrics unit change (monitoring and alerting impacted) was: Current plans for the release: * Apache Camel removal * Log4j2 support * JMS 2.0 preview support * KahaDB metrics update to use (micro or nanoseconds) * Make a pass at removing deprecated methods * Dependency updates Breaking changes: * Apache Camel removal (developers impated) * sendDuplicateFromStoreToDLQ (logging and DLQ processors impacted) * KahaDB metrics unit change (monitoring and alerting impacted) > ActiveMQ 5.17.0 Release Plans and Change notes > -- > > Key: AMQ-8486 > URL: https://issues.apache.org/jira/browse/AMQ-8486 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.17.0 > > > Current plans for the release: > * Apache Camel removal > * Log4j2 support > * JMS 2.0 preview support > * KahaDB metrics update to use (micro or nanoseconds) > * Make a pass at removing deprecated methods > * Wrapper conf now align with other startup scripts for dedicatedTaskRunner > and min heap memory > * Dependency updates > Breaking changes: > * Apache Camel removal (developers impated) > * sendDuplicateFromStoreToDLQ (logging and DLQ processors impacted) > * KahaDB metrics unit change (monitoring and alerting impacted) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (AMQ-8440) Set sendDuplicateFromStoreToDLQ to 'false' by default
[ https://issues.apache.org/jira/browse/AMQ-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-8440 started by Matt Pavlovich. --- > Set sendDuplicateFromStoreToDLQ to 'false' by default > - > > Key: AMQ-8440 > URL: https://issues.apache.org/jira/browse/AMQ-8440 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Fix For: 5.17.0 > > > For 5.17.0, set the default behavior to _not_ send a duplicateFromStore to > DLQ. > We now have the ability to log and increment a counter to assist in detecting > high-concurrency-from store scenarios without moving a copy of message(s) to > DLQ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (AMQ-2725) Issues With NetworkConnector and NetworkBridge MBeans
[ https://issues.apache.org/jira/browse/AMQ-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich closed AMQ-2725. --- Resolution: Duplicate This feature has been available for some time > Issues With NetworkConnector and NetworkBridge MBeans > -- > > Key: AMQ-2725 > URL: https://issues.apache.org/jira/browse/AMQ-2725 > Project: ActiveMQ > Issue Type: Bug > Components: JMX >Affects Versions: 5.3.1 > Environment: ActiveMQ 5.3.1 on Windoze XP Pro SP2 >Reporter: Joe Francis >Assignee: Matt Pavlovich >Priority: Minor > > On the JConsole, when you invoke the 'Stop' operation on the > NetworkConnectorView MBean, the corresponding NetworkBridgeView MBean > disappears as expected; however, when you invoke the NetworkConnectorView's > 'Start' operation to restart the bridge, the corresponding NetworkBridgeView > MBean does not reappear. > When you invoke the NetworkBridgeView MBean's Stop operation, the MBean > disappears. So there is no point having a Start operation for this MBean. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-2725) Issues With NetworkConnector and NetworkBridge MBeans
[ https://issues.apache.org/jira/browse/AMQ-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-2725: Fix Version/s: (was: 5.17.0) > Issues With NetworkConnector and NetworkBridge MBeans > -- > > Key: AMQ-2725 > URL: https://issues.apache.org/jira/browse/AMQ-2725 > Project: ActiveMQ > Issue Type: Bug > Components: JMX >Affects Versions: 5.3.1 > Environment: ActiveMQ 5.3.1 on Windoze XP Pro SP2 >Reporter: Joe Francis >Assignee: Matt Pavlovich >Priority: Minor > > On the JConsole, when you invoke the 'Stop' operation on the > NetworkConnectorView MBean, the corresponding NetworkBridgeView MBean > disappears as expected; however, when you invoke the NetworkConnectorView's > 'Start' operation to restart the bridge, the corresponding NetworkBridgeView > MBean does not reappear. > When you invoke the NetworkBridgeView MBean's Stop operation, the MBean > disappears. So there is no point having a Start operation for this MBean. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (AMQ-2725) Issues With NetworkConnector and NetworkBridge MBeans
[ https://issues.apache.org/jira/browse/AMQ-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493490#comment-17493490 ] Matt Pavlovich commented on AMQ-2725: - This has been fixed for networkConnectors for a while. For sure fixed in 5.15.x series. Try 5.16.4 and re-open if there are any issues. > Issues With NetworkConnector and NetworkBridge MBeans > -- > > Key: AMQ-2725 > URL: https://issues.apache.org/jira/browse/AMQ-2725 > Project: ActiveMQ > Issue Type: Bug > Components: JMX >Affects Versions: 5.3.1 > Environment: ActiveMQ 5.3.1 on Windoze XP Pro SP2 >Reporter: Joe Francis >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > > On the JConsole, when you invoke the 'Stop' operation on the > NetworkConnectorView MBean, the corresponding NetworkBridgeView MBean > disappears as expected; however, when you invoke the NetworkConnectorView's > 'Start' operation to restart the bridge, the corresponding NetworkBridgeView > MBean does not reappear. > When you invoke the NetworkBridgeView MBean's Stop operation, the MBean > disappears. So there is no point having a Start operation for this MBean. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (AMQ-5130) If a STOMP listener attempts to connect to an OpenWire transport connector the broker dies
[
https://issues.apache.org/jira/browse/AMQ-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich reassigned AMQ-5130:
---
Assignee: Matt Pavlovich
> If a STOMP listener attempts to connect to an OpenWire transport connector
> the broker dies
> --
>
> Key: AMQ-5130
> URL: https://issues.apache.org/jira/browse/AMQ-5130
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.15.13
> Environment: Linux Centos 6.4 Apache ActiveMQ 5.9.0, Apache ActiveMQ
> demo STOMP listener
>Reporter: Matthew Western
>Assignee: Matt Pavlovich
>Priority: Major
> Fix For: 5.17.1
>
> Attachments: AMQ5130.patch
>
>
> If a STOMP listener attempts to connect to AMQ with an nio openwire transport
> connector URI the broker dies (The JVM terminates with an out of memory
> error).
> I have consistently reproduced this using the test STOMP listener provided
> with AMQ 5.9.0. I have not checked to see what happens with the STOMP
> publisher but I imagine the results would be the same.
> I discovered this due to accidentally using the wrong URI with my STOMP
> client.
> I think this is a serious issue as it could be exploited as a DOS attack on
> known broker URIs.
> My AMQ configuration file is as follows:
> http://activemq.apache.org/schema/core;
> brokerName="broker2" dataDirectory="${activemq.data}"
> networkConnectorStartAsync="true" advisorySupport="true">
>
>
>
>
> memoryLimit="200mb" advisoryForConsumed="true" advisoryForDelivery="true">
>
>useQueueForQueueMessages="true" />
>
>
> memoryLimit="200mb" advisoryForConsumed="true" advisoryForDelivery="true">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> uri="nio://somehost.com:61610"
> updateClusterClients="true"
> rebalanceClusterClients="true"
> updateClusterClientsOnRemove="true"
> />
> uri="stomp+nio://somehost.com:61614"
> updateClusterClients="true"
> rebalanceClusterClients="true"
> updateClusterClientsOnRemove="true"
> />
>
>
>
>
>
> The listener terminates immediately upon starting with:
> cannot sysread(): Connection reset by peer
> And the broker JVM dies with the following hs_errpid*.log error:
> #
> # There is insufficient memory for the Java Runtime Environment to continue.
> # Native memory allocation (malloc) failed to allocate 693723136 bytes for
> committing reserved memory.
> # Possible reasons:
> # The system is out of physical RAM or swap space
> # In 32 bit mode, the process size limit was hit
> # Possible solutions:
> # Reduce memory load on the system
> # Increase physical memory or swap space
> # Check if swap backing store is full
> # Use 64 bit Java on a 64 bit OS
> # Decrease Java heap size (-Xmx/-Xms)
> # Decrease number of Java threads
> # Decrease Java thread stack sizes (-Xss)
> # Set larger code cache with -XX:ReservedCodeCacheSize=
> # This output file may be truncated or incomplete.
> #
> # Out of Memory Error (os_linux.cpp:2718), pid=8783, tid=140478943950592
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build
> 1.7.0_45-b18)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode
> linux-amd64 compressed oops)
> # Failed to write core dump. Core dumps have been disabled. To enable core
> dumping, try "ulimit -c unlimited" before starting Java again
> #
> --- T H R E A D ---
> Current thread (0x7fc3c8086000): VMThread [stack:
> 0x7fc3cd7d7000,0x7fc3cd8d8000] [id=8785]
> Stack: [0x7fc3cd7d7000,0x7fc3cd8d8000], sp=0x7fc3cd8d62d0, free
> space=1020k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> V [libjvm.so+0x992c8a] VMError::report_and_die()+0x2ea
> V [libjvm.so+0x49319b] report_vm_out_of_memory(char const*, int, unsigned
> long, char const*)+0x9b
> V [libjvm.so+0x81310e] os::Linux::commit_memory_impl(char*, unsigned long,
> bool)+0xfe
> V [libjvm.so+0x8135bf] os::Linux::commit_memory_impl(char*, unsigned long,
[jira] [Updated] (AMQ-5130) If a STOMP listener attempts to connect to an OpenWire transport connector the broker dies
[
https://issues.apache.org/jira/browse/AMQ-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated AMQ-5130:
Fix Version/s: 5.17.1
(was: 5.17.0)
> If a STOMP listener attempts to connect to an OpenWire transport connector
> the broker dies
> --
>
> Key: AMQ-5130
> URL: https://issues.apache.org/jira/browse/AMQ-5130
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.15.13
> Environment: Linux Centos 6.4 Apache ActiveMQ 5.9.0, Apache ActiveMQ
> demo STOMP listener
>Reporter: Matthew Western
>Priority: Major
> Fix For: 5.17.1
>
> Attachments: AMQ5130.patch
>
>
> If a STOMP listener attempts to connect to AMQ with an nio openwire transport
> connector URI the broker dies (The JVM terminates with an out of memory
> error).
> I have consistently reproduced this using the test STOMP listener provided
> with AMQ 5.9.0. I have not checked to see what happens with the STOMP
> publisher but I imagine the results would be the same.
> I discovered this due to accidentally using the wrong URI with my STOMP
> client.
> I think this is a serious issue as it could be exploited as a DOS attack on
> known broker URIs.
> My AMQ configuration file is as follows:
> http://activemq.apache.org/schema/core;
> brokerName="broker2" dataDirectory="${activemq.data}"
> networkConnectorStartAsync="true" advisorySupport="true">
>
>
>
>
> memoryLimit="200mb" advisoryForConsumed="true" advisoryForDelivery="true">
>
>useQueueForQueueMessages="true" />
>
>
> memoryLimit="200mb" advisoryForConsumed="true" advisoryForDelivery="true">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> uri="nio://somehost.com:61610"
> updateClusterClients="true"
> rebalanceClusterClients="true"
> updateClusterClientsOnRemove="true"
> />
> uri="stomp+nio://somehost.com:61614"
> updateClusterClients="true"
> rebalanceClusterClients="true"
> updateClusterClientsOnRemove="true"
> />
>
>
>
>
>
> The listener terminates immediately upon starting with:
> cannot sysread(): Connection reset by peer
> And the broker JVM dies with the following hs_errpid*.log error:
> #
> # There is insufficient memory for the Java Runtime Environment to continue.
> # Native memory allocation (malloc) failed to allocate 693723136 bytes for
> committing reserved memory.
> # Possible reasons:
> # The system is out of physical RAM or swap space
> # In 32 bit mode, the process size limit was hit
> # Possible solutions:
> # Reduce memory load on the system
> # Increase physical memory or swap space
> # Check if swap backing store is full
> # Use 64 bit Java on a 64 bit OS
> # Decrease Java heap size (-Xmx/-Xms)
> # Decrease number of Java threads
> # Decrease Java thread stack sizes (-Xss)
> # Set larger code cache with -XX:ReservedCodeCacheSize=
> # This output file may be truncated or incomplete.
> #
> # Out of Memory Error (os_linux.cpp:2718), pid=8783, tid=140478943950592
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build
> 1.7.0_45-b18)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode
> linux-amd64 compressed oops)
> # Failed to write core dump. Core dumps have been disabled. To enable core
> dumping, try "ulimit -c unlimited" before starting Java again
> #
> --- T H R E A D ---
> Current thread (0x7fc3c8086000): VMThread [stack:
> 0x7fc3cd7d7000,0x7fc3cd8d8000] [id=8785]
> Stack: [0x7fc3cd7d7000,0x7fc3cd8d8000], sp=0x7fc3cd8d62d0, free
> space=1020k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> V [libjvm.so+0x992c8a] VMError::report_and_die()+0x2ea
> V [libjvm.so+0x49319b] report_vm_out_of_memory(char const*, int, unsigned
> long, char const*)+0x9b
> V [libjvm.so+0x81310e] os::Linux::commit_memory_impl(char*, unsigned long,
> bool)+0xfe
> V [libjvm.so+0x8135bf] os::Linux::commit_memory_impl(char*, unsigned long,
> unsigned
[jira] [Updated] (AMQ-4764) Expose Authorization entries via JMX
[ https://issues.apache.org/jira/browse/AMQ-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-4764: Fix Version/s: 5.17.1 (was: 5.17.0) > Expose Authorization entries via JMX > > > Key: AMQ-4764 > URL: https://issues.apache.org/jira/browse/AMQ-4764 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 5.8.0 > Environment: All >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Fix For: 5.17.1 > > > It would be really handy to expose the AuthorizationMap via JMX so admins can > validate what the broker "sees" as the active configuration. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (AMQ-6883) Configuration issue if service wrapper is used
[ https://issues.apache.org/jira/browse/AMQ-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493487#comment-17493487 ] Matt Pavlovich commented on AMQ-6883: - Updated wrappers for macos, win32, win64, linux-32 and linux-64. * -Xms=1024 * dedicatedTaskRunner=false > Configuration issue if service wrapper is used > -- > > Key: AMQ-6883 > URL: https://issues.apache.org/jira/browse/AMQ-6883 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.15.14 >Reporter: Joachim Glink >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > Attachments: JIRA_AMQ_6883.patch > > Time Spent: 10m > Remaining Estimate: 0h > > The documentation > (http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html) > > states that the DedicatedTaskRunner is disabled by default from 5.6 onwards. > This is true if the ActiveMQ is started directly, e.g. with "activemq.bat > start". > But if the ActiveMQ is started as a windows service from the wrapper.exe the > DedicatedTaskRunner is still activated because the wrapper.conf has > following entry: > wrapper.java.additional.8=-Dorg.apache.activemq.UseDedicatedTaskRunner=true > Please make the default configuration of AMQ similar across all start-ups. > see mailing list entry: > http://activemq.2283324.n4.nabble.com/UseDedicatedTaskRunner-configuration-td4734704.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work logged] (AMQ-6883) Configuration issue if service wrapper is used
[ https://issues.apache.org/jira/browse/AMQ-6883?focusedWorklogId=728503=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728503 ] ASF GitHub Bot logged work on AMQ-6883: --- Author: ASF GitHub Bot Created on: 16/Feb/22 20:25 Start Date: 16/Feb/22 20:25 Worklog Time Spent: 10m Work Description: mattrpav opened a new pull request #772: URL: https://github.com/apache/activemq/pull/772 … bin/*.bat file for memory and dedicatedTaskRunner -- 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. To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 728503) Remaining Estimate: 0h Time Spent: 10m > Configuration issue if service wrapper is used > -- > > Key: AMQ-6883 > URL: https://issues.apache.org/jira/browse/AMQ-6883 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.15.14 >Reporter: Joachim Glink >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > Attachments: JIRA_AMQ_6883.patch > > Time Spent: 10m > Remaining Estimate: 0h > > The documentation > (http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html) > > states that the DedicatedTaskRunner is disabled by default from 5.6 onwards. > This is true if the ActiveMQ is started directly, e.g. with "activemq.bat > start". > But if the ActiveMQ is started as a windows service from the wrapper.exe the > DedicatedTaskRunner is still activated because the wrapper.conf has > following entry: > wrapper.java.additional.8=-Dorg.apache.activemq.UseDedicatedTaskRunner=true > Please make the default configuration of AMQ similar across all start-ups. > see mailing list entry: > http://activemq.2283324.n4.nabble.com/UseDedicatedTaskRunner-configuration-td4734704.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (AMQ-6883) Configuration issue if service wrapper is used
[ https://issues.apache.org/jira/browse/AMQ-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-6883 started by Matt Pavlovich. --- > Configuration issue if service wrapper is used > -- > > Key: AMQ-6883 > URL: https://issues.apache.org/jira/browse/AMQ-6883 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.15.14 >Reporter: Joachim Glink >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > Attachments: JIRA_AMQ_6883.patch > > > The documentation > (http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html) > > states that the DedicatedTaskRunner is disabled by default from 5.6 onwards. > This is true if the ActiveMQ is started directly, e.g. with "activemq.bat > start". > But if the ActiveMQ is started as a windows service from the wrapper.exe the > DedicatedTaskRunner is still activated because the wrapper.conf has > following entry: > wrapper.java.additional.8=-Dorg.apache.activemq.UseDedicatedTaskRunner=true > Please make the default configuration of AMQ similar across all start-ups. > see mailing list entry: > http://activemq.2283324.n4.nabble.com/UseDedicatedTaskRunner-configuration-td4734704.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (AMQ-5137) make networkConnector decreaseNetworkConsumerPriority="true" the default
[ https://issues.apache.org/jira/browse/AMQ-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-5137 started by Matt Pavlovich. --- > make networkConnector decreaseNetworkConsumerPriority="true" the default > > > Key: AMQ-5137 > URL: https://issues.apache.org/jira/browse/AMQ-5137 > Project: ActiveMQ > Issue Type: Improvement >Affects Versions: 5.15.13 >Reporter: Gary Tully >Assignee: Matt Pavlovich >Priority: Major > Labels: mesh, networkConnectors > Fix For: 5.17.0 > > > It makes sense to bias local consumers, to avoid hops where possible. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (AMQ-8493) Minor deprecated clean-ups in activemq-client
[ https://issues.apache.org/jira/browse/AMQ-8493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-8493 started by Matt Pavlovich. --- > Minor deprecated clean-ups in activemq-client > - > > Key: AMQ-8493 > URL: https://issues.apache.org/jira/browse/AMQ-8493 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (AMQ-8493) Minor deprecated clean-ups in activemq-client
[ https://issues.apache.org/jira/browse/AMQ-8493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-8493: --- Assignee: Matt Pavlovich > Minor deprecated clean-ups in activemq-client > - > > Key: AMQ-8493 > URL: https://issues.apache.org/jira/browse/AMQ-8493 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8493) Minor deprecated clean-ups in activemq-client
[ https://issues.apache.org/jira/browse/AMQ-8493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-8493: Fix Version/s: 5.17.0 > Minor deprecated clean-ups in activemq-client > - > > Key: AMQ-8493 > URL: https://issues.apache.org/jira/browse/AMQ-8493 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (AMQ-8493) Minor deprecated clean-ups in activemq-client
Matt Pavlovich created AMQ-8493: --- Summary: Minor deprecated clean-ups in activemq-client Key: AMQ-8493 URL: https://issues.apache.org/jira/browse/AMQ-8493 Project: ActiveMQ Issue Type: Task Reporter: Matt Pavlovich -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8492) Clean up warns and deprecated usages in KahaDB
[ https://issues.apache.org/jira/browse/AMQ-8492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-8492: Fix Version/s: NEEDS_REVIEW (was: 5.17.0) > Clean up warns and deprecated usages in KahaDB > -- > > Key: AMQ-8492 > URL: https://issues.apache.org/jira/browse/AMQ-8492 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: NEEDS_REVIEW > > > The new Long() deprecated usage is coming from activemq-protobuf generated > classes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8492) Clean up warns and deprecated usages in KahaDB
[ https://issues.apache.org/jira/browse/AMQ-8492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-8492: Fix Version/s: 5.x > Clean up warns and deprecated usages in KahaDB > -- > > Key: AMQ-8492 > URL: https://issues.apache.org/jira/browse/AMQ-8492 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.x, NEEDS_REVIEW > > > The new Long() deprecated usage is coming from activemq-protobuf generated > classes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8492) Clean up warns and deprecated usages in KahaDB
[ https://issues.apache.org/jira/browse/AMQ-8492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-8492: Description: The new Long() deprecated usage is coming from activemq-protobuf generated classes. > Clean up warns and deprecated usages in KahaDB > -- > > Key: AMQ-8492 > URL: https://issues.apache.org/jira/browse/AMQ-8492 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > > The new Long() deprecated usage is coming from activemq-protobuf generated > classes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (AMQ-8492) Clean up warns and deprecated usages in KahaDB
[ https://issues.apache.org/jira/browse/AMQ-8492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-8492: --- Assignee: Matt Pavlovich > Clean up warns and deprecated usages in KahaDB > -- > > Key: AMQ-8492 > URL: https://issues.apache.org/jira/browse/AMQ-8492 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8492) Clean up warns and deprecated usages in KahaDB
[ https://issues.apache.org/jira/browse/AMQ-8492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-8492: Fix Version/s: 5.17.0 > Clean up warns and deprecated usages in KahaDB > -- > > Key: AMQ-8492 > URL: https://issues.apache.org/jira/browse/AMQ-8492 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Priority: Minor > Fix For: 5.17.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (AMQ-8492) Clean up warns and deprecated usages in KahaDB
Matt Pavlovich created AMQ-8492: --- Summary: Clean up warns and deprecated usages in KahaDB Key: AMQ-8492 URL: https://issues.apache.org/jira/browse/AMQ-8492 Project: ActiveMQ Issue Type: Task Reporter: Matt Pavlovich -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3627) Allow properties to configure 'new' broker attributes and load from a file
[ https://issues.apache.org/jira/browse/ARTEMIS-3627?focusedWorklogId=728393=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728393 ] ASF GitHub Bot logged work on ARTEMIS-3627: --- Author: ASF GitHub Bot Created on: 16/Feb/22 17:58 Start Date: 16/Feb/22 17:58 Worklog Time Spent: 10m Work Description: gtully opened a new pull request #3959: URL: https://github.com/apache/activemq-artemis/pull/3959 …for long values -- 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. To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 728393) Time Spent: 5h (was: 4h 50m) > Allow properties to configure 'new' broker attributes and load from a file > -- > > Key: ARTEMIS-3627 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3627 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.20.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.21.0 > > Time Spent: 5h > Remaining Estimate: 0h > > Following up on ARTEMIS-851, where simple set attributes can be overridden > via system properties. This enhancement will allow properties to be loaded > from broker.properties and allow additions to lists and maps. > The additions to the collections require some naming convention. Many of the > elements already support a name attribute and this can be used to locate and > or create new entries. > The idea is that a plain broker can be augmented with the presence of a > properties file to add a new acceptor called "tcp" using properties of the > form: > acceptorConfigurations.tcp.params.host=localhost > acceptorConfigurations.tcp.params.port=61616 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3660) broker balancer - tidy up configuration; rename to connection router
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?focusedWorklogId=728391=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728391
]
ASF GitHub Bot logged work on ARTEMIS-3660:
---
Author: ASF GitHub Bot
Created on: 16/Feb/22 17:51
Start Date: 16/Feb/22 17:51
Worklog Time Spent: 10m
Work Description: gtully edited a comment on pull request #3932:
URL:
https://github.com/apache/activemq-artemis/pull/3932#issuecomment-1041824750
some more internal class rename to follow from @brusdev - leaving as draft
till complete. Best to get this all done at once.
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 728391)
Time Spent: 3h 10m (was: 3h)
> broker balancer - tidy up configuration; rename to connection router
>
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> Going further, I am renaming to better reflect what it does and we can make
> it stable.
> The new name is "Connection Routing" and the "Connection Routers" do
> balancing or partitioning or redirection.
>
> It has been flagged as experimental in the doc[1]:
> This feature is still *EXPERIMENTAL* and not meant to be run in production
> yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
> [1]
> [https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
> new doc will be:
> [https://activemq.apache.org/components/artemis/documentation/latest/connection-routers.html|https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (AMQ-8486) ActiveMQ 5.17.0 Release Plans and Change notes
[ https://issues.apache.org/jira/browse/AMQ-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-8486: Description: Current plans for the release: * Apache Camel removal * Log4j2 support * JMS 2.0 preview support * KahaDB metrics update to use (micro or nanoseconds) * Make a pass at removing deprecated methods * Dependency updates Breaking changes: * Apache Camel removal (developers impated) * sendDuplicateFromStoreToDLQ (logging and DLQ processors impacted) * KahaDB metrics unit change (monitoring and alerting impacted) was: Current plans for the release: * Apache Camel removal * Log4j2 support * JMS 2.0 preview support * KahaDB metrics update to use (micro or nanoseconds) * Dependency updates Breaking changes: * Apache Camel removal (developers impated) * sendDuplicateFromStoreToDLQ (logging and DLQ processors impacted) * KahaDB metrics unit change (monitoring and alerting impacted) > ActiveMQ 5.17.0 Release Plans and Change notes > -- > > Key: AMQ-8486 > URL: https://issues.apache.org/jira/browse/AMQ-8486 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.17.0 > > > Current plans for the release: > * Apache Camel removal > * Log4j2 support > * JMS 2.0 preview support > * KahaDB metrics update to use (micro or nanoseconds) > * Make a pass at removing deprecated methods > * Dependency updates > Breaking changes: > * Apache Camel removal (developers impated) > * sendDuplicateFromStoreToDLQ (logging and DLQ processors impacted) > * KahaDB metrics unit change (monitoring and alerting impacted) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARTEMIS-3666) Update to PostgreSQL 42.3.3
[ https://issues.apache.org/jira/browse/ARTEMIS-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-3666: Description: Update to the latest PostgreSQL release, 42.3.3. (was: Update to the latest PostgreSQL release, 42.3.2.) Summary: Update to PostgreSQL 42.3.3 (was: Update to PostgreSQL 42.3.2) > Update to PostgreSQL 42.3.3 > --- > > Key: ARTEMIS-3666 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3666 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.21.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Update to the latest PostgreSQL release, 42.3.3. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (ARTEMIS-3666) Update to PostgreSQL 42.3.2
[ https://issues.apache.org/jira/browse/ARTEMIS-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened ARTEMIS-3666: - > Update to PostgreSQL 42.3.2 > --- > > Key: ARTEMIS-3666 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3666 > Project: ActiveMQ Artemis > Issue Type: Dependency upgrade >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.21.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Update to the latest PostgreSQL release, 42.3.2. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (AMQ-8491) Document additional cachedLDAPAuthorizationMap properties
Chris Krusch created AMQ-8491:
-
Summary: Document additional cachedLDAPAuthorizationMap properties
Key: AMQ-8491
URL: https://issues.apache.org/jira/browse/AMQ-8491
Project: ActiveMQ
Issue Type: Improvement
Components: Documentation
Reporter: Chris Krusch
The following supported properties are not documented on the cached ldap
authorization modules documentation page at:
[https://activemq.apache.org/cached-ldap-authorization-module]
Requesting doc update to include them:
{{Property Default Description}}
{{groupNameAttribute cn Attribute of group objects that contains }}
{{ the group name}}
{{groupObjectClass groupOfNames Object class that identifies group objects}}
{{userNameAttribute uid Attribute of user objects that contains}}
{{ the user name}}
{{userObjectClass person Object class that identifies user objects}}
{{The descriptions for the properties are my suggestions - someone may want to
review for accuracy and/or completeness.}}
{{Not sure what version these properties were added - we've been using them in
our configs since 2014 so it's been a long time!}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3660) broker balancer - tidy up configuration; rename to connection router
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?focusedWorklogId=728323=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728323
]
ASF GitHub Bot logged work on ARTEMIS-3660:
---
Author: ASF GitHub Bot
Created on: 16/Feb/22 16:06
Start Date: 16/Feb/22 16:06
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3932:
URL:
https://github.com/apache/activemq-artemis/pull/3932#issuecomment-1041824750
some more internal class rename to follow form @brusdev - leaving as draft
till complete. Best to get this all done at once.
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 728323)
Time Spent: 3h (was: 2h 50m)
> broker balancer - tidy up configuration; rename to connection router
>
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> Going further, I am renaming to better reflect what it does and we can make
> it stable.
> The new name is "Connection Routing" and the "Connection Routers" do
> balancing or partitioning or redirection.
>
> It has been flagged as experimental in the doc[1]:
> This feature is still *EXPERIMENTAL* and not meant to be run in production
> yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
> [1]
> [https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
> new doc will be:
> [https://activemq.apache.org/components/artemis/documentation/latest/connection-routers.html|https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (AMQ-8486) ActiveMQ 5.17.0 Release Plans and Change notes
[
https://issues.apache.org/jira/browse/AMQ-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493289#comment-17493289
]
Jean-Baptiste Onofré commented on AMQ-8486:
---
As discussed together, I will create a PR to add {{CHANGES.md}} with some
details.
> ActiveMQ 5.17.0 Release Plans and Change notes
> --
>
> Key: AMQ-8486
> URL: https://issues.apache.org/jira/browse/AMQ-8486
> Project: ActiveMQ
> Issue Type: Task
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.17.0
>
>
> Current plans for the release:
> * Apache Camel removal
> * Log4j2 support
> * JMS 2.0 preview support
> * KahaDB metrics update to use (micro or nanoseconds)
> * Dependency updates
> Breaking changes:
> * Apache Camel removal (developers impated)
> * sendDuplicateFromStoreToDLQ (logging and DLQ processors impacted)
> * KahaDB metrics unit change (monitoring and alerting impacted)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3660) broker balancer - tidy up configuration; rename to connection router
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?focusedWorklogId=728256=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728256
]
ASF GitHub Bot logged work on ARTEMIS-3660:
---
Author: ASF GitHub Bot
Created on: 16/Feb/22 14:58
Start Date: 16/Feb/22 14:58
Worklog Time Spent: 10m
Work Description: brusdev commented on pull request #3932:
URL:
https://github.com/apache/activemq-artemis/pull/3932#issuecomment-1041580163
@gtully I'll push a few commits to finish refactoring for doc, packaging,
..., feel free to drop or squash them
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 728256)
Time Spent: 2h 50m (was: 2h 40m)
> broker balancer - tidy up configuration; rename to connection router
>
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> Going further, I am renaming to better reflect what it does and we can make
> it stable.
> The new name is "Connection Routing" and the "Connection Routers" do
> balancing or partitioning or redirection.
>
> It has been flagged as experimental in the doc[1]:
> This feature is still *EXPERIMENTAL* and not meant to be run in production
> yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
> [1]
> [https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
> new doc will be:
> [https://activemq.apache.org/components/artemis/documentation/latest/connection-routers.html|https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (AMQ-8490) Cannot configure Jetty for HttpsTransport
bogdan t. created AMQ-8490:
--
Summary: Cannot configure Jetty for HttpsTransport
Key: AMQ-8490
URL: https://issues.apache.org/jira/browse/AMQ-8490
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Reporter: bogdan t.
When using HttpTransport I can configure jetty by providing jetty.xml
{noformat}
http://localhost:8088?jetty.config=src/test/resources/httptransport.xml"/>
{noformat}
The same is *not possible* for secure https, even when providing jetty.config
property, it's not processed as:
{noformat}
org.apache.activemq.transport.http.HttpTransportFactory#doBind
calls: result.setJettyOptions(jettyOptions);
org.apache.activemq.transport.https.HttpsTransportFactory#doBind
do not call neither super method not call JettyOptions directly
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3660) broker balancer - tidy up configuration; rename to connection router
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?focusedWorklogId=728142=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728142
]
ASF GitHub Bot logged work on ARTEMIS-3660:
---
Author: ASF GitHub Bot
Created on: 16/Feb/22 11:40
Start Date: 16/Feb/22 11:40
Worklog Time Spent: 10m
Work Description: pwright commented on pull request #3932:
URL:
https://github.com/apache/activemq-artemis/pull/3932#issuecomment-1041400668
@gtully doh! I searched the diff for .md, but TIL how to filter files in a
PR
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 728142)
Time Spent: 2h 40m (was: 2.5h)
> broker balancer - tidy up configuration; rename to connection router
>
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> Going further, I am renaming to better reflect what it does and we can make
> it stable.
> The new name is "Connection Routing" and the "Connection Routers" do
> balancing or partitioning or redirection.
>
> It has been flagged as experimental in the doc[1]:
> This feature is still *EXPERIMENTAL* and not meant to be run in production
> yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
> [1]
> [https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
> new doc will be:
> [https://activemq.apache.org/components/artemis/documentation/latest/connection-routers.html|https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3660) broker balancer - tidy up configuration; rename to connection router
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?focusedWorklogId=728141=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728141
]
ASF GitHub Bot logged work on ARTEMIS-3660:
---
Author: ASF GitHub Bot
Created on: 16/Feb/22 11:39
Start Date: 16/Feb/22 11:39
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3932:
URL:
https://github.com/apache/activemq-artemis/pull/3932#issuecomment-1041399573
@pwright for sure and there is:
https://github.com/apache/activemq-artemis/pull/3932/files?file-filters%5B%5D=.md=true
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 728141)
Time Spent: 2.5h (was: 2h 20m)
> broker balancer - tidy up configuration; rename to connection router
>
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> Going further, I am renaming to better reflect what it does and we can make
> it stable.
> The new name is "Connection Routing" and the "Connection Routers" do
> balancing or partitioning or redirection.
>
> It has been flagged as experimental in the doc[1]:
> This feature is still *EXPERIMENTAL* and not meant to be run in production
> yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
> [1]
> [https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
> new doc will be:
> [https://activemq.apache.org/components/artemis/documentation/latest/connection-routers.html|https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work logged] (AMQ-8489) fail fast and obviously if building on something other than Java 11+
[ https://issues.apache.org/jira/browse/AMQ-8489?focusedWorklogId=728139=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728139 ] ASF GitHub Bot logged work on AMQ-8489: --- Author: ASF GitHub Bot Created on: 16/Feb/22 11:33 Start Date: 16/Feb/22 11:33 Worklog Time Spent: 10m Work Description: gemmellr opened a new pull request #769: URL: https://github.com/apache/activemq/pull/769 Aligns main branch behaviour with proposed 5.16.x branch changes in #768 -- 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. To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 728139) Remaining Estimate: 0h Time Spent: 10m > fail fast and obviously if building on something other than Java 11+ > > > Key: AMQ-8489 > URL: https://issues.apache.org/jira/browse/AMQ-8489 > Project: ActiveMQ > Issue Type: Task >Affects Versions: 5.17.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.17.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The main/5.17.x build requires you build using Java 11+. It obviously fails > if run on e.g 8, which the 5.16.x build requires is used. It does fail > reasonably fast, but only after e.g installing the root pom. There is an > enforcer check for the Java version already in the parent, it just is > checking for Java 8. Replace it with one to make the build fail immediately > and in a quickly obvious "you must build using Java 11+" way. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8489) fail fast and obviously if building on something other than Java 11+
[ https://issues.apache.org/jira/browse/AMQ-8489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated AMQ-8489: Description: The main/5.17.x build requires you build using Java 11+. It obviously fails if run on e.g 8, which the 5.16.x build requires is used. It does fail reasonably fast, but only after e.g installing the root pom. There is an enforcer check for the Java version already in the parent, it just is checking for Java 8. Replace it with one to make the build fail immediately and in a quickly obvious "you must build using Java 11+" way. (was: The main/5.17.x build requires you build using Java 11+. It obviously fails if run on e.g 8, which the 5.16.x build requires is used. It does fail reasonably fast, but only after e.g installing the root pom. There is an enforcer check for the Java version already, it just is checking for Java 8. Add an enforcer check (or rather, replace the ineffective existing one) to make the build fail immediately and in a quickly obvious "you must build using Java 8" way.) > fail fast and obviously if building on something other than Java 11+ > > > Key: AMQ-8489 > URL: https://issues.apache.org/jira/browse/AMQ-8489 > Project: ActiveMQ > Issue Type: Task >Affects Versions: 5.17.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.17.0 > > > The main/5.17.x build requires you build using Java 11+. It obviously fails > if run on e.g 8, which the 5.16.x build requires is used. It does fail > reasonably fast, but only after e.g installing the root pom. There is an > enforcer check for the Java version already in the parent, it just is > checking for Java 8. Replace it with one to make the build fail immediately > and in a quickly obvious "you must build using Java 11+" way. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8489) fail fast and obviously if building on something other than Java 11+
[ https://issues.apache.org/jira/browse/AMQ-8489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated AMQ-8489: Description: The main/5.17.x build requires you build using Java 11+. It obviously fails if run on e.g 8, which the 5.16.x build requires is used. It does fail reasonably fast, but only after e.g installing the root pom. There is an enforcer check for the Java version already, it just is checking for Java 8. Add an enforcer check (or rather, replace the ineffective existing one) to make the build fail immediately and in a quickly obvious "you must build using Java 8" way. was: The 5.16.x build requires you build using Java 8. It fails if run on e.g 11, which the main/5.17.x build requires is used, and people increasingly have as their default JDK regardless. Add an enforcer check (or rather, replace the ineffective existing one) to make the build fail immediately and in a quickly obvious "you must build using Java 8" way. > fail fast and obviously if building on something other than Java 11+ > > > Key: AMQ-8489 > URL: https://issues.apache.org/jira/browse/AMQ-8489 > Project: ActiveMQ > Issue Type: Task >Affects Versions: 5.17.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.17.0 > > > The main/5.17.x build requires you build using Java 11+. It obviously fails > if run on e.g 8, which the 5.16.x build requires is used. It does fail > reasonably fast, but only after e.g installing the root pom. There is an > enforcer check for the Java version already, it just is checking for Java 8. > > Add an enforcer check (or rather, replace the ineffective existing one) to > make the build fail immediately and in a quickly obvious "you must build > using Java 8" way. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8489) fail fast and obviously if building on something other than Java 11+
[ https://issues.apache.org/jira/browse/AMQ-8489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated AMQ-8489: Fix Version/s: 5.17.0 (was: 5.16.5) > fail fast and obviously if building on something other than Java 11+ > > > Key: AMQ-8489 > URL: https://issues.apache.org/jira/browse/AMQ-8489 > Project: ActiveMQ > Issue Type: Task >Affects Versions: 5.17.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.17.0 > > > The 5.16.x build requires you build using Java 8. It fails if run on e.g 11, > which the main/5.17.x build requires is used, and people increasingly have as > their default JDK regardless. > > Add an enforcer check (or rather, replace the ineffective existing one) to > make the build fail immediately and in a quickly obvious "you must build > using Java 8" way. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (AMQ-8489) fail fast and obviously if building on something other than Java 11+
[ https://issues.apache.org/jira/browse/AMQ-8489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated AMQ-8489: Affects Version/s: 5.17.0 (was: 5.16.4) > fail fast and obviously if building on something other than Java 11+ > > > Key: AMQ-8489 > URL: https://issues.apache.org/jira/browse/AMQ-8489 > Project: ActiveMQ > Issue Type: Task >Affects Versions: 5.17.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.16.5 > > > The 5.16.x build requires you build using Java 8. It fails if run on e.g 11, > which the main/5.17.x build requires is used, and people increasingly have as > their default JDK regardless. > > Add an enforcer check (or rather, replace the ineffective existing one) to > make the build fail immediately and in a quickly obvious "you must build > using Java 8" way. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (AMQ-8489) fail fast and obviously if building on something other than Java 11+
Robbie Gemmell created AMQ-8489: --- Summary: fail fast and obviously if building on something other than Java 11+ Key: AMQ-8489 URL: https://issues.apache.org/jira/browse/AMQ-8489 Project: ActiveMQ Issue Type: Task Affects Versions: 5.16.4 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 5.16.5 The 5.16.x build requires you build using Java 8. It fails if run on e.g 11, which the main/5.17.x build requires is used, and people increasingly have as their default JDK regardless. Add an enforcer check (or rather, replace the ineffective existing one) to make the build fail immediately and in a quickly obvious "you must build using Java 8" way. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3660) broker balancer - tidy up configuration; rename to connection router
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?focusedWorklogId=728135=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728135
]
ASF GitHub Bot logged work on ARTEMIS-3660:
---
Author: ASF GitHub Bot
Created on: 16/Feb/22 11:17
Start Date: 16/Feb/22 11:17
Worklog Time Spent: 10m
Work Description: pwright commented on pull request #3932:
URL:
https://github.com/apache/activemq-artemis/pull/3932#issuecomment-1041381705
@gtully should an update to
https://github.com/apache/activemq-artemis/blob/main/docs/user-manual/en/broker-balancers.md
be part of this PR?
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 728135)
Time Spent: 2h 20m (was: 2h 10m)
> broker balancer - tidy up configuration; rename to connection router
>
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> Going further, I am renaming to better reflect what it does and we can make
> it stable.
> The new name is "Connection Routing" and the "Connection Routers" do
> balancing or partitioning or redirection.
>
> It has been flagged as experimental in the doc[1]:
> This feature is still *EXPERIMENTAL* and not meant to be run in production
> yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
> [1]
> [https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
> new doc will be:
> [https://activemq.apache.org/components/artemis/documentation/latest/connection-routers.html|https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work logged] (AMQ-8488) fail fast and obviously if building on something other than Java 8
[ https://issues.apache.org/jira/browse/AMQ-8488?focusedWorklogId=728132=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728132 ] ASF GitHub Bot logged work on AMQ-8488: --- Author: ASF GitHub Bot Created on: 16/Feb/22 11:09 Start Date: 16/Feb/22 11:09 Worklog Time Spent: 10m Work Description: gemmellr opened a new pull request #768: URL: https://github.com/apache/activemq/pull/768 5.16.x must be built with Java 8. Main requires Java 11+. Many people just have Java 11 defaults now regardless. This enforces the restriction to make it fail quickly+obviously to aid during mismatches or slips when switching back and forth. -- 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. To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 728132) Remaining Estimate: 0h Time Spent: 10m > fail fast and obviously if building on something other than Java 8 > -- > > Key: AMQ-8488 > URL: https://issues.apache.org/jira/browse/AMQ-8488 > Project: ActiveMQ > Issue Type: Task >Affects Versions: 5.16.4 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 5.16.5 > > Time Spent: 10m > Remaining Estimate: 0h > > The 5.16.x build requires you build using Java 8. It fails if run on e.g 11, > which the main/5.17.x build requires is used, and people increasingly have as > their default JDK regardless. > > Add an enforcer check (or rather, replace the ineffective existing one) to > make the build fail immediately and in a quickly obvious "you must build > using Java 8" way. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (AMQNET-754) coktogelhebat
coktogelhebat created AMQNET-754: Summary: coktogelhebat Key: AMQNET-754 URL: https://issues.apache.org/jira/browse/AMQNET-754 Project: ActiveMQ .Net Issue Type: Bug Reporter: coktogelhebat Dapatkan uang jutaan rupiah dengan cara mudah lewat permainan judi togel. Akan semakin besar uangnya jika anda memilih situs [Agen Togel Online|http://51.161.54.227/] Terpercaya saat ini bernama Coktogel. Dapatkan juga bonus besar setiap harinya. Untuk pendaftaran dan info lebih lengkap, silahkan kunjungi situs taruhan togel COKTOGEL. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARTEMIS-3660) broker balancer - tidy up configuration; rename to connection router
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-3660:
Description:
the use of target in the configuration is a little confusing and extra
verbose...
in place of target-key I propose key-type
in place of target-key-filter I propose key-filter
While released, this feature is not yet used in the wild. I think we can just
fix this without regard to deprecation at this point.
Going further, I am renaming to better reflect what it does and we can make it
stable.
The new name is "Connection Routing" and the "Connection Routers" do balancing
or partitioning or redirection.
It has been flagged as experimental in the doc[1]:
This feature is still *EXPERIMENTAL* and not meant to be run in production yet.
Furthermore, its configuration can change until declared as {*}officially
stable{*}.
[1]
[https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
new doc will be:
[https://activemq.apache.org/components/artemis/documentation/latest/connection-routers.html|https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
was:
the use of target in the configuration is a little confusing and extra
verbose...
in place of target-key I propose key-type
in place of target-key-filter I propose key-filter
While released, this feature is not yet used in the wild. I think we can just
fix this without regard to deprecation at this point.
It has been flagged as experimental in the doc[1]:
h3. This feature is still *EXPERIMENTAL* and not meant to be run in production
yet. Furthermore, its configuration can change until declared as {*}officially
stable{*}.
[1]
https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html
> broker balancer - tidy up configuration; rename to connection router
>
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> Going further, I am renaming to better reflect what it does and we can make
> it stable.
> The new name is "Connection Routing" and the "Connection Routers" do
> balancing or partitioning or redirection.
>
> It has been flagged as experimental in the doc[1]:
> This feature is still *EXPERIMENTAL* and not meant to be run in production
> yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
> [1]
> [https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
> new doc will be:
> [https://activemq.apache.org/components/artemis/documentation/latest/connection-routers.html|https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html]
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (AMQ-8488) fail fast and obviously if building on something other than Java 8
Robbie Gemmell created AMQ-8488: --- Summary: fail fast and obviously if building on something other than Java 8 Key: AMQ-8488 URL: https://issues.apache.org/jira/browse/AMQ-8488 Project: ActiveMQ Issue Type: Task Affects Versions: 5.16.4 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 5.16.5 The 5.16.x build requires you build using Java 8. It fails if run on e.g 11, which the main/5.17.x build requires is used, and people increasingly have as their default JDK regardless. Add an enforcer check (or rather, replace the ineffective existing one) to make the build fail immediately and in a quickly obvious "you must build using Java 8" way. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARTEMIS-3660) broker balancer - tidy up configuration; rename to connection router
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-3660:
Summary: broker balancer - tidy up configuration; rename to connection
router (was: broker balancer - tidy up configuration naming)
> broker balancer - tidy up configuration; rename to connection router
>
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> It has been flagged as experimental in the doc[1]:
> h3. This feature is still *EXPERIMENTAL* and not meant to be run in
> production yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
>
> [1]
> https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (ARTEMIS-3660) broker balancer - tidy up configuration; rename to connection router
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned ARTEMIS-3660:
---
Assignee: Gary Tully
> broker balancer - tidy up configuration; rename to connection router
>
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Assignee: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> It has been flagged as experimental in the doc[1]:
> h3. This feature is still *EXPERIMENTAL* and not meant to be run in
> production yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
>
> [1]
> https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work logged] (ARTEMIS-3660) broker balancer - tidy up configuration naming
[
https://issues.apache.org/jira/browse/ARTEMIS-3660?focusedWorklogId=728126=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728126
]
ASF GitHub Bot logged work on ARTEMIS-3660:
---
Author: ASF GitHub Bot
Created on: 16/Feb/22 10:53
Start Date: 16/Feb/22 10:53
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3932:
URL:
https://github.com/apache/activemq-artemis/pull/3932#issuecomment-1041360576
done the rename, balancer -> routing package, Balancer to Router in class
names to reflect the xml config
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 728126)
Time Spent: 2h 10m (was: 2h)
> broker balancer - tidy up configuration naming
> --
>
> Key: ARTEMIS-3660
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3660
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
>Affects Versions: 2.20.0
>Reporter: Gary Tully
>Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> the use of target in the configuration is a little confusing and extra
> verbose...
> in place of target-key I propose key-type
> in place of target-key-filter I propose key-filter
>
> While released, this feature is not yet used in the wild. I think we can just
> fix this without regard to deprecation at this point.
>
> It has been flagged as experimental in the doc[1]:
> h3. This feature is still *EXPERIMENTAL* and not meant to be run in
> production yet. Furthermore, its configuration can change until declared as
> {*}officially stable{*}.
>
> [1]
> https://activemq.apache.org/components/artemis/documentation/latest/broker-balancers.html
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (AMQ-7426) Upgrade to log4j2
[
https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493167#comment-17493167
]
Robbie Gemmell commented on AMQ-7426:
-
The Log4J transitive dependency from Zookeeper related bits were excluded
(directly or via dependencyManagement) and reload4j was added to
activemq-partition as a dependency to serve in their place during AMQ-8472. The
classes included in activemq-all thus should be those from {_}reload4j{_},
which necessarily uses the same _org.apache.log4j_ namespace to serve their
intent to act as a substitute for Log4j. The
/META-INF/maven/ch.qos.reload4j/reload4j/ presence in the
activemq-all-5.16.4.jar file without a log4j equivalent (such as the
/META-INF/maven/log4j/log4j/ present in 5.16.3) further suggests that is indeed
the case. It should be trivial to confirm that either way by simply comparing
the actual contained classes with those from the individual reload4j/log4j jars.
(Aside: easier still, dont use activemq-all, use the specific components you
need and maintain visibility and control of what is actually being utilised)
> Upgrade to log4j2
> -
>
> Key: AMQ-7426
> URL: https://issues.apache.org/jira/browse/AMQ-7426
> Project: ActiveMQ
> Issue Type: Task
> Components: Broker
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.17.0
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> This JIRA will upgrade 5.17.x to use Log4J 2.x instead of 1.x
> (5.16.x was switched to using [reload4j|https://reload4j.qos.ch/] instead of
> Log4j 1.x via AMQ-8472 in 5.16.4)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (AMQ-8486) ActiveMQ 5.17.0 Release Plans and Change notes
[ https://issues.apache.org/jira/browse/AMQ-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-8486: - Assignee: Jean-Baptiste Onofré > ActiveMQ 5.17.0 Release Plans and Change notes > -- > > Key: AMQ-8486 > URL: https://issues.apache.org/jira/browse/AMQ-8486 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.17.0 > > > Current plans for the release: > * Apache Camel removal > * Log4j2 support > * JMS 2.0 preview support > * KahaDB metrics update to use (micro or nanoseconds) > * Dependency updates > Breaking changes: > * Apache Camel removal (developers impated) > * sendDuplicateFromStoreToDLQ (logging and DLQ processors impacted) > * KahaDB metrics unit change (monitoring and alerting impacted) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (AMQ-8470) Failed to start JMX connector Cannot bind to URL
[ https://issues.apache.org/jira/browse/AMQ-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493091#comment-17493091 ] Chris Scott commented on AMQ-8470: -- I can confirm that there is nothing else running on port 1099 (it works with JDK8 and 11 which kind of confirms this). I thought adding a list of versions where this issues arises would add more clarity, clearly it hasn't. So let me restate this With JDK17 running with activemq 5.16.3 the error occurs, the release notes state that 5.16.3 fully supports JDK9+ [https://activemq.apache.org/activemq-5016003-release] With JDK11 running activemq 5.16.3 the error does occur. > Failed to start JMX connector Cannot bind to URL > > > Key: AMQ-8470 > URL: https://issues.apache.org/jira/browse/AMQ-8470 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.15.12, 5.15.13, 5.15.15, 5.16.2, 5.16.3 >Reporter: Chris Scott >Assignee: Jean-Baptiste Onofré >Priority: Major > > With Java 17 from version 5.15.12 the following error is raised when the > ManagementContext is configured to create a jmx connector. > [JMX connector] WARN o.a.a.broker.jmx.ManagementContext - Failed to start > JMX connector Cannot bind to URL [rmi://localhost:1099/jmxrmi]: > javax.naming.CommunicationException [Root exception is > java.rmi.NoSuchObjectException: no such object in table]. Will restart > management to re-create JMX connector, trying to remedy this issue. > This error does not occur when running Java 8 or Java 11. > This error does not occur when running Java 17 against 5.15.11 of ActiveMQ > > This could be related to AMQ-7400 which introduced in 5.15.12 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
