[jira] [Closed] (AMQNET-588) Activemq nms api solution cleanup
[ https://issues.apache.org/jira/browse/AMQNET-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Andre Pearce closed AMQNET-588. --- > Activemq nms api solution cleanup > - > > Key: AMQNET-588 > URL: https://issues.apache.org/jira/browse/AMQNET-588 > Project: ActiveMQ .Net > Issue Type: Improvement > Components: NMS >Reporter: Krzysztof Porebski >Assignee: Michael Andre Pearce >Priority: Major > Fix For: 1.8.0 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > In order to be able to release AMQNET-565 some further clean up work has to > be done. > * Reorganize solution > * Update package and build scripts > * Migrate docs to docfx -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARTEMIS-2419) java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName during startup
[
https://issues.apache.org/jira/browse/ARTEMIS-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-2419:
Description:
Testing with Apache Artemis 2.9.0 I am encountering the following exception
during start-up. The issue is being thrown from a test site and I have not yet
identified what exactly triggers this problem.
Apache ActiveMQ Artemis 2.9.0
{noformat}
java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName
at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87)
at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:70)
at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:321)
at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:317)
at org.slf4j.impl.Slf4jLogger.info(Slf4jLogger.java:186)
at
org.apache.activemq.hawtio.branding.PluginContextListener.contextInitialized(PluginContextListener.java:53)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:876)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:532)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:839)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:344)
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1480)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1442)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:799)
at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
at org.eclipse.jetty.server.Server.start(Server.java:452)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
at org.eclipse.jetty.server.Server.doStart(Server.java:419)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.apache.activemq.artemis.component.WebServerComponent.start(WebServerComponent.java:229)
at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:105)
at
org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:150)
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:98)
at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:125)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)
Exception in thread "Thread-1 (ActiveMQ-client-netty-threads)"
java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName
at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87)
at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:70)
at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:321)
at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:67)
at
io.netty.util.internal.logging.LocationAwareSlf4JLogger.log(LocationAwareSlf4JLogger.java:46)
at
io.netty.util.internal.logging.LocationAwareSlf4JLogger.warn(LocationAwareSlf4JLogger.java:209)
at
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:908)
at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
Exception in thread "Thread-0 (ActiveMQ-client-netty-threads)"
java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName
at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87)
at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:70)
at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:321)
at
[jira] [Commented] (ARTEMIS-2419) java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName during startup
[ https://issues.apache.org/jira/browse/ARTEMIS-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880430#comment-16880430 ] Keith Wall commented on ARTEMIS-2419: - [~jbertram] thanks for the quick reply. it does indeed relate to an use-case where Artemis is upgraded. I'll confirm what we do. > java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName during startup > -- > > Key: ARTEMIS-2419 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2419 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.9.0 >Reporter: Keith Wall >Priority: Major > > Testing with Apache Artemis 2.9.0 I am encountering the following exception > during start-up. The issue is being thrown from a test site and I have not > yet identified what exactly triggers this problem. > Apache ActiveMQ Artemis 2.9.0 > java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName > at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87) > at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:70) > at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:321) > at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:317) > at org.slf4j.impl.Slf4jLogger.info(Slf4jLogger.java:186) > at > org.apache.activemq.hawtio.branding.PluginContextListener.contextInitialized(PluginContextListener.java:53) > at > org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:876) > at > org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:532) > at > org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:839) > at > org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:344) > at > org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1480) > at > org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1442) > at > org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:799) > at > org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261) > at > org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113) > at > org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) > at org.eclipse.jetty.server.Server.start(Server.java:452) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105) > at > org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) > at org.eclipse.jetty.server.Server.doStart(Server.java:419) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) > at > org.apache.activemq.artemis.component.WebServerComponent.start(WebServerComponent.java:229) > at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:105) > at > org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:150) > at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:98) > at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:125) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129) > at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49) > Exception in thread "Thread-1 (ActiveMQ-client-netty-threads)" > java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName > at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87) > at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:70) > at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:321) > at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:67) > at > io.netty.util.internal.logging.LocationAwareSlf4JLogger.log(LocationAwareSlf4JLogger.java:46) > at >
[jira] [Commented] (ARTEMIS-2419) java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName during startup
[ https://issues.apache.org/jira/browse/ARTEMIS-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880351#comment-16880351 ] Justin Bertram commented on ARTEMIS-2419: - Did you upgrade an existing instance from a previous version (e.g. 2.8.0) to 2.9.0? If so, did you follow the upgrade instructions in [the documentation|http://activemq.apache.org/components/artemis/documentation/latest/versions.html]? > java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName during startup > -- > > Key: ARTEMIS-2419 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2419 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.9.0 >Reporter: Keith Wall >Priority: Major > > Testing with Apache Artemis 2.9.0 I am encountering the following exception > during start-up. The issue is being thrown from a test site and I have not > yet identified what exactly triggers this problem. > Apache ActiveMQ Artemis 2.9.0 > java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName > at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87) > at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:70) > at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:321) > at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:317) > at org.slf4j.impl.Slf4jLogger.info(Slf4jLogger.java:186) > at > org.apache.activemq.hawtio.branding.PluginContextListener.contextInitialized(PluginContextListener.java:53) > at > org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:876) > at > org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:532) > at > org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:839) > at > org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:344) > at > org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1480) > at > org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1442) > at > org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:799) > at > org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261) > at > org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113) > at > org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) > at org.eclipse.jetty.server.Server.start(Server.java:452) > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105) > at > org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) > at org.eclipse.jetty.server.Server.doStart(Server.java:419) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) > at > org.apache.activemq.artemis.component.WebServerComponent.start(WebServerComponent.java:229) > at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:105) > at > org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:150) > at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:98) > at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:125) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129) > at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49) > Exception in thread "Thread-1 (ActiveMQ-client-netty-threads)" > java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName > at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87) > at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:70) > at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:321) > at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:67) > at >
[jira] [Created] (ARTEMIS-2419) java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName during startup
Keith Wall created ARTEMIS-2419: --- Summary: java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName during startup Key: ARTEMIS-2419 URL: https://issues.apache.org/jira/browse/ARTEMIS-2419 Project: ActiveMQ Artemis Issue Type: Bug Affects Versions: 2.9.0 Reporter: Keith Wall Testing with Apache Artemis 2.9.0 I am encountering the following exception during start-up. The issue is being thrown from a test site and I have not yet identified what exactly triggers this problem. Apache ActiveMQ Artemis 2.9.0 java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87) at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:70) at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:321) at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:317) at org.slf4j.impl.Slf4jLogger.info(Slf4jLogger.java:186) at org.apache.activemq.hawtio.branding.PluginContextListener.contextInitialized(PluginContextListener.java:53) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:876) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:532) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:839) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:344) at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1480) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1442) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:799) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:540) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) at org.eclipse.jetty.server.Server.start(Server.java:452) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.Server.doStart(Server.java:419) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.apache.activemq.artemis.component.WebServerComponent.start(WebServerComponent.java:229) at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:105) at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:150) at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:98) at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:125) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129) at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49) Exception in thread "Thread-1 (ActiveMQ-client-netty-threads)" java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87) at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:70) at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:321) at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:67) at io.netty.util.internal.logging.LocationAwareSlf4JLogger.log(LocationAwareSlf4JLogger.java:46) at io.netty.util.internal.logging.LocationAwareSlf4JLogger.warn(LocationAwareSlf4JLogger.java:209) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:908) at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) Exception in thread "Thread-0 (ActiveMQ-client-netty-threads)" java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName at
[jira] [Resolved] (AMQ-7238) Demand Bridge does not always clean up subscription properly out of remoteId map
[ https://issues.apache.org/jira/browse/AMQ-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved AMQ-7238. - Resolution: Fixed > Demand Bridge does not always clean up subscription properly out of remoteId > map > > > Key: AMQ-7238 > URL: https://issues.apache.org/jira/browse/AMQ-7238 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.15.9 >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Minor > Fix For: 5.16.0, 5.15.10 > > > In the DemandForwardingBridgeSupport class there are two maps to track > DemandSubscriptions (tracked by both local and remote consumer Ids). There > are a couple of cases where the subscription gets cleared from the local map > when demand goes away but the remote map is not cleared leading to a memory > leak. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7238) Demand Bridge does not always clean up subscription properly out of remoteId map
[ https://issues.apache.org/jira/browse/AMQ-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880276#comment-16880276 ] ASF subversion and git services commented on AMQ-7238: -- Commit 8a11ab4a1b59693e498f16e629f7e21191445e6f in activemq's branch refs/heads/activemq-5.15.x from Christopher L. Shannon (cshannon) [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=8a11ab4 ] AMQ-7238 - Ensure remoteId subscription map is also cleared when local map is cleared inside DemandForwardingBridgeSupport (cherry picked from commit c7eff840588be718da9a985d5c2b8db89b26796d) > Demand Bridge does not always clean up subscription properly out of remoteId > map > > > Key: AMQ-7238 > URL: https://issues.apache.org/jira/browse/AMQ-7238 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.15.9 >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Minor > Fix For: 5.16.0, 5.15.10 > > > In the DemandForwardingBridgeSupport class there are two maps to track > DemandSubscriptions (tracked by both local and remote consumer Ids). There > are a couple of cases where the subscription gets cleared from the local map > when demand goes away but the remote map is not cleared leading to a memory > leak. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7238) Demand Bridge does not always clean up subscription properly out of remoteId map
[ https://issues.apache.org/jira/browse/AMQ-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880275#comment-16880275 ] ASF subversion and git services commented on AMQ-7238: -- Commit c7eff840588be718da9a985d5c2b8db89b26796d in activemq's branch refs/heads/master from Christopher L. Shannon (cshannon) [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=c7eff84 ] AMQ-7238 - Ensure remoteId subscription map is also cleared when local map is cleared inside DemandForwardingBridgeSupport > Demand Bridge does not always clean up subscription properly out of remoteId > map > > > Key: AMQ-7238 > URL: https://issues.apache.org/jira/browse/AMQ-7238 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.15.9 >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Minor > Fix For: 5.16.0, 5.15.10 > > > In the DemandForwardingBridgeSupport class there are two maps to track > DemandSubscriptions (tracked by both local and remote consumer Ids). There > are a couple of cases where the subscription gets cleared from the local map > when demand goes away but the remote map is not cleared leading to a memory > leak. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQ-7238) Demand Bridge does not always clean up subscription properly out of remoteId map
Christopher L. Shannon created AMQ-7238: --- Summary: Demand Bridge does not always clean up subscription properly out of remoteId map Key: AMQ-7238 URL: https://issues.apache.org/jira/browse/AMQ-7238 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.15.9 Reporter: Christopher L. Shannon Assignee: Christopher L. Shannon Fix For: 5.16.0, 5.15.10 In the DemandForwardingBridgeSupport class there are two maps to track DemandSubscriptions (tracked by both local and remote consumer Ids). There are a couple of cases where the subscription gets cleared from the local map when demand goes away but the remote map is not cleared leading to a memory leak. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (ARTEMIS-2418) Race conditions between cursor movement and page writing
[ https://issues.apache.org/jira/browse/ARTEMIS-2418?focusedWorklogId=273223=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-273223 ] ASF GitHub Bot logged work on ARTEMIS-2418: --- Author: ASF GitHub Bot Created on: 08/Jul/19 11:13 Start Date: 08/Jul/19 11:13 Worklog Time Spent: 10m Work Description: wy96f commented on pull request #2743: ARTEMIS-2418 Race conditions between cursor movement and page writing URL: https://github.com/apache/activemq-artemis/pull/2743 The current code of CursorIterator::internalGetNext is a little complicated and not easy to follow logically. And there are two race conditions between cursor movement and page writing: 1. Suppose the cursor's initial position is (p1,0) and page p1 is live with 0 msg. When we call internalGetNext(), the cursor moves to next page, i.e. position is (p2, 0) now. Meanwhile p1 is filled with message m1 and p2 is created with m2. Then we retrieve m2 from p2 rather than m1. 2. Suppose the cursor's initial position is (p1, 1) and the page p1 is non live with 1 msg. When we call internalGetNext(), the cursor moves to position(p2, 0) and get null page cache since p2 is not yet created. Then p2 is created with m1 and p3 is created with m2 which means current writing page no. is p3. After the while loop the cursor moves to position(p3, 0) and we retrieve m2 from p3 rather than m1. In both cases we would miss message m1 and subsequent page files won't be deleted unless the broker restarts. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 273223) Time Spent: 10m Remaining Estimate: 0h > Race conditions between cursor movement and page writing > > > Key: ARTEMIS-2418 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2418 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.9.0 >Reporter: yangwei >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The current code of CursorIterator::internalGetNext is a little complicated > and not easy to follow logically. > And there are two race conditions between cursor movement and page writing: > 1. Suppose the cursor's initial position is (p1,0) and page p1 is live with 0 > msg. When we call internalGetNext(), the cursor moves to next page, i.e. > position is (p2, 0) now. Meanwhile p1 is filled with message m1 and p2 is > created with m2. Then we retrieve m2 from p2 rather than m1. > 2. Suppose the cursor's initial position is (p1, 1) and the page p1 is non > live with 1 msg. When we call internalGetNext(), the cursor moves to > position(p2, 0) and get null page cache since p2 is not yet created. Then p2 > is created with m1 and p3 is created with m2 which means current writing page > no. is p3. After the while loop the cursor moves to position(p3, 0) and we > retrieve m2 from p3 rather than m1. > In both cases we would miss message m1 and subsequent page files won't be > deleted unless the broker restarts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARTEMIS-2418) Race conditions between cursor movement and page writing
yangwei created ARTEMIS-2418: Summary: Race conditions between cursor movement and page writing Key: ARTEMIS-2418 URL: https://issues.apache.org/jira/browse/ARTEMIS-2418 Project: ActiveMQ Artemis Issue Type: Bug Components: Broker Affects Versions: 2.9.0 Reporter: yangwei The current code of CursorIterator::internalGetNext is a little complicated and not easy to follow logically. And there are two race conditions between cursor movement and page writing: 1. Suppose the cursor's initial position is (p1,0) and page p1 is live with 0 msg. When we call internalGetNext(), the cursor moves to next page, i.e. position is (p2, 0) now. Meanwhile p1 is filled with message m1 and p2 is created with m2. Then we retrieve m2 from p2 rather than m1. 2. Suppose the cursor's initial position is (p1, 1) and the page p1 is non live with 1 msg. When we call internalGetNext(), the cursor moves to position(p2, 0) and get null page cache since p2 is not yet created. Then p2 is created with m1 and p3 is created with m2 which means current writing page no. is p3. After the while loop the cursor moves to position(p3, 0) and we retrieve m2 from p3 rather than m1. In both cases we would miss message m1 and subsequent page files won't be deleted unless the broker restarts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7234) Topic flow control with messages in a transaction can loop forever waiting for usage
[ https://issues.apache.org/jira/browse/AMQ-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880194#comment-16880194 ] ASF subversion and git services commented on AMQ-7234: -- Commit ede4dbc8649792628b1135db9cdf9b06fd6844df in activemq's branch refs/heads/activemq-5.15.x from gtully [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=ede4dbc ] AMQ-7234 - fix up memory usage wait timeout such that topic pfc in a transaction can see connection context state changes, fix and test (cherry picked from commit de3f77063fa579159184d23ac98df97e80d63327) > Topic flow control with messages in a transaction can loop forever waiting > for usage > > > Key: AMQ-7234 > URL: https://issues.apache.org/jira/browse/AMQ-7234 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 5.16.0 > > > The memory usage wait(timeout > 0) does not respect the timeout. Topic pfc > loops on that wait to check the connection context, but it never gets to > check the status and stays hung even when jmx is used to kill the connection. > If the topic producer uses alwaysSendSync it avoids this code path and can be > closes via JMX and the rollback will release resources as expected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7234) Topic flow control with messages in a transaction can loop forever waiting for usage
[ https://issues.apache.org/jira/browse/AMQ-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-7234: Fix Version/s: 5.15.10 > Topic flow control with messages in a transaction can loop forever waiting > for usage > > > Key: AMQ-7234 > URL: https://issues.apache.org/jira/browse/AMQ-7234 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 5.16.0, 5.15.10 > > > The memory usage wait(timeout > 0) does not respect the timeout. Topic pfc > loops on that wait to check the connection context, but it never gets to > check the status and stays hung even when jmx is used to kill the connection. > If the topic producer uses alwaysSendSync it avoids this code path and can be > closes via JMX and the rollback will release resources as expected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (ARTEMIS-2409) HornetQ client vs Artemis broker compatibility: issue while using JMSMessageID as selector
[
https://issues.apache.org/jira/browse/ARTEMIS-2409?focusedWorklogId=273180=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-273180
]
ASF GitHub Bot logged work on ARTEMIS-2409:
---
Author: ASF GitHub Bot
Created on: 08/Jul/19 09:28
Start Date: 08/Jul/19 09:28
Worklog Time Spent: 10m
Work Description: TomasHofman commented on pull request #2742:
ARTEMIS-2409 Convert HornetQ field names in consumer/queue selector s…
URL: https://github.com/apache/activemq-artemis/pull/2742
…trings
https://issues.apache.org/jira/browse/ARTEMIS-2409
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 273180)
Time Spent: 10m
Remaining Estimate: 0h
> HornetQ client vs Artemis broker compatibility: issue while using
> JMSMessageID as selector
> --
>
> Key: ARTEMIS-2409
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2409
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.9.0
>Reporter: Tomas Hofman
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When Hornetq client connects to Artemis broker, and creates consumer with
> selector containing e.g. {{JMSMessageID}} field, selector fails to correctly
> match messages.
> When using JMSMessageID as a selector, HornetQ client converts the header to
> {{HQUserID}}, while Artemis is expecting header {{AMQUserID}}.
> The broker should detect a legacy HornetQ client and adjust the incoming
> selector.
> {code}
> String selector = "JMSMessageID = 'ID:06df8801-9719-11e9-9313-972d6542d784'";
> // message with above ID exists in the queue
> org.hornetq.api.core.client.ClientConsumer hqConsumer =
> hqSession.createConsumer(queueName, selector, true);
> org.hornetq.api.core.client.ClientMessage message = hqConsumer.receive(1000);
> assertNotNull(message); // fails
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (ARTEMIS-2411) Keys and values must be >= 0
[
https://issues.apache.org/jira/browse/ARTEMIS-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880083#comment-16880083
]
Bhavesh Kharwa edited comment on ARTEMIS-2411 at 7/8/19 7:26 AM:
-
Artemis journal directory cleanup not happen (ARTEMIS-2416 ), so I have
executed above command.
was (Author: bhavesh.kharwa):
Artemis journal directory cleanup not happen (ARTEMIS-2416 ), I have executed
above command.
> Keys and values must be >= 0
>
>
> Key: ARTEMIS-2411
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2411
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Bhavesh Kharwa
>Priority: Major
>
> Got following error while executing compact command
> *Command*
> {noformat}
> artemis data compact{noformat}
>
> *Error:*
> {noformat}
> 2019-07-04 07:33:27,255 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,035 found and discarded
> 2019-07-04 07:33:27,261 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,059 found and discarded
> 2019-07-04 07:33:27,261 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,133 found and discarded
> 2019-07-04 07:33:27,262 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,512 found and discarded
> 2019-07-04 07:33:27,263 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,515 found and discarded
> 2019-07-04 07:33:27,263 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,535 found and discarded
> 2019-07-04 07:33:27,264 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,576 found and discarded
> 2019-07-04 07:33:27,264 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,582 found and discarded
> 2019-07-04 07:33:27,264 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,598 found and discarded
> 2019-07-04 07:33:27,264 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,617 found and discarded
> Error:Keys and values must be >= 0
> java.lang.IllegalArgumentException: Keys and values must be >= 0
>at
> org.apache.activemq.artemis.utils.collections.ConcurrentLongHashSet.checkBiggerEqualZero(ConcurrentLongHashSet.java:428)
>at
> org.apache.activemq.artemis.utils.collections.ConcurrentLongHashSet.add(ConcurrentLongHashSet.java:125)
>at
> org.apache.activemq.artemis.utils.collections.ConcurrentLongHashMap.lambda$keysLongHashSet$1(ConcurrentLongHashMap.java:187)
>at
> org.apache.activemq.artemis.utils.collections.ConcurrentLongHashMap$Section.forEach(ConcurrentLongHashMap.java:442)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARTEMIS-2411) Keys and values must be >= 0
[
https://issues.apache.org/jira/browse/ARTEMIS-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880083#comment-16880083
]
Bhavesh Kharwa commented on ARTEMIS-2411:
-
Artemis journal directory cleanup not happen (ARTEMIS-2416 ), I have executed
above command.
> Keys and values must be >= 0
>
>
> Key: ARTEMIS-2411
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2411
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Bhavesh Kharwa
>Priority: Major
>
> Got following error while executing compact command
> *Command*
> {noformat}
> artemis data compact{noformat}
>
> *Error:*
> {noformat}
> 2019-07-04 07:33:27,255 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,035 found and discarded
> 2019-07-04 07:33:27,261 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,059 found and discarded
> 2019-07-04 07:33:27,261 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,133 found and discarded
> 2019-07-04 07:33:27,262 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,512 found and discarded
> 2019-07-04 07:33:27,263 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,515 found and discarded
> 2019-07-04 07:33:27,263 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,535 found and discarded
> 2019-07-04 07:33:27,264 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,576 found and discarded
> 2019-07-04 07:33:27,264 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,582 found and discarded
> 2019-07-04 07:33:27,264 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,598 found and discarded
> 2019-07-04 07:33:27,264 WARN [org.apache.activemq.artemis.journal]
> AMQ142015: Uncommitted transaction with id 145,280,617 found and discarded
> Error:Keys and values must be >= 0
> java.lang.IllegalArgumentException: Keys and values must be >= 0
>at
> org.apache.activemq.artemis.utils.collections.ConcurrentLongHashSet.checkBiggerEqualZero(ConcurrentLongHashSet.java:428)
>at
> org.apache.activemq.artemis.utils.collections.ConcurrentLongHashSet.add(ConcurrentLongHashSet.java:125)
>at
> org.apache.activemq.artemis.utils.collections.ConcurrentLongHashMap.lambda$keysLongHashSet$1(ConcurrentLongHashMap.java:187)
>at
> org.apache.activemq.artemis.utils.collections.ConcurrentLongHashMap$Section.forEach(ConcurrentLongHashMap.java:442)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
