[jira] [Closed] (ARTEMIS-1805) Some broker operations in hawtio causes error
[ https://issues.apache.org/jira/browse/ARTEMIS-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1805. Resolution: Fixed > Some broker operations in hawtio causes error > - > > Key: ARTEMIS-1805 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1805 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Stanislav Knot >Assignee: Stanislav Knot >Priority: Minor > Fix For: 2.6.0 > > > updateQueue, sendQueueInfoToQueue and updateDuplicateIdCache operations cause > an error if selected in hawtio console. Adding @Operation annotation fixes > error, but methods are exposed and I am not 100% sure it is correct. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1801) Remove dereferences before null check
[ https://issues.apache.org/jira/browse/ARTEMIS-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1801. Resolution: Fixed > Remove dereferences before null check > - > > Key: ARTEMIS-1801 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1801 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Stanislav Knot >Assignee: Stanislav Knot >Priority: Minor > Fix For: 2.6.0 > > > There are some dereferences before object is checked for null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1813) DB2 should avoid Blob to append data
[ https://issues.apache.org/jira/browse/ARTEMIS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1813. Resolution: Fixed Fix Version/s: 2.6.0 > DB2 should avoid Blob to append data > > > Key: ARTEMIS-1813 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1813 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1815) add "exclusive-queue" example
[ https://issues.apache.org/jira/browse/ARTEMIS-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1815. Resolution: Fixed > add "exclusive-queue" example > -- > > Key: ARTEMIS-1815 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1815 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Pat Fox >Priority: Minor > Fix For: 2.6.0 > > > add "exclusive-queue" example to the examples dir. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-618) Fails to initialize journal if hard drive block size is over 512 bytes
[ https://issues.apache.org/jira/browse/ARTEMIS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-618. --- Resolution: Fixed > Fails to initialize journal if hard drive block size is over 512 bytes > -- > > Key: ARTEMIS-618 > URL: https://issues.apache.org/jira/browse/ARTEMIS-618 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 > Environment: CentOS 7 on hard drive with 4 KB blocks >Reporter: Rostyslav Smirnov >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > AIO journal fails to initialize with the following error: > AMQ224000: Failure in initialisation: java.io.IOException: Cannot initialize > file > at org.apache.activemq.artemis.jlibaio.LibaioContext.fill(Native > Method) [artemis-native-1.3.0.jar:] > at > org.apache.activemq.artemis.jlibaio.LibaioFile.fill(LibaioFile.java:122) > [artemis-native-1.3.0.jar:] > at > org.apache.activemq.artemis.core.io.aio.AIOSequentialFile.fill(AIOSequentialFile.java:126) > [artemis-journal-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile0(JournalFilesRepository.java:587) > [artemis-journal-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.createFile(JournalFilesRepository.java:537) > [artemis-journal-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.journal.impl.JournalFilesRepository.ensureMinFiles(JournalFilesRepository.java:201) > [artemis-journal-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.journal.impl.JournalImpl.setUpCurrentFile(JournalImpl.java:2709) > [artemis-journal-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1755) > [artemis-journal-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1135) > [artemis-journal-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.journal.impl.JournalImpl.load(JournalImpl.java:1119) > [artemis-journal-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:864) > [artemis-server-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2054) > [artemis-server-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1927) > [artemis-server-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:63) > [artemis-server-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:427) > [artemis-server-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:394) > [artemis-jms-server-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:65) > [artemis-cli-1.3.0.jar:1.3.0] > at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:83) > [artemis-cli-1.3.0.jar:1.3.0] > at > org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:110) > [artemis-cli-1.3.0.jar:1.3.0] > at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:72) > [artemis-cli-1.3.0.jar:1.3.0] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [rt.jar:1.8.0_65] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [rt.jar:1.8.0_65] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [rt.jar:1.8.0_65] > at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65] > at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:122) > [artemis-boot.jar:1.3.0] > at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:45) > [artemis-boot.jar:1.3.0] > This is due to buffers not being aligned for writing to file open with > O_DIRECT flag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1701) Zone ID not stripped properly from IPv6 addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1701. Resolution: Fixed > Zone ID not stripped properly from IPv6 addresses > - > > Key: ARTEMIS-1701 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1701 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.4.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-370) Make JDBC Journal Sync period configurable
[ https://issues.apache.org/jira/browse/ARTEMIS-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-370. --- Resolution: Fixed > Make JDBC Journal Sync period configurable > -- > > Key: ARTEMIS-370 > URL: https://issues.apache.org/jira/browse/ARTEMIS-370 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Martyn Taylor >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-857) JMX+API support for viewing and manually clearing message group caches
[ https://issues.apache.org/jira/browse/ARTEMIS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-857. --- Resolution: Fixed > JMX+API support for viewing and manually clearing message group caches > -- > > Key: ARTEMIS-857 > URL: https://issues.apache.org/jira/browse/ARTEMIS-857 > Project: ActiveMQ Artemis > Issue Type: Sub-task > Components: Broker >Reporter: Matt Pavlovich >Priority: Major > Fix For: 2.6.0 > > > Need an API to support for viewing message group infomration and optionally > flushing group-id maps that are not cleared by mis-behaving clients. > ie.. client never sends the JMSXSeqID -1 message -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1781) Broken backward compatibility with HornetQ
[
https://issues.apache.org/jira/browse/ARTEMIS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1781.
Resolution: Fixed
> Broken backward compatibility with HornetQ
> --
>
> Key: ARTEMIS-1781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1781
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.5.5, 2.5.0
>Reporter: Tomas Hofman
>Priority: Major
> Fix For: 2.6.0
>
>
> When connector is configured to use SSL encryption, HornetQ client receives
> invalid parameter keys - camelCase instead of dash-separated.
> {code:java}
> 2018-01-23 17:39:32,769 logLev=WARN class=org.hornetq.jms.server
> thread="Periodic Recovery" HQ122015: Can not connect to XARecoveryConfig
> [transportConfiguration = [TransportConfiguration(name=hornetq-ssl-connector,
> factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory)
> ?trustStorePassword=123456=123456=5500=true=ld9c02ad-umobi-mobicorp-test=/data/jboss/server/mobi/configuration/keys/jspStore_dev-jks=/data/jboss/server/mobi/configuration/keys/mobiJspDynWesTrust_dev-jks],
> discoveryConfiguration = null, username=Z100283, password=] on
> auto-generated resource recovery: java.lang.IllegalStateException: The
> following keys are invalid for configuring a connector: trustStorePassword,
> keyStorePassword, sslEnabled, trustStorePath, keyStorePath
> at
> org.hornetq.core.client.impl.ClientSessionFactoryImpl.checkTransportKeys(ClientSessionFactoryImpl.java:1542)
> at
> org.hornetq.core.client.impl.ClientSessionFactoryImpl.(ClientSessionFactoryImpl.java:212)
> at
> org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:872)
> at
> org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.connect(HornetQXAResourceWrapper.java:377)
> at
> org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.getDelegate(HornetQXAResourceWrapper.java:286)
> at
> org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.recover(HornetQXAResourceWrapper.java:74)
> at
> com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:541)
> at
> com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:181)
> at
> com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747)
> at
> com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375)
> {code}
> Original issue: https://issues.jboss.org/browse/ENTMQBR-1034
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1286) Server stops responding and throws OutOfDirectMemoryError when sending & receiving lots of 2MB MQTT messages.
[
https://issues.apache.org/jira/browse/ARTEMIS-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1286.
Resolution: Fixed
> Server stops responding and throws OutOfDirectMemoryError when sending &
> receiving lots of 2MB MQTT messages.
> -
>
> Key: ARTEMIS-1286
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1286
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker, MQTT
>Affects Versions: 2.1.0
>Reporter: Phillip Jenkins
>Assignee: clebert suconic
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: MQTTBasicPubSubExample2.zip, artemis log showing v2.4
> still having trouble handling large messages.log, broker.xml,
> image-2018-02-24-19-54-00-892.png, mqtt.zip
>
>
> Originally seen in v2.1 and present in v2.2.
> If you send and receive a lot of 2MB messages in short time thru Artemis via
> Netty connector, the server throws the following OutOfDirectMemoryError
> exception. The server stops responding and will not (any longer) accept
> connections without throwing exceptions in an infinite loop.
> {code:java}
> 11:24:07,434 INFO [org.apache.activemq.artemis] AMQ241001: HTTP Server
> started at http://localhost:8161
> 11:24:07,434 INFO [org.apache.activemq.artemis] AMQ241002: Artemis Jolokia
> REST API available at http://localhost:8161/jolokia
> 11:58:35,991 WARN [org.apache.activemq.artemis.core.server] AMQ222151:
> removing consumer which did not handle a message, consumer=ServerConsumerImpl
> [id=2229, filter=null, binding=LocalQueueBinding
> [address=SOAP.S.PRN.ACBCAF6238234680,
> queue=QueueImpl[name=ACBCAF6238234680.SOAP.S.PRN.ACBCAF6238234680,
> postOffice=PostOfficeImpl
> [server=ActiveMQServerImpl::serverUUID=afa7de73-67e7-11e7-a231-54ee7505882d],
> temp=false]@46adc2a5, filter=FilterImpl [sfilterString=NOT ((AMQAddress =
> 'activemq.management') OR (AMQAddress = 'activemq.notifications'))],
> name=ACBCAF6238234680.SOAP.S.PRN.ACBCAF6238234680,
> clusterName=ACBCAF6238234680.SOAP.S.PRN.ACBCAF6238234680afa7de73-67e7-11e7-a231-54ee7505882d]],
>
> message=Reference[3551]:NON-RELIABLE:CoreMessage[messageID=3551,durable=false,userID=null,priority=0,
> timestamp=0,expiration=0, durable=false,
> address=SOAP.S.PRN.ACBCAF6238234680,properties=TypedProperties[mqtt.message.retain=false,mqtt.qos.level=0]]@1305748199:
> io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 3729415
> byte(s) of direct memory (used: 1070952692, max: 1073741824)
> at
> io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:585)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:539)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.allocateDirect(UnpooledUnsafeNoCleanerDirectByteBuf.java:30)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> io.netty.buffer.UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeNoCleanerDirectByteBuf.allocateDirect(UnpooledByteBufAllocator.java:169)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> io.netty.buffer.UnpooledUnsafeDirectByteBuf.(UnpooledUnsafeDirectByteBuf.java:68)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.(UnpooledUnsafeNoCleanerDirectByteBuf.java:25)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> io.netty.buffer.UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeNoCleanerDirectByteBuf.(UnpooledByteBufAllocator.java:164)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> io.netty.buffer.UnpooledByteBufAllocator.newDirectBuffer(UnpooledByteBufAllocator.java:73)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:181)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> io.netty.buffer.AbstractByteBufAllocator.buffer(AbstractByteBufAllocator.java:117)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:828)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.buffer.WrappedByteBuf.readBytes(WrappedByteBuf.java:616)
> [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at
> org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readBytes(ChannelBufferWrapper.java:315)
> [artemis-commons-2.2.0-SNAPSHOT.jar:2.2.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.protocol.mqtt.MQTTPublishManager.sendServerMessage(MQTTPublishManager.java:277)
> [artemis-mqtt-protocol-2.2.0-SNAPSHOT.jar:]
> at
>
[jira] [Closed] (ARTEMIS-1798) DEBUG message bad write method arg count: public void org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.setUpInactivityParams
[
https://issues.apache.org/jira/browse/ARTEMIS-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1798.
Resolution: Fixed
Fix Version/s: 2.6.0
> DEBUG message bad write method arg count: public void
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.setUpInactivityParams
> --
>
> Key: ARTEMIS-1798
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1798
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Trivial
> Fix For: 2.6.0
>
>
> {noformat}
> 16:06:31,002 DEBUG
> [org.apache.activemq.artemis.utils.uri.FluentPropertyBeanIntrospectorWithIgnores]
> bad write method arg count: public void
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.setUpInactivityParams(org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection,org.apache.activemq.command.WireFormatInfo)
> throws java.io.IOException: java.beans.IntrospectionException: bad write
> method arg count: public void
> org.apache.activemq.artemis.core.protocol.openwire.OpenWireProtocolManager.setUpInactivityParams(org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection,org.
> {noformat}
> setUpInactivityParams does not set any property, which causes this error
> message when debug logging is enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1758) Support SASL EXTERNAL
[ https://issues.apache.org/jira/browse/ARTEMIS-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1758. Resolution: Fixed > Support SASL EXTERNAL > - > > Key: ARTEMIS-1758 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1758 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP >Affects Versions: 2.5.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.6.0 > > > Add support for SASL EXTERNAL > https://tools.ietf.org/html/rfc4422#appendix-A > Peer principal from TLS client cert is used as the client identity on the > broker. > The identity is mapped to a broker user and role via the > TextFileCertificateLoginModule -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1753) When using the 1.5.5 Artemis JMS Client, NPE is thrown when creating a durable subscription
[ https://issues.apache.org/jira/browse/ARTEMIS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1753. Resolution: Fixed > When using the 1.5.5 Artemis JMS Client, NPE is thrown when creating a > durable subscription > --- > > Key: ARTEMIS-1753 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1753 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Martyn Taylor >Priority: Major > Fix For: 2.6.0 > > > When creating a durable topic subcription using the Artemis 1.5.5 client a > QueueQuery is performed to see if the subscription already exists. There is > some code that converts the queue names to the old 1.x scheme. However, if > the subscription does not already exist, the conversion is attempted on a > null string, causing an NPE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1822) Inconsistent method name
[
https://issues.apache.org/jira/browse/ARTEMIS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1822.
Resolution: Fixed
> Inconsistent method name
>
>
> Key: ARTEMIS-1822
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1822
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: Broker
>Reporter: KuiLIU
>Priority: Trivial
> Fix For: 2.6.0
>
>
> The following method is named "lookupRecord".
> "lookupRecord" seems to find a related record.
> But the method is checking whether recordsSnapshot contains the id or not.
> Thus, the method name "containsRecord" is more intuitive than "lookupRecord".
> {code:java}
>public boolean lookupRecord(final long id) {
> return recordsSnapshot.contains(id);
>}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1740) Add support for regex based certificate authentication
[
https://issues.apache.org/jira/browse/ARTEMIS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1740.
> Add support for regex based certificate authentication
> --
>
> Key: ARTEMIS-1740
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1740
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Lionel Cons
>Priority: Major
> Fix For: 2.6.0
>
>
> The current certificate authentication module
> ({{TextFileCertificateLoginModule}}) uses a file mapping user names to DNs.
> In some cases, the list of known DNs can be large and dynamic. This is the
> case for instance when using host certificates.
> Host certificates could be very dynamic (when new virtual machines get
> created) while keeping a fixed structure such as {{CN=hostxyz.acme.org,
> OU=computers, DC=acme, DC=org}}. It is impractical to generate all the
> possible DNs and feed this to Artemis.
> It would be very useful to have regular expression based certificate
> authentication. With the example above, we could have a single line:
> {quote}
> acme.computers=/^CN=\w+\.acme\.org, OU=computers, DC=acme, DC=org$/
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1761) Log one warning if cluster could not be formed because it's not possible to connect to other cluster node
[
https://issues.apache.org/jira/browse/ARTEMIS-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1761.
Resolution: Fixed
> Log one warning if cluster could not be formed because it's not possible to
> connect to other cluster node
> -
>
> Key: ARTEMIS-1761
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1761
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
> Fix For: 2.6.0
>
>
> If discovery-group receives connector which is not possible to use to create
> cluster connection (using such connector fails) then server should log one
> warning. Currently server is logging this on DEBUG level which is confusing
> and it's not clear why cluster was not formed. It's just silently retrying
> bad connector on background (on debug level).
> Current debug logs:
> {code}
> 14:43:45,777 DEBUG
> [org.apache.activemq.artemis.core.server.cluster.impl.BridgeImpl] (Thread-4
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3@3f47a5c5))
> Bridge ClusterConnecti
> onBridge@516796ab [name=sf.my-cluster.6eca14fb-4535-11e7-bc50-3ca9f4349bfc,
> queue=QueueImpl[name=sf.my-cluster.6eca14fb-4535-11e7-bc50-3ca9f4349bfc,
> postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUU
> ID=5630528e-4535-11e7-9213-3c970e9648c8]]@2d035848
> targetConnector=ServerLocatorImpl
> (identity=(Cluster-connection-bridge::ClusterConnectionBridge@516796ab
> [name=sf.my-cluster.6eca14fb-4535-11e7-bc50-3ca9f4349bf
> c, queue=QueueImpl[name=sf.my-cluster.6eca14fb-4535-11e7-bc50-3ca9f4349bfc,
> postOffice=PostOfficeImpl
> [server=ActiveMQServerImpl::serverUUID=5630528e-4535-11e7-9213-3c970e9648c8]]@2d035848
> targetConnector=Server
> LocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector,
> factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?httpUpgradeEndpoint=https-acceptor
> ame=default=true=9080=localhost],
> discoveryGroupConfiguration=null]]::ClusterConnectionImpl@386706758[nodeUUID=5630528e-4535-11e7-9213-3c970e9648c8,
> connector=TransportConfiguration(
> name=http-connector,
> factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
>
> ?httpUpgradeEndpoint=https-acceptor=default=true=8080=loca
> lhost, address=jms,
> server=ActiveMQServerImpl::serverUUID=5630528e-4535-11e7-9213-3c970e9648c8]))
> [initialConnectors=[TransportConfiguration(name=http-connector,
> factory=org-apache-activemq-artemis-core-remoting
> -impl-netty-NettyConnectorFactory)
> ?httpUpgradeEndpoint=https-acceptor=default=true=9080=localhost],
> discoveryGroupConfiguration=null]] is unable to connect to des
> tination. Retrying: ActiveMQNotConnectedException[errorType=NOT_CONNECTED
> message=Unable to connect to server using configuration
> TransportConfiguration(name=http-connector,
> factory=org-apache-activemq-artemis-c
> ore-remoting-impl-netty-NettyConnectorFactory)
> ?httpUpgradeEndpoint=https-acceptor=default=true=9080=localhost]
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:245)
> [artemis-core-client-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
> at
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:685)
> [artemis-core-client-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
> at
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:659)
> [artemis-core-client-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
> at
> org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge.createSessionFactory(ClusterConnectionBridge.java:136)
> [artemis-server-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
> at
> org.apache.activemq.artemis.core.server.cluster.impl.BridgeImpl.connect(BridgeImpl.java:857)
> [artemis-server-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
> at
> org.apache.activemq.artemis.core.server.cluster.impl.BridgeImpl$ConnectRunnable.run(BridgeImpl.java:1048)
> [artemis-server-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
> at
> org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:101)
> [artemis-commons-1.5.5.001-redhat-1.jar:1.5.5.001-redhat-1]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [rt.jar:1.8.0_71]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [rt.jar:1.8.0_71]
> at java.lang.Thread.run(Thread.java:745)
[jira] [Closed] (ARTEMIS-1834) Incorrect STOMP destination header
[
https://issues.apache.org/jira/browse/ARTEMIS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1834.
Resolution: Fixed
> Incorrect STOMP destination header
> --
>
> Key: ARTEMIS-1834
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1834
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: STOMP
>Reporter: Lionel Cons
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.6.0
>
>
> In the most recent snapshot (2.6.0-20180427.020303-62) the STOMP
> {{destination}} header is now modified by Artemis.
> I'm using {{anycastPrefix=/queue/}} and {{multicastPrefix=/topic/}} to match
> ActiveMQ 5's STOMP behavior.
> When sending a message to {{/topic/foo}}, the sent STOMP frame contains
> {{destination:/topic/foo}} in its header, as expected.
> However, the received STOMP frame now contains {{destination:foo}} in its
> header. It was {{destination:/topic/foo}} in previous Artemis versions.
> IMHO, the STOMP {{destination}} header should be left untouched.
> {{anycastPrefix}} and {{multicastPrefix}} should only be used to guess the
> destination type and not to change the destination string itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1746) Client-side openSSH support is broken
[ https://issues.apache.org/jira/browse/ARTEMIS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1746. Resolution: Fixed Fix Version/s: 2.6.0 > Client-side openSSH support is broken > - > > Key: ARTEMIS-1746 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1746 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Christian Sailer >Priority: Major > Fix For: 2.6.0 > > > The new feature to use openSSH via the netty-tcnative library in Artemis > 2.5.0 only works for enabling on the server side. > When enabling it on the client side, there are several issue, the first of > which is that it tries to use a server ssl context on the client side and > then fails due to a client/server mismatch. > Also, I could not find any integration tests actually using openSSL. > I am working on a patch to fix these issues including tests. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1653) Allow database tables to be created externally
[ https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1653. Resolution: Fixed > Allow database tables to be created externally > -- > > Key: ARTEMIS-1653 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1653 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.4.0 >Reporter: Niels Lippke >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > > In some environments (e.g. production) it is not allowed that applications > create their own schema. It's common practice to pass DDL-Statetements to > DBAs instead prior to rollout. > Currently the broker does not support this scenario. If the required tables > already exist the broker fails to start. > A better approach is that if the broker detects empy tables and initializes > them in the very same way it does if the tables dont't exist. > See also discussion in > [forum|http://activemq.2283324.n4.nabble.com/ARTEMIS-Server-doesn-t-start-if-JDBC-store-is-used-and-table-NODE-MANAGER-STORE-is-empty-td4735779.html]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1846) Using activemq.usemaskedpassword in URL is broken
[
https://issues.apache.org/jira/browse/ARTEMIS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1846.
Resolution: Fixed
> Using activemq.usemaskedpassword in URL is broken
> -
>
> Key: ARTEMIS-1846
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1846
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.6.0
>
>
> Specifying {{activemq.usemaskedpassword}} in the URL of a connector results
> in this exception:
> {noformat}
> WARN: AMQ212007: connector.create or connectorFactory.createConnector should
> never throw an exception, implementation is badly behaved, but we will deal
> with it anyway.
> java.lang.ClassCastException: java.lang.String cannot be cast to
> java.lang.Boolean
> at
> org.apache.activemq.artemis.utils.ConfigurationHelper.getPasswordProperty(ConfigurationHelper.java:166)
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector.(NettyConnector.java:339)
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector.(NettyConnector.java:272)
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnectorFactory.createConnector(NettyConnectorFactory.java:39)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createConnector(ClientSessionFactoryImpl.java:1053)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createTransportConnection(ClientSessionFactoryImpl.java:1074)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.establishNewConnection(ClientSessionFactoryImpl.java:1264)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:891)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:795)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:238)
> at
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:775)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:768)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:269)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:264)
> at
> org.apache.activemq.artemis.jms.example.SSLExample.main(SSLExample.java:47)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.activemq.artemis.maven.ArtemisClientPlugin.doExecute(ArtemisClientPlugin.java:61)
> at
> org.apache.activemq.artemis.maven.ArtemisAbstractPlugin.execute(ArtemisAbstractPlugin.java:74)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Closed] (ARTEMIS-1777) Adding AMQP as an option on producer & consumer & import
[ https://issues.apache.org/jira/browse/ARTEMIS-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1777. Resolution: Fixed > Adding AMQP as an option on producer & consumer & import > > > Key: ARTEMIS-1777 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1777 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > We need a way to import, consume and produce using AMQP. > > --protocol amqp as an option on the CLI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1744) Address or queue containing '*' or '?' cannot be deleted from hawtio console
[ https://issues.apache.org/jira/browse/ARTEMIS-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1744. Resolution: Fixed Fix Version/s: 2.6.0 > Address or queue containing '*' or '?' cannot be deleted from hawtio console > > > Key: ARTEMIS-1744 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1744 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Stanislav Knot >Assignee: Stanislav Knot >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1821) LDAPLoginModule always returns true on commit()
[ https://issues.apache.org/jira/browse/ARTEMIS-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1821. Resolution: Fixed > LDAPLoginModule always returns true on commit() > --- > > Key: ARTEMIS-1821 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1821 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1818) Reconnecting core JMS client won't re-create auto-created queue
[ https://issues.apache.org/jira/browse/ARTEMIS-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1818. Resolution: Fixed > Reconnecting core JMS client won't re-create auto-created queue > --- > > Key: ARTEMIS-1818 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1818 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.6.0 > > > Scenario: > * Start broker > * core JMS client sends message to queue > * broker auto-creates queue & receives message > * core JMS client creates consumer on queue and consumes the message; > consumer's connection uses reconnectAttempts=-1 > * stop broker > * during shutdown the consumer is disconnected and since the message-count is > already 0 that means the broker will auto-delete the consumer's queue > * start broker > * consumer automatically reconnects > * broker throws an error that the consumer's queue doesn't exist > * consumer is broken and will not receive any messages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1832) HAAutomaticBackupSharedStoreTest::basicDiscovery is dead
[ https://issues.apache.org/jira/browse/ARTEMIS-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1832. Resolution: Fixed > HAAutomaticBackupSharedStoreTest::basicDiscovery is dead > > > Key: ARTEMIS-1832 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1832 > Project: ActiveMQ Artemis > Issue Type: Test > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > Fix For: 2.6.0 > > > HAAutomaticBackupSharedStoreTest::basicDiscovery is creating queues on not > existing nodes and is not setting up any SessionFactory on the existing ones. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1785) CLI producer with text messages is broken
[ https://issues.apache.org/jira/browse/ARTEMIS-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1785. Resolution: Fixed > CLI producer with text messages is broken > - > > Key: ARTEMIS-1785 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1785 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: clebert suconic >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > Using ./artemis producer with a text message is broken as the .txt file > cannot be located > > example: > > ./artemis producer --text-size 1000 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1791) Large message files are not removed after redistribution across a cluster
[ https://issues.apache.org/jira/browse/ARTEMIS-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1791. Resolution: Fixed Fix Version/s: 2.6.0 > Large message files are not removed after redistribution across a cluster > - > > Key: ARTEMIS-1791 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1791 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.7.0 >Reporter: Ingo Weiss >Assignee: Howard Gao >Priority: Major > Fix For: 2.6.0 > > > Large messages are not removed from the large messages directory after they > have been redistributed to other nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1780) AMQP: NPE when dispatching ObjectMessage that was handled as a Large Message
[ https://issues.apache.org/jira/browse/ARTEMIS-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1780. Resolution: Fixed > AMQP: NPE when dispatching ObjectMessage that was handled as a Large Message > > > Key: ARTEMIS-1780 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1780 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.5.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 2.6.0 > > > When JMS ObjectMessage is sent which end up being treated as a large message > and is converted to / from Core the dispatch of the message throws an NPE > seemingly because the ServerJMSObjectMessage and converter code is calling > the wrong method to get the underlying buffer. The other message types go > through a getDataBuffer method while the ObjectMessage handler code uses a > getBodyBuffer that doesn't account for the case of the message being "Large" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1790) Improve Topology Member Finding
[ https://issues.apache.org/jira/browse/ARTEMIS-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1790. Resolution: Fixed > Improve Topology Member Finding > --- > > Key: ARTEMIS-1790 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1790 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Major > Fix For: 2.6.0 > > > When finding out if a connector belong to a target node it compares the whole > parameter map which is not necessary. Also in understanding the connector the > best place is to delegate it to the corresponding remoting connection who > understands it. (e.g. INVMConnection knows whether the connector belongs to a > target node by checking it's serverID only. The netty ones only need to match > host and port, and understanding that localhost and 127.0.0.1 are same thing). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1764) Broker does not start properly if prepared tx exists with ack to non existent queue
[ https://issues.apache.org/jira/browse/ARTEMIS-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1764. Resolution: Fixed > Broker does not start properly if prepared tx exists with ack to non existent > queue > --- > > Key: ARTEMIS-1764 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1764 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Martyn Taylor >Priority: Major > Fix For: 2.6.0 > > > A Tx exists with an ack or messagequeue X in prepared state. If X is deleted > and the broker stopped and started. The journal loader throws an exception > and the broker does not start properly. Acceptors are not started etc... > > 2018-03-22 13:35:07,149 WARN [org.apache.activemq.artemis.core.server] > AMQ222043: Message for queue 6,107,672 which does not exist. This message > will be ignored. > 2018-03-22 13:35:07,152 ERROR [org.apache.activemq.artemis.core.server] > AMQ224000: Failure in initialisation: java.lang.IllegalStateException: Cannot > find queue with id 6107672 > at > org.apache.activemq.artemis.core.server.impl.PostOfficeJournalLoader.handlePreparedAcknowledge(PostOfficeJournalLoader.java:306) > [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at > org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadPreparedTransactions(AbstractJournalStorageManager.java:1721) > [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at > org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:1169) > [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at > org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2588) > [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at > org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:2346) > [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at > org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:71) > [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at > org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:522) > [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at > org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:461) > [artemis-server-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at > org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:111) > [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:82) > [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149) > [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:97) > [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:124) > [artemis-cli-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [rt.jar:1.8.0_151] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [rt.jar:1.8.0_151] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [rt.jar:1.8.0_151] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] > at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129) > [artemis-boot.jar:2.6.0-SNAPSHOT] > at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49) > [artemis-boot.jar:2.6.0-SNAPSHOT] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1842) Vote is blocked on Netty Thread
[ https://issues.apache.org/jira/browse/ARTEMIS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1842. Resolution: Fixed > Vote is blocked on Netty Thread > --- > > Key: ARTEMIS-1842 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1842 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: clebert suconic >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > Topology Updates are sent through the Netty Thread. The voting will wait a > completion on a topology update, what can cause a distributed deadlock. > > the fix is to always use executors on topology updates or to have the Voting > to get away from the topology update. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1772) Reduce memory footprint and allocations of QueueImpl
[ https://issues.apache.org/jira/browse/ARTEMIS-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1772. Resolution: Fixed > Reduce memory footprint and allocations of QueueImpl > > > Key: ARTEMIS-1772 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1772 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > > Each message referenced into QueueImpl is using Atomic* and boxed types that > could be turned into primitive types, reducing the number of allocations and > increasing the precision of the memory footprint estimation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1768) Openwire connection logs failures on clean close
[ https://issues.apache.org/jira/browse/ARTEMIS-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1768. Resolution: Fixed Fix Version/s: 2.6.0 > Openwire connection logs failures on clean close > > > Key: ARTEMIS-1768 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1768 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1845) Timestamp header field should display in human readable format on console.
[ https://issues.apache.org/jira/browse/ARTEMIS-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1845. Resolution: Fixed > Timestamp header field should display in human readable format on console. > --- > > Key: ARTEMIS-1845 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1845 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Web Console >Affects Versions: 2.5.0 >Reporter: Shailendra Kumar singh >Priority: Major > Fix For: 2.6.0 > > Attachments: ConsoleView.png > > > Timestamp header field should display in human readable format on console. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1829) Remove deprecated plugin's messageExpired implementations
[ https://issues.apache.org/jira/browse/ARTEMIS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1829. Resolution: Fixed > Remove deprecated plugin's messageExpired implementations > - > > Key: ARTEMIS-1829 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1829 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > Fix For: 2.6.0 > > > NotificationActiveMQServerPlugin and LoggingActiveMQServerPlugin are > implementing the deprecated version of ActiveMQServerPlugin::messageExpired > that is not called by the new version of the method nor any other part of the > code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1837) Replication catch up dead locks with clients failing
[ https://issues.apache.org/jira/browse/ARTEMIS-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1837. Resolution: Fixed > Replication catch up dead locks with clients failing > > > Key: ARTEMIS-1837 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1837 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > if a client failed during the initial replication catch up, the Netty thread > would be used to issue an error and reconnect, but the catchup may be waiting > completion. Result is a deadlock freezing both backup and live. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1806) JDBC Connection leaks
[ https://issues.apache.org/jira/browse/ARTEMIS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1806. Resolution: Fixed > JDBC Connection leaks > - > > Key: ARTEMIS-1806 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1806 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > > The JDBC Connection leaks on: > * JDBCFileUtils::getDBFileDriver(DataSource, SQLProvider) > * SharedStoreBackupActivation.FailbackChecker::run on a failed > awaitLiveStatus -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1774) Node Manager Store table name should be configurable
[ https://issues.apache.org/jira/browse/ARTEMIS-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1774. Resolution: Fixed > Node Manager Store table name should be configurable > > > Key: ARTEMIS-1774 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1774 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1775) Mismatch in Windows cmd files using ARTEMIS_INSTANCE_ETC and ARTEMIS_ETC_INSTANCE
[ https://issues.apache.org/jira/browse/ARTEMIS-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1775. Resolution: Fixed > Mismatch in Windows cmd files using ARTEMIS_INSTANCE_ETC and > ARTEMIS_ETC_INSTANCE > - > > Key: ARTEMIS-1775 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1775 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.5.0 >Reporter: Benjamin Graf >Priority: Major > Fix For: 2.6.0 > > > Actually both version are used ARTEMIS_INSTANCE_ETC and ARTEMIS_ETC_INSTANCE. > ARTEMIS_ETC_INSTANCE seems wrong in artemis.profile.cmd > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1838) Race on converting isDurable from AMQP to Core
[ https://issues.apache.org/jira/browse/ARTEMIS-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1838. Resolution: Fixed > Race on converting isDurable from AMQP to Core > -- > > Key: ARTEMIS-1838 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1838 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.5.0 >Reporter: clebert suconic >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > When converting many messages from AMQP to Core, the durable property gets > misplaced 1 in 1000 conversions done in multi-thread. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1810) JDBCSequentialFileFactoryDriver should check <=0 read length
[ https://issues.apache.org/jira/browse/ARTEMIS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1810. Resolution: Fixed > JDBCSequentialFileFactoryDriver should check <=0 read length > > > Key: ARTEMIS-1810 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1810 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1752) Avoid null pointer in bridge
[ https://issues.apache.org/jira/browse/ARTEMIS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1752. Resolution: Fixed > Avoid null pointer in bridge > > > Key: ARTEMIS-1752 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1752 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: 2.6.0 > > > serverLocator.notifyNodeDown(System.currentTimeMillis(), targetNodeID); > > shpould have a null guard in BridgeImpl.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1847) Update Netty to 4-1-24-Final
[ https://issues.apache.org/jira/browse/ARTEMIS-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1847. Resolution: Fixed > Update Netty to 4-1-24-Final > > > Key: ARTEMIS-1847 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1847 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Timothy Bish >Priority: Minor > Fix For: 2.6.0 > > > Update to latest netty release. Matches release used in Qpid JMS version > used currently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1765) Compressed Large Messages are not converted to other protocols
[ https://issues.apache.org/jira/browse/ARTEMIS-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1765. Resolution: Fixed > Compressed Large Messages are not converted to other protocols > -- > > Key: ARTEMIS-1765 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1765 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: clebert suconic >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1862) fix acceptor config default for 'amqpLowCredits' and update related code defaults
[ https://issues.apache.org/jira/browse/ARTEMIS-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1862. Resolution: Fixed > fix acceptor config default for 'amqpLowCredits' and update related code > defaults > - > > Key: ARTEMIS-1862 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1862 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.5.0 >Reporter: Robbie Gemmell >Priority: Major > Fix For: 2.6.0 > > > The brokers AMQP protocol support has configurable 'amqpCredits' and > 'amqpLowCredits' values to govern the amount of credit given to a producer at > a time and when it is refreshed. The broker.xml files appears to set these to > values of 1000 and 300 respectively by default, while the code has default > values of 100 and 30 instead. > The XML configuration for the 'amqp' acceptor (using the AMQP port, 5672) has > incorrectly had the value 'amqpMinCredits' applied rather than > 'amqpLowCredits' as required and used on the 'artemis' acceptor, and as > result this has no effect and the codes fallback of 30 gets used instead. > This results in the broker waiting until it has processed very nearly every > message a producer could have sent with the outstanding credit before sending > any new credit, meaning producers with reasonable throughput will likely get > stalled awaiting more credit repeatedly. > The change in the coming PR corrects the XML config, changes the code to use > the same values as this for a consistent default, and adds a test to verify > the default credit refresh behaviour is as expected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1848) Auto deletion broken for OpenWire clients
[ https://issues.apache.org/jira/browse/ARTEMIS-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1848. Resolution: Fixed > Auto deletion broken for OpenWire clients > - > > Key: ARTEMIS-1848 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1848 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.6.0 > > > Queues created based on the creation of a consumer are not properly > auto-deleted when the consumer disconnects and the queue has no messages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1843) AMQP: Update Qpid JMS to latest 0.32.0 release and Proton-j to 0.27.1 to match
[ https://issues.apache.org/jira/browse/ARTEMIS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1843. Resolution: Fixed > AMQP: Update Qpid JMS to latest 0.32.0 release and Proton-j to 0.27.1 to match > -- > > Key: ARTEMIS-1843 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1843 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP >Affects Versions: 2.5.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 2.6.0 > > > Update broker to latest Qpid JMS 0.32.0 release and Proton-J 0.27.1 release > The latest proton-j release contains several fixes and improvements to > transfers spread across multiple frames as well as some other new API to aid > in handling transfer payloads without needing to copy the payload body buffer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1762) JdbcNodeManager shouldn't be used if no HA is configured
[ https://issues.apache.org/jira/browse/ARTEMIS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1762. Resolution: Fixed > JdbcNodeManager shouldn't be used if no HA is configured > > > Key: ARTEMIS-1762 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1762 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > > JDBC based journal is using a JdbcNodeManager when no HA is configured: > should be better to not have it to avoid unneeded lock table creations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1776) Implement asynchronous flow control on bridge and clustered bridge
[ https://issues.apache.org/jira/browse/ARTEMIS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1776. Resolution: Fixed > Implement asynchronous flow control on bridge and clustered bridge > -- > > Key: ARTEMIS-1776 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1776 > Project: ActiveMQ Artemis > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: clebert suconic >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > Currently the flow control on the Bridge is based on back pressure only, > through Netty writeable interfaces. > > If the user selected a positive producerWindowSize the Queue may block while > the Processing is happening. What could lead to distributed deadlocks on the > Bridge. > > This will avoid that possibility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1809) Add example showing Virtual Topic Mapping
[ https://issues.apache.org/jira/browse/ARTEMIS-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1809. Resolution: Fixed > Add example showing Virtual Topic Mapping > -- > > Key: ARTEMIS-1809 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1809 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: OpenWire >Affects Versions: 2.5.0 >Reporter: Pat Fox >Priority: Minor > Fix For: 2.6.0 > > > Add a simple example to demonstrate the use of > "virtualTopicConsumerWildcards" to map ActiveMQ 5.x virtual topic consumers > to use the Artemis Address model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1767) JDBC Lock Acquisition Timeout should behave like the file based version
[ https://issues.apache.org/jira/browse/ARTEMIS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1767. Resolution: Fixed > JDBC Lock Acquisition Timeout should behave like the file based version > --- > > Key: ARTEMIS-1767 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1767 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > > The journal lock timeout (file-based) is infinite by default, not > customizable by the user's configuration and exposed programmatically just > for testing purposes: the JDBC version of it need to do the same in order to > avoid being misconfigured, breaking JDBC HA reliability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1819) Missing fields on listAllConsumersAsJSON, listConsumersAsJSON and listConnectionsAsJSON
[ https://issues.apache.org/jira/browse/ARTEMIS-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1819. Resolution: Fixed Fix Version/s: 2.6.0 > Missing fields on listAllConsumersAsJSON, listConsumersAsJSON and > listConnectionsAsJSON > --- > > Key: ARTEMIS-1819 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1819 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.5.0 >Reporter: Ingo Weiss >Priority: Minor > Labels: regresion > Fix For: 2.6.0 > > > This is a regression against 1.5.5. Some fields are missing. On > listConsumersAsJSON and listAllConsumersAsJSON the fields are > destinationName, destinationType and durable. listConnectionsAsJSON is > missing clientID. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1782) Missing drop-down menu with create/delete/browse buttons in hawtio console
[ https://issues.apache.org/jira/browse/ARTEMIS-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1782. Resolution: Fixed > Missing drop-down menu with create/delete/browse buttons in hawtio console > -- > > Key: ARTEMIS-1782 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1782 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Stanislav Knot >Assignee: Stanislav Knot >Priority: Major > Fix For: 2.6.0 > > > When hawtio console is opened, there is drop-down menu, that usually contains > 'create' 'delete' or 'browse' buttons, missing. Even though refreshing the > page helps, it is not obvious that it will solve the issue. It causes > confusion and is annoying to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1839) NettyConnector is ignoring sniHost on Kerberos connection
[ https://issues.apache.org/jira/browse/ARTEMIS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1839. Resolution: Fixed > NettyConnector is ignoring sniHost on Kerberos connection > - > > Key: ARTEMIS-1839 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1839 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: clebert suconic >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > This was regressed on > [6501c3d|https://github.com/apache/activemq-artemis/commit/6501c3de1fc8d440923b241f95a4f7f0ead6a7c3] > The sniHost started being ignored on the SSLContext. > > org.apache.activemq.artemis.tests.integration.ssl.CoreClientOverOneWaySSLKerb5Test.testOneWaySSLWithGoodClientCipherSuite > was failing because of this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1793) Do not expose the _AMQ_ROUTING_TYPE header (at least) in STOMP
[
https://issues.apache.org/jira/browse/ARTEMIS-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1793.
Resolution: Fixed
> Do not expose the _AMQ_ROUTING_TYPE header (at least) in STOMP
> --
>
> Key: ARTEMIS-1793
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1793
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: STOMP
>Affects Versions: 2.5.0
>Reporter: Lionel Cons
>Assignee: Justin Bertram
>Priority: Minor
> Fix For: 2.6.0
>
>
> Artemis currently exposes the {{_AMQ_ROUTING_TYPE}} at least when using STOMP.
> Here is what a STOMP {{MESSAGE}} frame currently looks like (header part
> only):
> {code}
> _AMQ_ROUTING_TYPE:1
> content-length:1
> content-type:text/unknown
> destination:whatever
> expires:0
> message-id:123
> persistent:false
> priority:4
> redelivered:false
> timestamp:1523267009887
> {code}
> All the header lines are useful (and with typical lowercase names) except
> {{_AMQ_ROUTING_TYPE}}.
> If this information can be useful to messaging clients then a more "user
> friendly" name should be used and documented.
> Otherwise, this header should probably not be exposed, at least not by
> default.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1826) Hide embedded jetty version
[ https://issues.apache.org/jira/browse/ARTEMIS-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1826. Resolution: Fixed > Hide embedded jetty version > --- > > Key: ARTEMIS-1826 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1826 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.6.0 > > > This was first raised on the 5.x broker via AMQ-6951. However, it impacts > Artemis as well since it also uses embedded Jetty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-375) When use ./artemis data exp, the xml printed to stdout mixed with logging information
[ https://issues.apache.org/jira/browse/ARTEMIS-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-375. --- Resolution: Fixed > When use ./artemis data exp, the xml printed to stdout mixed with logging > information > - > > Key: ARTEMIS-375 > URL: https://issues.apache.org/jira/browse/ARTEMIS-375 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Howard Nguyen >Priority: Major > Fix For: 2.6.0 > > Attachments: XmlDataExport-improvement.patch > > > When use ./artemis data exp, the xml printed to stdout mixed with logging > information. > Attached patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1763) Remove 'quick check' before quorum
[ https://issues.apache.org/jira/browse/ARTEMIS-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1763. Resolution: Fixed > Remove 'quick check' before quorum > -- > > Key: ARTEMIS-1763 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1763 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: 2.6.0 > > > A check was added to SharedNothingBackupQuorum in isLiveDown method to > quickly check if the backup could still connect to the live. This should be > removed as it is unreliable and by passes the actual quorum vote. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1796) Flush during handshake of AMQP can cause issues with SASL clients
[ https://issues.apache.org/jira/browse/ARTEMIS-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1796. Resolution: Fixed > Flush during handshake of AMQP can cause issues with SASL clients > - > > Key: ARTEMIS-1796 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1796 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 > Environment: I found this by setting up a debug point on the > handshake. But as I saw it the flush could still happen shortly after causing > intermittent issues with SASL clients. > > The flush should be deferred until the initial handshake is finished. This is > as simple as only doing the flush if the first packet was received, and that > would be enough for this. > > The solution I'm implementing is to differentiate flushes from scheduled > flushes, and doing a regular flush if the first packet was received. >Reporter: clebert suconic >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1757) Improve DB2 compatibility
[ https://issues.apache.org/jira/browse/ARTEMIS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1757. Resolution: Fixed > Improve DB2 compatibility > - > > Key: ARTEMIS-1757 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1757 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1788) JDBC HA should use JDBC Network Timeout
[ https://issues.apache.org/jira/browse/ARTEMIS-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1788. Resolution: Fixed > JDBC HA should use JDBC Network Timeout > --- > > Key: ARTEMIS-1788 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1788 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > > The JDBC Node Manager doesn't use the JDBC Network Timeout used on the rest > of the Journal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1844) [Artemis Testsuite] CoreClientOverOneWaySSLTest.testOneWaySSLWithGoodClientCipherSuite[storeType=*] fails
[
https://issues.apache.org/jira/browse/ARTEMIS-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1844.
Resolution: Fixed
> [Artemis Testsuite]
> CoreClientOverOneWaySSLTest.testOneWaySSLWithGoodClientCipherSuite[storeType=*]
> fails
> -
>
> Key: ARTEMIS-1844
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1844
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
> Fix For: 2.6.0
>
>
> This is stable issue on IBM JDK.
> {code:java}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.fail(Assert.java:95)
> at
> org.apache.activemq.artemis.tests.integration.ssl.CoreClientOverOneWaySSLTest.testOneWaySSLWithGoodClientCipherSuite(CoreClientOverOneWaySSLTest.java:414)
> {code}
> {code:java|title=Test log}
> 13:00:22,253 INFO [org.apache.activemq.artemis.core.server] #*#*# Starting
> test: testOneWaySSLWithGoodClientCipherSuite[storeType=JCEKS]()...
> #test testOneWaySSLWithGoodClientCipherSuite[storeType=JCEKS]
> 13:00:22,258 INFO [org.apache.activemq.artemis.core.server] AMQ221000: live
> Message Broker is starting with configuration Broker Configuration
> (clustered=false,journalDirectory=/mnt/hudson_workspace/artemis-project-testsuite-rhel-master-local-discs/666ed8c2/tests/integration-tests/./target/tmp/junit3344164161239630016/journal,bindingsDirectory=/mnt/hudson_workspace/artemis-project-testsuite-rhel-master-local-discs/666ed8c2/tests/integration-tests/./target/tmp/junit3344164161239630016/bindings,largeMessagesDirectory=/mnt/hudson_workspace/artemis-project-testsuite-rhel-master-local-discs/666ed8c2/tests/integration-tests/./target/tmp/junit3344164161239630016/large-msg,pagingDirectory=/mnt/hudson_workspace/artemis-project-testsuite-rhel-master-local-discs/666ed8c2/tests/integration-tests/./target/tmp/junit3344164161239630016/page)
> 13:00:22,260 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-server]. Adding protocol support for: CORE
> 13:00:22,261 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-amqp-protocol]. Adding protocol support for:
> AMQP
> 13:00:22,261 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-stomp-protocol]. Adding protocol support for:
> STOMP
> 13:00:22,262 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-openwire-protocol]. Adding protocol support
> for: OPENWIRE
> 13:00:22,263 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
> for: HORNETQ
> 13:00:22,264 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-mqtt-protocol]. Adding protocol support for:
> MQTT
> 13:00:22,279 INFO [org.apache.activemq.artemis.core.server] AMQ221020:
> Started Acceptor at localhost:61616 for protocols
> [CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
> 13:00:22,279 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server
> is now live
> 13:00:22,279 INFO [org.apache.activemq.artemis.core.server] AMQ221001: Apache
> ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010
> [nodeID=048e5da0-b7c4-11e5-9b66-4f0c52a9abc9]
> 13:00:22,283 INFO [org.apache.activemq.artemis.tests.integration] Using
> suite: SSL_DHE_DSS_WITH_AES_128_CBC_SHA256
> 13:00:22,312 WARNING [io.netty.channel.DefaultChannelPipeline] An
> exceptionCaught() event was fired, and it reached at the tail of the
> pipeline. It usually means the last handler in the pipeline did not handle
> the exception.: io.netty.handler.codec.DecoderException:
> javax.net.ssl.SSLHandshakeException: no cipher suites in common
> at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:358)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:230)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
>
[jira] [Closed] (ARTEMIS-1760) JDBC HA should have configurable tolerance of DB time misalignment
[ https://issues.apache.org/jira/browse/ARTEMIS-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1760. Resolution: Fixed > JDBC HA should have configurable tolerance of DB time misalignment > -- > > Key: ARTEMIS-1760 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1760 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1816) OpenWire should avoid ByteArrayOutputStream lazy allocation
[ https://issues.apache.org/jira/browse/ARTEMIS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1816. Resolution: Fixed > OpenWire should avoid ByteArrayOutputStream lazy allocation > --- > > Key: ARTEMIS-1816 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1816 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker, OpenWire >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Minor > Fix For: 2.6.0 > > > OpenWireMessageConverter::toAMQMessage on bytes messages is lazy allocating a > write buffer with a default size of 1024 even when it won't be used to write > anything. > To avoid an useless allocation would be better to reduce it to a zero length > one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1851) IllegalStateException in web console
[
https://issues.apache.org/jira/browse/ARTEMIS-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1851.
Resolution: Fixed
> IllegalStateException in web console
>
>
> Key: ARTEMIS-1851
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1851
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Lionel Cons
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.6.0
>
>
> Using the default configuration, when browsing the toplevel broker object
> from the web console, the {{ReplicaSync}} attribute contains:
> {code}
> ERROR: java.lang.IllegalStateException : AMQ119118: Management method not
> applicable for current server configuration
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1747) When Broker Stops and Starts configuration changes by reload are lost
[ https://issues.apache.org/jira/browse/ARTEMIS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1747. Resolution: Fixed > When Broker Stops and Starts configuration changes by reload are lost > - > > Key: ARTEMIS-1747 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1747 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Michael Andre Pearce >Assignee: Michael Andre Pearce >Priority: Blocker > Fix For: 2.6.0 > > > When the broker is stopped and started (not JVM restart) e.g. by the > NetworkHealthChecker when a network is detected unhealthy and then becomes > healthy again, the broker looses any configuration changes made by reload. > address-settings > security-settings > addresses > queues > > This seems to be due to initializing step uses the stored configuration > object thats created on JVM start, and this is never updated when reloads > occur, thus why on start and stop broker configuration is reverted to the > state when broker first started. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1800) Incorrect number of messages on queue after remove of scheduled message
[
https://issues.apache.org/jira/browse/ARTEMIS-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1800.
Resolution: Fixed
> Incorrect number of messages on queue after remove of scheduled message
> ---
>
> Key: ARTEMIS-1800
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1800
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Justin Bertram
>Assignee: Christopher L. Shannon
>Priority: Major
> Fix For: 2.6.0
>
>
> This will reproduce the failure if added to
> {{org.apache.activemq.artemis.tests.integration.management.QueueControlTest}}:
> {noformat}
>@Test
>public void testGetScheduledCountOnRemove() throws Exception {
> long delay = Integer.MAX_VALUE;
> SimpleString address = RandomUtil.randomSimpleString();
> SimpleString queue = RandomUtil.randomSimpleString();
> session.createQueue(address, RoutingType.MULTICAST, queue, null,
> durable);
> QueueControl queueControl = createManagementControl(address, queue);
> Assert.assertEquals(0, queueControl.getScheduledCount());
> ClientProducer producer = session.createProducer(address);
> ClientMessage message = session.createMessage(durable);
> message.putLongProperty(Message.HDR_SCHEDULED_DELIVERY_TIME,
> System.currentTimeMillis() + delay);
> producer.send(message);
> queueControl.removeAllMessages();
> Assert.assertEquals(0, queueControl.getMessageCount());
> session.deleteQueue(queue);
>}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1770) Warnings/Errors during clean shutdown of server with JMS Bridge
[
https://issues.apache.org/jira/browse/ARTEMIS-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1770.
Resolution: Fixed
> Warnings/Errors during clean shutdown of server with JMS Bridge
> ---
>
> Key: ARTEMIS-1770
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1770
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
> Fix For: 2.6.0
>
>
> If server with JMS bridge is cleanly shutdown then following errors appears
> in the server log:
> {code}
> 16:03:06,458 ERROR [org.apache.activemq.artemis.core.client] (ServerService
> Thread Pool -- 76) AMQ214004: XA end operation failed :
> ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119010:
> Connection is destroyed]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:338)
> [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:318)
> [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaEnd(ActiveMQSessionContext.java:383)
> [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1173)
> [artemis-core-client-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
> at
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.doEnd(TransactionImple.java:1069)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.endAssociation(TransactionImple.java:1040)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.endAssociation(XAResourceRecord.java:1287)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at
> com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:313)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3023)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at
> com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3002)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at
> com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1674)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:124)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:284)
> [narayana-jts-idlj-5.5.5.Final-redhat-1.jar:5.5.5.Final-redhat-1 (revision:
> c79e6)]
> at
> org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Entry.rollbackLocal(JBossLocalTransactionProvider.java:317)
> at
> org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.rollbackLocal(JBossJTALocalTransactionProvider.java:116)
> at
> org.wildfly.transaction.client.LocalTransaction.rollback(LocalTransaction.java:87)
> at
> org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.stop(JMSBridgeImpl.java:501)
> [artemis-jms-server-1.5.3.003-redhat-1.jar:1.5.3.003-redhat-1]
> at
> org.wildfly.extension.messaging.activemq.jms.bridge.JMSBridgeService$2.run(JMSBridgeService.java:127)
>
> [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-15.jar:7.1.0.Alpha1-redhat-15]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [rt.jar:1.8.0_71]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [rt.jar:1.8.0_71]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [jboss-threads-2.2.1.Final-redhat-1.jar:2.2.1.Final-redhat-1]
> 16:03:06,464 WARN [com.arjuna.ats.jta] (ServerService Thread Pool -- 76)
> ARJUNA016129: Could not end XA resource ClientSessionImpl
> [name=9969f262-0f10-11e7-a802-3ca9f4349bfc, username=johnOut,
[jira] [Closed] (ARTEMIS-1823) Log warning on boot when persistence is disabled and paging enabled
[
https://issues.apache.org/jira/browse/ARTEMIS-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1823.
Resolution: Fixed
> Log warning on boot when persistence is disabled and paging enabled
> ---
>
> Key: ARTEMIS-1823
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1823
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jiri Ondrusek
>Priority: Major
> Fix For: 2.6.0
>
>
> When Artemis server persistence is disabled and address policy is set to
> {{PAGE}}, page files are still persisted.
> If this configuration is detected on server start, log warning message that
> despite disabled persistence, page files will be persisted.
> *Customer scenario*: When persistence is disabled and paging is used,
> customer may not be aware that page files need to be persisted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1748) AMQP client connections are not cleaned up properly on connectionDestroyed
[ https://issues.apache.org/jira/browse/ARTEMIS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1748. Resolution: Fixed > AMQP client connections are not cleaned up properly on connectionDestroyed > -- > > Key: ARTEMIS-1748 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1748 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Ulf Lilleengen >Priority: Major > Fix For: 2.6.0 > > > Similar to https://issues.apache.org/jira/browse/ARTEMIS-1050 but for the > AMQPClientConnectionFactory and ProtonClientConnectionManager > PR: [https://github.com/apache/activemq-artemis/pull/1955] > > In general it would be good to get a review of those to classes to ensure > they are doing the correct thing on failures etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1779) ClusterConnectionBridge may connect to other nodes than its target
[ https://issues.apache.org/jira/browse/ARTEMIS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1779. Resolution: Fixed > ClusterConnectionBridge may connect to other nodes than its target > -- > > Key: ARTEMIS-1779 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1779 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Major > Fix For: 2.6.0 > > > The cluster connection bridge has a TopologyListener and connects to a new > node each time it receives a nodeUp() event. It needs to put a check here to > make sure that the cluster bridge only connects to its target node and it's > backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1808) LargeServerMessageImpl leaks direct ByteBuffer
[ https://issues.apache.org/jira/browse/ARTEMIS-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1808. Resolution: Fixed > LargeServerMessageImpl leaks direct ByteBuffer > -- > > Key: ARTEMIS-1808 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1808 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1799) Create a NotificationActiveMQServerPlugin to publish new types of notifications
[ https://issues.apache.org/jira/browse/ARTEMIS-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1799. Resolution: Fixed > Create a NotificationActiveMQServerPlugin to publish new types of > notifications > --- > > Key: ARTEMIS-1799 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1799 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 2.5.0 >Reporter: Christopher L. Shannon >Assignee: Christopher L. Shannon >Priority: Major > Fix For: 2.6.0 > > > For monitoring the broker it would be helpful to support publishing of new > notification types that can be listened for. This is similar to the > advisories that ActiveMQ 5.x supports. > By adding this functionality to a plugin it can be easily enabled/disabled by > the user through configuration and fine tuned to a user's requirements. For > this initial Jira I'm proposing adding the following notification types: > connection creation/destroyed events, session created/closed events, address > added/removed events, delivered messages, and expired messages. > It will be easy to enhance these new notifications in future Jiras (ie add > more properties to the messages if necessary) and also easy to add new > notifications to the plugin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1754) LargeServerMessageImpl.toString() may leak files
[ https://issues.apache.org/jira/browse/ARTEMIS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1754. Resolution: Fixed > LargeServerMessageImpl.toString() may leak files > > > Key: ARTEMIS-1754 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1754 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.5.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Major > Fix For: 2.6.0 > > > This overridden method calls getPersistentSize() which may lead to open the > large file to get the size. Calling it alone will cause the file being opened > without closing it. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1824) Broker cannot run from path containing unicode characters
[
https://issues.apache.org/jira/browse/ARTEMIS-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1824.
Resolution: Fixed
Fix Version/s: 2.6.0
> Broker cannot run from path containing unicode characters
> -
>
> Key: ARTEMIS-1824
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1824
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
> Fix For: 2.6.0
>
>
> Reproducer:
> 1. create broker at path containing unicode char
> 2. run broker
> 3. you wil get something like this (broker will not start)
> {code:java}
> [sknot@sknot bin]$
> "/home/sknot/Veřejné/apache-artemis-2.6.0-SNAPSHOT/bin/slave/bin/artemis" run
> Listening for transport dt_socket at address: 5005
> __ _
>/ \ | |_ ___ __ __(_) _
> / _ \| _ \ __|/ _ \ \/ | |/ __/
> / ___ \ | \/ |_/ __/ |\/| | |\___ \
> /_/ \_\| \__\|_| |_|_|/___ /
> Apache ActiveMQ Artemis 2.6.0-SNAPSHOT
> Exception in thread "main" org.xml.sax.SAXParseException; systemId:
> jar:file:/home/sknot/Veřejné/apache-artemis-2.6.0-SNAPSHOT/lib/artemis-server-2.6.0-SNAPSHOT.jar!/schema/artemis-configuration.xsd;
> lineNumber: 1083; columnNumber: 51; src-resolve: Cannot resolve the name
> 'xml:specialAttrs' to a(n) 'attribute group' component.
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:4154)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4137)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1684)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseLocal(XSDAttributeGroupTraverser.java:80)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:643)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.processComplexContent(XSDComplexTypeTraverser.java:1123)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:335)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:191)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1894)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1782)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(XSDElementTraverser.java:405)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseGlobal(XSDElementTraverser.java:242)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(XSDHandler.java:1439)
> at
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:635)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:610)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:569)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:535)
> at
> com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:254)
> at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638)
> at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:670)
> at org.apache.activemq.artemis.utils.XMLUtil.validate(XMLUtil.java:327)
> at
> org.apache.activemq.artemis.core.config.FileDeploymentManager.readConfiguration(FileDeploymentManager.java:85)
> at
> org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:68)
> at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:82)
> at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:97)
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:124)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Closed] (ARTEMIS-1783) Exception in thread "main" java.lang.BootstrapMethodError: java.lang.NoClassDefFoundError: com/google/common/base/Supplier
[
https://issues.apache.org/jira/browse/ARTEMIS-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1783.
Resolution: Fixed
Fix Version/s: 2.6.0
> Exception in thread "main" java.lang.BootstrapMethodError:
> java.lang.NoClassDefFoundError: com/google/common/base/Supplier
> --
>
> Key: ARTEMIS-1783
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1783
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.5.0
>Reporter: Jiri Daněk
>Assignee: Justin Bertram
>Priority: Trivial
> Fix For: 2.6.0
>
>
> When using my program cli-artemis-jms at
> https://github.com/rh-messaging/cli-java, which depends on
> activemq-artemis-jms-client, I get the following stack trace
> {noformat}
> junit5(?) $ java -jar systemtests/client_executable/cli-artemis-jms.jar
> receiver --address test --log-msgs json --count 0
> Exception in thread "main" java.lang.BootstrapMethodError:
> java.lang.NoClassDefFoundError: com/google/common/base/Supplier
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessageObjectPools.(CoreMessageObjectPools.java:26)
> at
> org.apache.activemq.artemis.core.protocol.ClientPacketDecoder.(ClientPacketDecoder.java:36)
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createPacketDecoder(ActiveMQClientProtocolManager.java:520)
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.connect(ActiveMQClientProtocolManager.java:412)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.establishNewConnection(ClientSessionFactoryImpl.java:1273)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:891)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:795)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:238)
> at
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:784)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:813)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:277)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:272)
> at
> com.redhat.mqe.acc.AccConnectionManager.(AccConnectionManager.java:68)
> at
> com.redhat.mqe.acc.AccConnectionManagerFactory.make(AccConnectionManagerFactory.java:33)
> at
> com.redhat.mqe.acc.AccConnectionManagerFactory.make(AccConnectionManagerFactory.java:27)
> at com.redhat.mqe.lib.CoreClient.createConnection(CoreClient.java:86)
> at
> com.redhat.mqe.lib.ReceiverClient.consumeMessage(ReceiverClient.java:170)
> at
> com.redhat.mqe.lib.ReceiverClient.startClient(ReceiverClient.java:147)
> at com.redhat.mqe.lib.Main.main(Main.java:50)
> at com.redhat.mqe.acc.Main.main(Main.java:74)
> Caused by: java.lang.NoClassDefFoundError: com/google/common/base/Supplier
> ... 20 more
> Caused by: java.lang.ClassNotFoundException: com.google.common.base.Supplier
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 20 more
> {noformat}
> I get this with artemis-jms-client 2.5.0, but not with artemis-jms-client
> 2.4.0.
> I believe the guilty commit is in ARTEMIS-1586, "794e56da99456e Refactor to
> make more generic", which introduced usage of Google Guava, without adding it
> to the package's pom file, causing my maven to miss that transitive
> dependency when building uberjar.
> The command above runs when triggered from Intellij IDE, where the dependency
> is on classpath, for some reason.
> Workaround is easy, add Guava to dependencies of your own program which is
> using the artemis jms library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1743) NPE in server log when Artemis trace logging is enabled
[
https://issues.apache.org/jira/browse/ARTEMIS-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1743.
Resolution: Fixed
> NPE in server log when Artemis trace logging is enabled
> ---
>
> Key: ARTEMIS-1743
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1743
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.5.0
>Reporter: Miroslav Novak
>Assignee: Stanislav Knot
>Priority: Major
> Fix For: 2.6.0
>
>
> Artemis master (95b7438e7a7661692d5b78be944d05e254df9067) contains issue when
> trace logging is enabled.
> If large message is sent and Artemis trace logs are enabled then following
> NPE is logged in server log:
> {code}
> 09:42:14,005 WARN
> [org.apache.activemq.artemis.core.message.impl.CoreMessage] (default I/O-9)
> Error creating String for message: : java.lang.NullPointerException
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.encode(CoreMessage.java:584)
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.checkEncode(CoreMessage.java:248)
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.getEncodeSize(CoreMessage.java:647)
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.getPersistentSize(CoreMessage.java:1157)
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.toString(CoreMessage.java:1132)
> at java.lang.String.valueOf(String.java:2994) [rt.jar:1.8.0_131]
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> [rt.jar:1.8.0_131]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.wireformat.SessionSendLargeMessage.toString(SessionSendLargeMessage.java:73)
> at java.lang.String.valueOf(String.java:2994) [rt.jar:1.8.0_131]
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> [rt.jar:1.8.0_131]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:368)
> at
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:646)
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:297)
> at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:413)
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1359)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:935)
> at
> org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:443)
> at
> org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:379)
> at
> org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [xnio-api-3.6.1.Final.jar:3.6.1.Final]
> at
> org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [xnio-api-3.6.1.Final.jar:3.6.1.Final]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [xnio-nio-3.6.1.Final.jar:3.6.1.Final]
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> [xnio-nio-3.6.1.Final.jar:3.6.1.Final]
> {code}
> Currently it appears that it has not impact on functionality but NPEs are
> flooding server log.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1797) Auto-create-address flag shouldn't block temp destination creation
[ https://issues.apache.org/jira/browse/ARTEMIS-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic closed ARTEMIS-1797. Resolution: Fixed > Auto-create-address flag shouldn't block temp destination creation > -- > > Key: ARTEMIS-1797 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1797 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.5.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Major > Fix For: 2.6.0 > > > When creating a temp destination and auto-create-address set to false, the > broker throws an error and refuse to create it. This doesn't conform to > normal use-case (like amqp dynamic flag) where the temp destination should be > allowed even if the auto-create-address is false. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-1804) NPE in recent snapshot
[
https://issues.apache.org/jira/browse/ARTEMIS-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic closed ARTEMIS-1804.
Resolution: Fixed
> NPE in recent snapshot
> --
>
> Key: ARTEMIS-1804
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1804
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Lionel Cons
>Priority: Major
> Fix For: 2.6.0
>
>
> Running some tests against {{artemis-2.6.0-20180410.175207-36}}, I noticed
> the broker logged several NPEs looking like:
> {code:java}
> 2018-04-12 14:19:15,097 WARN [io.netty.handler.ssl.SslHandler] [id:
> 0xc8c4c74d, L:/xxx:yyy ! R:/aaa:bbb] flush() raised a masked exception.:
> java.lang.NullPointerException
> at io.netty.handler.ssl.SslHandler.wrapAndFlush(SslHandler.java:742)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.handler.ssl.SslHandler.flush(SslHandler.java:734)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.handler.ssl.SslHandler.flush(SslHandler.java:1595)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.handler.ssl.SslHandler.access$600(SslHandler.java:165)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.handler.ssl.SslHandler$1.run(SslHandler.java:631)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:309)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1822) Inconsistent method name
[
https://issues.apache.org/jira/browse/ARTEMIS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reopened ARTEMIS-1822:
--
> Inconsistent method name
>
>
> Key: ARTEMIS-1822
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1822
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: Broker
>Reporter: KuiLIU
>Priority: Trivial
> Fix For: 2.6.0
>
>
> The following method is named "lookupRecord".
> "lookupRecord" seems to find a related record.
> But the method is checking whether recordsSnapshot contains the id or not.
> Thus, the method name "containsRecord" is more intuitive than "lookupRecord".
> {code:java}
>public boolean lookupRecord(final long id) {
> return recordsSnapshot.contains(id);
>}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1783) Exception in thread "main" java.lang.BootstrapMethodError: java.lang.NoClassDefFoundError: com/google/common/base/Supplier
[
https://issues.apache.org/jira/browse/ARTEMIS-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reopened ARTEMIS-1783:
--
> Exception in thread "main" java.lang.BootstrapMethodError:
> java.lang.NoClassDefFoundError: com/google/common/base/Supplier
> --
>
> Key: ARTEMIS-1783
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1783
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.5.0
>Reporter: Jiri Daněk
>Assignee: Justin Bertram
>Priority: Trivial
>
> When using my program cli-artemis-jms at
> https://github.com/rh-messaging/cli-java, which depends on
> activemq-artemis-jms-client, I get the following stack trace
> {noformat}
> junit5(?) $ java -jar systemtests/client_executable/cli-artemis-jms.jar
> receiver --address test --log-msgs json --count 0
> Exception in thread "main" java.lang.BootstrapMethodError:
> java.lang.NoClassDefFoundError: com/google/common/base/Supplier
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessageObjectPools.(CoreMessageObjectPools.java:26)
> at
> org.apache.activemq.artemis.core.protocol.ClientPacketDecoder.(ClientPacketDecoder.java:36)
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createPacketDecoder(ActiveMQClientProtocolManager.java:520)
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.connect(ActiveMQClientProtocolManager.java:412)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.establishNewConnection(ClientSessionFactoryImpl.java:1273)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:891)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:795)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:238)
> at
> org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:784)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:813)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:277)
> at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:272)
> at
> com.redhat.mqe.acc.AccConnectionManager.(AccConnectionManager.java:68)
> at
> com.redhat.mqe.acc.AccConnectionManagerFactory.make(AccConnectionManagerFactory.java:33)
> at
> com.redhat.mqe.acc.AccConnectionManagerFactory.make(AccConnectionManagerFactory.java:27)
> at com.redhat.mqe.lib.CoreClient.createConnection(CoreClient.java:86)
> at
> com.redhat.mqe.lib.ReceiverClient.consumeMessage(ReceiverClient.java:170)
> at
> com.redhat.mqe.lib.ReceiverClient.startClient(ReceiverClient.java:147)
> at com.redhat.mqe.lib.Main.main(Main.java:50)
> at com.redhat.mqe.acc.Main.main(Main.java:74)
> Caused by: java.lang.NoClassDefFoundError: com/google/common/base/Supplier
> ... 20 more
> Caused by: java.lang.ClassNotFoundException: com.google.common.base.Supplier
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 20 more
> {noformat}
> I get this with artemis-jms-client 2.5.0, but not with artemis-jms-client
> 2.4.0.
> I believe the guilty commit is in ARTEMIS-1586, "794e56da99456e Refactor to
> make more generic", which introduced usage of Google Guava, without adding it
> to the package's pom file, causing my maven to miss that transitive
> dependency when building uberjar.
> The command above runs when triggered from Intellij IDE, where the dependency
> is on classpath, for some reason.
> Workaround is easy, add Guava to dependencies of your own program which is
> using the artemis jms library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1785) CLI producer with text messages is broken
[ https://issues.apache.org/jira/browse/ARTEMIS-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1785: -- > CLI producer with text messages is broken > - > > Key: ARTEMIS-1785 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1785 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: clebert suconic >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > Using ./artemis producer with a text message is broken as the .txt file > cannot be located > > example: > > ./artemis producer --text-size 1000 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1826) Hide embedded jetty version
[ https://issues.apache.org/jira/browse/ARTEMIS-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1826: -- > Hide embedded jetty version > --- > > Key: ARTEMIS-1826 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1826 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.6.0 > > > This was first raised on the 5.x broker via AMQ-6951. However, it impacts > Artemis as well since it also uses embedded Jetty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1800) Incorrect number of messages on queue after remove of scheduled message
[
https://issues.apache.org/jira/browse/ARTEMIS-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reopened ARTEMIS-1800:
--
> Incorrect number of messages on queue after remove of scheduled message
> ---
>
> Key: ARTEMIS-1800
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1800
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Justin Bertram
>Assignee: Christopher L. Shannon
>Priority: Major
> Fix For: 2.6.0
>
>
> This will reproduce the failure if added to
> {{org.apache.activemq.artemis.tests.integration.management.QueueControlTest}}:
> {noformat}
>@Test
>public void testGetScheduledCountOnRemove() throws Exception {
> long delay = Integer.MAX_VALUE;
> SimpleString address = RandomUtil.randomSimpleString();
> SimpleString queue = RandomUtil.randomSimpleString();
> session.createQueue(address, RoutingType.MULTICAST, queue, null,
> durable);
> QueueControl queueControl = createManagementControl(address, queue);
> Assert.assertEquals(0, queueControl.getScheduledCount());
> ClientProducer producer = session.createProducer(address);
> ClientMessage message = session.createMessage(durable);
> message.putLongProperty(Message.HDR_SCHEDULED_DELIVERY_TIME,
> System.currentTimeMillis() + delay);
> producer.send(message);
> queueControl.removeAllMessages();
> Assert.assertEquals(0, queueControl.getMessageCount());
> session.deleteQueue(queue);
>}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1836) Artemis broker for Windows does not set login.config path correctly
[
https://issues.apache.org/jira/browse/ARTEMIS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reopened ARTEMIS-1836:
--
> Artemis broker for Windows does not set login.config path correctly
> ---
>
> Key: ARTEMIS-1836
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1836
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.7.0
>Reporter: Joaquin Nadal
>Priority: Minor
> Fix For: 2.6.0
>
>
> On windows when creating a broker, the login.config file cannot be reached
> due to missing path.
> The issue can be replicated on a Windows machine by running _{{artemis create
> mybroker}}_, and trying to use that broker. An exception is printed to
> console saying file _/login.config_ cannot be found.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1449) Artemis does not start on Oracle JDK 9
[
https://issues.apache.org/jira/browse/ARTEMIS-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reopened ARTEMIS-1449:
--
> Artemis does not start on Oracle JDK 9
> --
>
> Key: ARTEMIS-1449
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1449
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.4.0
> Environment: {noformat}
> $ java --version
> java 9
> Java(TM) SE Runtime Environment (build 9+181)
> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)
> {noformat}
>Reporter: Jiri Daněk
>Priority: Minor
> Fix For: 2.6.0
>
>
> {noformat}
> apache-artemis-2.4.0-20171004.165128-60-bin]$ i0/bin/artemis run
> Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option
> UseFastAccessorMethods; support was removed in 9.0
> __ _
> / \ | |_ ___ __ __(_) _
>/ _ \| _ \ __|/ _ \ \/ | |/ __/
> / ___ \ | \/ |_/ __/ |\/| | |\___ \
> /_/ \_\| \__\|_| |_|_|/___ /
> Apache ActiveMQ Artemis 2.4.0-SNAPSHOT
> Exception in thread "main" java.lang.NoClassDefFoundError:
> javax/xml/bind/JAXBContext
> at org.apache.activemq.artemis.dto.XmlUtil.decode(XmlUtil.java:90)
> at
> org.apache.activemq.artemis.cli.factory.xml.XmlBrokerFactoryHandler.createBroker(XmlBrokerFactoryHandler.java:35)
> at
> org.apache.activemq.artemis.cli.factory.BrokerFactory.createBrokerConfiguration(BrokerFactory.java:46)
> at
> org.apache.activemq.artemis.cli.factory.BrokerFactory.createBrokerConfiguration(BrokerFactory.java:53)
> at
> org.apache.activemq.artemis.cli.commands.Configurable.getBrokerDTO(Configurable.java:105)
> at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:65)
> at
> org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:149)
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:96)
> at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:123)
> 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:564)
> at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129)
> at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBContext
> at
> java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:563)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
> ... 15 more
> {noformat}
> If I add the module in {{artemis.profile}}
> {noformat}
> JAVA_ARGS=" --add-modules java.xml.bind [...]
> {noformat}
> I then get
> {noformat}
> apache-artemis-2.4.0-20171004.165128-60-bin]$ i0/bin/artemis run
> Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option
> UseFastAccessorMethods; support was removed in 9.0
> __ _
> / \ | |_ ___ __ __(_) _
>/ _ \| _ \ __|/ _ \ \/ | |/ __/
> / ___ \ | \/ |_/ __/ |\/| | |\___ \
> /_/ \_\| \__\|_| |_|_|/___ /
> Apache ActiveMQ Artemis 2.4.0-SNAPSHOT
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by io.netty.util.internal.ReflectionUtil
> (file:/home/jdanek/Downloads/AMQ7/apache-artemis-2.4.0-20171004.165128-60-bin/apache-artemis-2.4.0-SNAPSHOT/lib/netty-all-4.1.16.Final.jar)
> to constructor java.nio.DirectByteBuffer(long,int)
> WARNING: Please consider reporting this to the maintainers of
> io.netty.util.internal.ReflectionUtil
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 12:10:31,825 INFO [org.apache.activemq.artemis.integration.bootstrap]
> AMQ101000: Starting ActiveMQ Artemis Server
> 12:10:31,891 INFO [org.apache.activemq.artemis.core.server] AMQ221000: live
> Message Broker is starting with configuration Broker Configuration
> (clustered=false,journalDirectory=./data/journal,bindingsDirectory=./data/bindings,largeMessagesDirectory=./data/large-messages,pagingDirectory=./data/paging)
> 12:10:31,923 INFO [org.apache.activemq.artemis.core.server] AMQ221013: Using
> NIO Journal
> 12:10:31,953 INFO [org.apache.activemq.artemis.core.server] AMQ221057:
> Global Max Size is being adjusted to 1/2 of the JVM max size (-Xmx). being
>
[jira] [Reopened] (ARTEMIS-1779) ClusterConnectionBridge may connect to other nodes than its target
[ https://issues.apache.org/jira/browse/ARTEMIS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1779: -- > ClusterConnectionBridge may connect to other nodes than its target > -- > > Key: ARTEMIS-1779 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1779 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Major > Fix For: 2.6.0 > > > The cluster connection bridge has a TopologyListener and connects to a new > node each time it receives a nodeUp() event. It needs to put a check here to > make sure that the cluster bridge only connects to its target node and it's > backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1752) Avoid null pointer in bridge
[ https://issues.apache.org/jira/browse/ARTEMIS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1752: -- > Avoid null pointer in bridge > > > Key: ARTEMIS-1752 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1752 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Andy Taylor >Assignee: Andy Taylor >Priority: Major > Fix For: 2.6.0 > > > serverLocator.notifyNodeDown(System.currentTimeMillis(), targetNodeID); > > shpould have a null guard in BridgeImpl.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1701) Zone ID not stripped properly from IPv6 addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1701: -- > Zone ID not stripped properly from IPv6 addresses > - > > Key: ARTEMIS-1701 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1701 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.4.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1753) When using the 1.5.5 Artemis JMS Client, NPE is thrown when creating a durable subscription
[ https://issues.apache.org/jira/browse/ARTEMIS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1753: -- > When using the 1.5.5 Artemis JMS Client, NPE is thrown when creating a > durable subscription > --- > > Key: ARTEMIS-1753 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1753 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Martyn Taylor >Priority: Major > Fix For: 2.6.0 > > > When creating a durable topic subcription using the Artemis 1.5.5 client a > QueueQuery is performed to see if the subscription already exists. There is > some code that converts the queue names to the old 1.x scheme. However, if > the subscription does not already exist, the conversion is attempted on a > null string, causing an NPE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1806) JDBC Connection leaks
[ https://issues.apache.org/jira/browse/ARTEMIS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1806: -- > JDBC Connection leaks > - > > Key: ARTEMIS-1806 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1806 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.5.0 >Reporter: Francesco Nigro >Assignee: Francesco Nigro >Priority: Major > Fix For: 2.6.0 > > > The JDBC Connection leaks on: > * JDBCFileUtils::getDBFileDriver(DataSource, SQLProvider) > * SharedStoreBackupActivation.FailbackChecker::run on a failed > awaitLiveStatus -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1758) Support SASL EXTERNAL
[ https://issues.apache.org/jira/browse/ARTEMIS-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1758: -- > Support SASL EXTERNAL > - > > Key: ARTEMIS-1758 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1758 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP >Affects Versions: 2.5.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Major > Fix For: 2.6.0 > > > Add support for SASL EXTERNAL > https://tools.ietf.org/html/rfc4422#appendix-A > Peer principal from TLS client cert is used as the client identity on the > broker. > The identity is mapped to a broker user and role via the > TextFileCertificateLoginModule -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-857) JMX+API support for viewing and manually clearing message group caches
[ https://issues.apache.org/jira/browse/ARTEMIS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-857: - > JMX+API support for viewing and manually clearing message group caches > -- > > Key: ARTEMIS-857 > URL: https://issues.apache.org/jira/browse/ARTEMIS-857 > Project: ActiveMQ Artemis > Issue Type: Sub-task > Components: Broker >Reporter: Matt Pavlovich >Priority: Major > Fix For: 2.6.0 > > > Need an API to support for viewing message group infomration and optionally > flushing group-id maps that are not cleared by mis-behaving clients. > ie.. client never sends the JMSXSeqID -1 message -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1804) NPE in recent snapshot
[
https://issues.apache.org/jira/browse/ARTEMIS-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reopened ARTEMIS-1804:
--
> NPE in recent snapshot
> --
>
> Key: ARTEMIS-1804
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1804
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Lionel Cons
>Priority: Major
> Fix For: 2.6.0
>
>
> Running some tests against {{artemis-2.6.0-20180410.175207-36}}, I noticed
> the broker logged several NPEs looking like:
> {code:java}
> 2018-04-12 14:19:15,097 WARN [io.netty.handler.ssl.SslHandler] [id:
> 0xc8c4c74d, L:/xxx:yyy ! R:/aaa:bbb] flush() raised a masked exception.:
> java.lang.NullPointerException
> at io.netty.handler.ssl.SslHandler.wrapAndFlush(SslHandler.java:742)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.handler.ssl.SslHandler.flush(SslHandler.java:734)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.handler.ssl.SslHandler.flush(SslHandler.java:1595)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.handler.ssl.SslHandler.access$600(SslHandler.java:165)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.handler.ssl.SslHandler$1.run(SslHandler.java:631)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:309)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
> [netty-all-4.1.22.Final.jar:4.1.22.Final]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.6.0-SNAPSHOT.jar:2.6.0-SNAPSHOT]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1818) Reconnecting core JMS client won't re-create auto-created queue
[ https://issues.apache.org/jira/browse/ARTEMIS-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1818: -- > Reconnecting core JMS client won't re-create auto-created queue > --- > > Key: ARTEMIS-1818 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1818 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.6.0 > > > Scenario: > * Start broker > * core JMS client sends message to queue > * broker auto-creates queue & receives message > * core JMS client creates consumer on queue and consumes the message; > consumer's connection uses reconnectAttempts=-1 > * stop broker > * during shutdown the consumer is disconnected and since the message-count is > already 0 that means the broker will auto-delete the consumer's queue > * start broker > * consumer automatically reconnects > * broker throws an error that the consumer's queue doesn't exist > * consumer is broken and will not receive any messages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1842) Vote is blocked on Netty Thread
[ https://issues.apache.org/jira/browse/ARTEMIS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1842: -- > Vote is blocked on Netty Thread > --- > > Key: ARTEMIS-1842 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1842 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: clebert suconic >Assignee: clebert suconic >Priority: Major > Fix For: 2.6.0 > > > Topology Updates are sent through the Netty Thread. The voting will wait a > completion on a topology update, what can cause a distributed deadlock. > > the fix is to always use executors on topology updates or to have the Voting > to get away from the topology update. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1746) Client-side openSSH support is broken
[ https://issues.apache.org/jira/browse/ARTEMIS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1746: -- > Client-side openSSH support is broken > - > > Key: ARTEMIS-1746 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1746 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Christian Sailer >Priority: Major > > The new feature to use openSSH via the netty-tcnative library in Artemis > 2.5.0 only works for enabling on the server side. > When enabling it on the client side, there are several issue, the first of > which is that it tries to use a server ssl context on the client side and > then fails due to a client/server mismatch. > Also, I could not find any integration tests actually using openSSL. > I am working on a patch to fix these issues including tests. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1747) When Broker Stops and Starts configuration changes by reload are lost
[ https://issues.apache.org/jira/browse/ARTEMIS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic reopened ARTEMIS-1747: -- > When Broker Stops and Starts configuration changes by reload are lost > - > > Key: ARTEMIS-1747 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1747 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Michael Andre Pearce >Assignee: Michael Andre Pearce >Priority: Blocker > Fix For: 2.6.0 > > > When the broker is stopped and started (not JVM restart) e.g. by the > NetworkHealthChecker when a network is detected unhealthy and then becomes > healthy again, the broker looses any configuration changes made by reload. > address-settings > security-settings > addresses > queues > > This seems to be due to initializing step uses the stored configuration > object thats created on JVM start, and this is never updated when reloads > occur, thus why on start and stop broker configuration is reverted to the > state when broker first started. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ARTEMIS-1844) [Artemis Testsuite] CoreClientOverOneWaySSLTest.testOneWaySSLWithGoodClientCipherSuite[storeType=*] fails
[
https://issues.apache.org/jira/browse/ARTEMIS-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reopened ARTEMIS-1844:
--
> [Artemis Testsuite]
> CoreClientOverOneWaySSLTest.testOneWaySSLWithGoodClientCipherSuite[storeType=*]
> fails
> -
>
> Key: ARTEMIS-1844
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1844
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 1.5.6, 2.5.0
>Reporter: Radovan Stancel
>Priority: Major
> Fix For: 2.6.0
>
>
> This is stable issue on IBM JDK.
> {code:java}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.fail(Assert.java:95)
> at
> org.apache.activemq.artemis.tests.integration.ssl.CoreClientOverOneWaySSLTest.testOneWaySSLWithGoodClientCipherSuite(CoreClientOverOneWaySSLTest.java:414)
> {code}
> {code:java|title=Test log}
> 13:00:22,253 INFO [org.apache.activemq.artemis.core.server] #*#*# Starting
> test: testOneWaySSLWithGoodClientCipherSuite[storeType=JCEKS]()...
> #test testOneWaySSLWithGoodClientCipherSuite[storeType=JCEKS]
> 13:00:22,258 INFO [org.apache.activemq.artemis.core.server] AMQ221000: live
> Message Broker is starting with configuration Broker Configuration
> (clustered=false,journalDirectory=/mnt/hudson_workspace/artemis-project-testsuite-rhel-master-local-discs/666ed8c2/tests/integration-tests/./target/tmp/junit3344164161239630016/journal,bindingsDirectory=/mnt/hudson_workspace/artemis-project-testsuite-rhel-master-local-discs/666ed8c2/tests/integration-tests/./target/tmp/junit3344164161239630016/bindings,largeMessagesDirectory=/mnt/hudson_workspace/artemis-project-testsuite-rhel-master-local-discs/666ed8c2/tests/integration-tests/./target/tmp/junit3344164161239630016/large-msg,pagingDirectory=/mnt/hudson_workspace/artemis-project-testsuite-rhel-master-local-discs/666ed8c2/tests/integration-tests/./target/tmp/junit3344164161239630016/page)
> 13:00:22,260 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-server]. Adding protocol support for: CORE
> 13:00:22,261 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-amqp-protocol]. Adding protocol support for:
> AMQP
> 13:00:22,261 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-stomp-protocol]. Adding protocol support for:
> STOMP
> 13:00:22,262 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-openwire-protocol]. Adding protocol support
> for: OPENWIRE
> 13:00:22,263 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
> for: HORNETQ
> 13:00:22,264 INFO [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-mqtt-protocol]. Adding protocol support for:
> MQTT
> 13:00:22,279 INFO [org.apache.activemq.artemis.core.server] AMQ221020:
> Started Acceptor at localhost:61616 for protocols
> [CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
> 13:00:22,279 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server
> is now live
> 13:00:22,279 INFO [org.apache.activemq.artemis.core.server] AMQ221001: Apache
> ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010
> [nodeID=048e5da0-b7c4-11e5-9b66-4f0c52a9abc9]
> 13:00:22,283 INFO [org.apache.activemq.artemis.tests.integration] Using
> suite: SSL_DHE_DSS_WITH_AES_128_CBC_SHA256
> 13:00:22,312 WARNING [io.netty.channel.DefaultChannelPipeline] An
> exceptionCaught() event was fired, and it reached at the tail of the
> pipeline. It usually means the last handler in the pipeline did not handle
> the exception.: io.netty.handler.codec.DecoderException:
> javax.net.ssl.SSLHandshakeException: no cipher suites in common
> at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:358)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:230)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
> [netty-all-4.0.30.Final.jar:4.0.30.Final]
> at
>
[jira] [Reopened] (ARTEMIS-1659) AMQ224000: Failure in initialisation: java.lang.IllegalStateException: java.lang.IllegalStateException: Cursor 28 had already been created
[
https://issues.apache.org/jira/browse/ARTEMIS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic reopened ARTEMIS-1659:
--
> AMQ224000: Failure in initialisation: java.lang.IllegalStateException:
> java.lang.IllegalStateException: Cursor 28 had already been created
> ---
>
> Key: ARTEMIS-1659
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1659
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.0.0
> Environment: Artemis 2
>Reporter: Tom Ross
>Assignee: Michael Andre Pearce
>Priority: Major
> Fix For: 2.5.0
>
>
> The following exception can be seen in the amq log file
> {noformat}
> 08:07:04,658 ERROR [org.apache.activemq.artemis.core.server] AMQ224000:
> Failure in initialisation: java.lang.IllegalStateException:
> java.lang.IllegalStateException: Cursor 28 had already been created
> at
> org.apache.activemq.artemis.core.server.QueueConfig$Builder.build(QueueConfig.java:151)
> [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at
> org.apache.activemq.artemis.core.server.impl.PostOfficeJournalLoader.initQueues(PostOfficeJournalLoader.java:154)
> [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:2481)
> [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:2258)
> [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at
> org.apache.activemq.artemis.core.server.impl.SharedNothingBackupActivation.run(SharedNothingBackupActivation.java:342)
> [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$ActivationThread.run(ActiveMQServerImpl.java:2866)
> [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> Caused by: java.lang.IllegalStateException: Cursor 28 had already been created
> at
> org.apache.activemq.artemis.core.paging.cursor.impl.PageCursorProviderImpl.createSubscription(PageCursorProviderImpl.java:100)
> [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> at
> org.apache.activemq.artemis.core.server.QueueConfig$Builder.build(QueueConfig.java:149)
> [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
