[jira] [Closed] (AMQ-7306) How to configure automatic cleaning strategy when ActiveMQ + zookeeper disk limit reaches its maximum
[ https://issues.apache.org/jira/browse/AMQ-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7306. - Resolution: Won't Fix The LevelDB store has been deprecated for several years now and will not receive any additional fixes, recommend moving to KahaDB store for stability. > How to configure automatic cleaning strategy when ActiveMQ + zookeeper disk > limit reaches its maximum > - > > Key: AMQ-7306 > URL: https://issues.apache.org/jira/browse/AMQ-7306 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-leveldb-store >Affects Versions: 5.15.0 >Reporter: liuhanjiang >Priority: Major > Attachments: activemq.xml > > > The largest < store Usage > configuration in persistence < system Usage > > > < / storeusage > > > When the maximum value is reached, the producer will be blocked. Why is there > no automatic cleaning strategy? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (AMQ-7304) Acitvemq is getting timed out for connecting to RHEL7.6 machine while its able to connect to RHEL7.5 machine
[ https://issues.apache.org/jira/browse/AMQ-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7304. - Resolution: Invalid This is most likely a configuration issue, please ask support questions on the users mailing list. http://activemq.apache.org/contact/#mailing > Acitvemq is getting timed out for connecting to RHEL7.6 machine while its > able to connect to RHEL7.5 machine > > > Key: AMQ-7304 > URL: https://issues.apache.org/jira/browse/AMQ-7304 > Project: ActiveMQ > Issue Type: New Feature >Reporter: rajiv devaraj >Priority: Blocker > > Server being interchanged with different operating system one of them able to > connect while other is getting timed out . > The machine which is getting time out in connecting to the server is RHEL7.6 > OS , while client machine can connect to the server when it is RHEL 7.5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (AMQ-7299) Using erlang and amqp protocol
[ https://issues.apache.org/jira/browse/AMQ-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7299. - Resolution: Invalid Please ask questions on the users mailing list, Jira is for bug reports https://activemq.apache.org/contact/#mailing > Using erlang and amqp protocol > -- > > Key: AMQ-7299 > URL: https://issues.apache.org/jira/browse/AMQ-7299 > Project: ActiveMQ > Issue Type: Wish > Components: AMQP >Reporter: Roman Hordovskyi >Priority: Major > > I'm currently using the RabbitMQ broker and have a plan to switch to > ActiveMQ. But I don't know how to figure out some functionality from > ActiveMQ. > For working with ActiveMQ I use this client > https://github.com/rabbitmq/rabbitmq-amqp1.0-client > Please tell me if there is an opportunity in ActiveMQ to set parameters or > their analogs that we use in RabbitMQ? > These are the parameters that I use in RabbitMQ when declaring the queue: > - exclusive (used by only one connection and the queue will be deleted when > that connection closes) > - auto-delete (queue that has had at least one consumer is deleted when the > last consumer unsubscribes) > - args: > * Queue TTL > * Queue length limit > Help me please or tell me where to turn with this request? -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (AMQ-7294) Can activeMQ be builded and tested sucessfullly in docker?
[ https://issues.apache.org/jira/browse/AMQ-7294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7294. - Resolution: Invalid Please ask questions on the users mailing list, Jira is where bug reports are made. https://activemq.apache.org/contact/#mailing > Can activeMQ be builded and tested sucessfullly in docker? > --- > > Key: AMQ-7294 > URL: https://issues.apache.org/jira/browse/AMQ-7294 > Project: ActiveMQ > Issue Type: Bug > Components: karaf >Affects Versions: 5.15.9 >Reporter: Chen >Priority: Major > > Can activeMQ be builded and tested sucessfullly in docker? -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (AMQ-7281) KahaDB Scheduler log files not being deleted
[
https://issues.apache.org/jira/browse/AMQ-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-7281:
--
Issue Type: New Feature (was: Bug)
> KahaDB Scheduler log files not being deleted
>
>
> Key: AMQ-7281
> URL: https://issues.apache.org/jira/browse/AMQ-7281
> Project: ActiveMQ
> Issue Type: New Feature
> Components: KahaDB
>Affects Versions: 5.15.4, 5.15.9
> Environment: RHEL 7.6 x86_64
> jdk1.8.0_172
>Reporter: Sergiy Dryga
>Priority: Minor
> Attachments: kahadb_log_1.txt, kahadb_scheduler.png,
> scheduler_log_1.txt
>
>
> Dear Support Team!
> I faced with a problem with KahaDB Scheduler, it doesn't delete old log
> files. It looks similar to previously reported issue AMQ-6152, see
> 'scheduler_log_1.txt'. But after testing I noticed that it's not the same
> problem, KahaDB Scheduler deletes not used files well.
> Investigation also showed that the most old file contains pending message,
> it's ok. But there are a lot of files without any panding messages. I assumed
> that it contains ACK and added enableAckCompaction="true" and
> compactAcksIgnoresStoreGrowth="true" to the config:
>
>directory="${activemq.data}/static-broker/kahadb"
> journalMaxFileLength="1mb"
> cleanupInterval="6"
> enableIndexWriteAsync="true"
> journalDiskSyncStrategy="never"
> enableAckCompaction="true"
> compactAcksIgnoresStoreGrowth="true"
> indexCacheSize="10"
> indexWriteBatchSize="5000"
> checkForCorruptJournalFiles="true"
> ignoreMissingJournalfiles="true" />
>
> And yes, it looks like KahaDB started to move ACK, see 'kahadb_log_1.txt'.
> But it doesn't work with KahaDB Scheduler, it's not possible to specify ACK
> compaction options in 'jobSchedulerStore' config section:
>
> http://www.springframework.org/schema/beans;
> id="jobSchedulerStore"
> class="org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl">
> />
>
>
>
> How is it possible to solve this problem?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (AMQ-7290) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
[ https://issues.apache.org/jira/browse/AMQ-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-7290. --- Resolution: Fixed > AMQP: Update Qpid JMS, Proton-J and Netty to latest releases > > > Key: AMQ-7290 > URL: https://issues.apache.org/jira/browse/AMQ-7290 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.10 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 5.15.11 > > > Update the AMQP dependencies for the project to latest release -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (AMQ-7290) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
Timothy Bish created AMQ-7290: - Summary: AMQP: Update Qpid JMS, Proton-J and Netty to latest releases Key: AMQ-7290 URL: https://issues.apache.org/jira/browse/AMQ-7290 Project: ActiveMQ Issue Type: Task Components: AMQP Affects Versions: 5.15.10 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 5.15.11 Update the AMQP dependencies for the project to latest release -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (AMQ-7281) KahaDB Scheduler log files not being deleted
[
https://issues.apache.org/jira/browse/AMQ-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-7281:
--
Issue Type: New Feature (was: Bug)
> KahaDB Scheduler log files not being deleted
>
>
> Key: AMQ-7281
> URL: https://issues.apache.org/jira/browse/AMQ-7281
> Project: ActiveMQ
> Issue Type: New Feature
> Components: KahaDB
>Affects Versions: 5.15.4, 5.15.9
> Environment: RHEL 7.6 x86_64
> jdk1.8.0_172
>Reporter: Sergiy Dryga
>Priority: Minor
> Attachments: kahadb_log_1.txt, scheduler_log_1.txt
>
>
> Dear Support Team!
> I faced with a problem with KahaDB Scheduler, it doesn't delete old log
> files. It looks similar to previously reported issue AMQ-6152, see
> 'scheduler_log_1.txt'. But after testing I noticed that it's not the same
> problem, KahaDB Scheduler deletes not used files well.
> Investigation also showed that the most old file contains pending message,
> it's ok. But there are a lot of files without any panding messages. I assumed
> that it contains ACK and added enableAckCompaction="true" and
> compactAcksIgnoresStoreGrowth="true" to the config:
>
>directory="${activemq.data}/static-broker/kahadb"
> journalMaxFileLength="1mb"
> cleanupInterval="6"
> enableIndexWriteAsync="true"
> journalDiskSyncStrategy="never"
> enableAckCompaction="true"
> compactAcksIgnoresStoreGrowth="true"
> indexCacheSize="10"
> indexWriteBatchSize="5000"
> checkForCorruptJournalFiles="true"
> ignoreMissingJournalfiles="true" />
>
> And yes, it looks like KahaDB started to move ACK, see 'kahadb_log_1.txt'.
> But it doesn't work with KahaDB Scheduler, it's not possible to specify ACK
> compaction options in 'jobSchedulerStore' config section:
>
> http://www.springframework.org/schema/beans;
> id="jobSchedulerStore"
> class="org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl">
> />
>
>
>
> How is it possible to solve this problem?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (AMQ-7281) KahaDB Scheduler log files not being deleted
[
https://issues.apache.org/jira/browse/AMQ-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912359#comment-16912359
]
Timothy Bish commented on AMQ-7281:
---
The scheduler doesn't support the ack compaction feature. You are welcome to
contribute to the project and enhance it to do so though as we love
contributions
> KahaDB Scheduler log files not being deleted
>
>
> Key: AMQ-7281
> URL: https://issues.apache.org/jira/browse/AMQ-7281
> Project: ActiveMQ
> Issue Type: New Feature
> Components: KahaDB
>Affects Versions: 5.15.4, 5.15.9
> Environment: RHEL 7.6 x86_64
> jdk1.8.0_172
>Reporter: Sergiy Dryga
>Priority: Minor
> Attachments: kahadb_log_1.txt, scheduler_log_1.txt
>
>
> Dear Support Team!
> I faced with a problem with KahaDB Scheduler, it doesn't delete old log
> files. It looks similar to previously reported issue AMQ-6152, see
> 'scheduler_log_1.txt'. But after testing I noticed that it's not the same
> problem, KahaDB Scheduler deletes not used files well.
> Investigation also showed that the most old file contains pending message,
> it's ok. But there are a lot of files without any panding messages. I assumed
> that it contains ACK and added enableAckCompaction="true" and
> compactAcksIgnoresStoreGrowth="true" to the config:
>
>directory="${activemq.data}/static-broker/kahadb"
> journalMaxFileLength="1mb"
> cleanupInterval="6"
> enableIndexWriteAsync="true"
> journalDiskSyncStrategy="never"
> enableAckCompaction="true"
> compactAcksIgnoresStoreGrowth="true"
> indexCacheSize="10"
> indexWriteBatchSize="5000"
> checkForCorruptJournalFiles="true"
> ignoreMissingJournalfiles="true" />
>
> And yes, it looks like KahaDB started to move ACK, see 'kahadb_log_1.txt'.
> But it doesn't work with KahaDB Scheduler, it's not possible to specify ACK
> compaction options in 'jobSchedulerStore' config section:
>
> http://www.springframework.org/schema/beans;
> id="jobSchedulerStore"
> class="org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl">
> />
>
>
>
> How is it possible to solve this problem?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (AMQ-7281) KahaDB Scheduler log files not being deleted
[
https://issues.apache.org/jira/browse/AMQ-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-7281:
--
Priority: Minor (was: Major)
> KahaDB Scheduler log files not being deleted
>
>
> Key: AMQ-7281
> URL: https://issues.apache.org/jira/browse/AMQ-7281
> Project: ActiveMQ
> Issue Type: Bug
> Components: KahaDB
>Affects Versions: 5.15.4, 5.15.9
> Environment: RHEL 7.6 x86_64
> jdk1.8.0_172
>Reporter: Sergiy Dryga
>Priority: Minor
> Attachments: kahadb_log_1.txt, scheduler_log_1.txt
>
>
> Dear Support Team!
> I faced with a problem with KahaDB Scheduler, it doesn't delete old log
> files. It looks similar to previously reported issue AMQ-6152, see
> 'scheduler_log_1.txt'. But after testing I noticed that it's not the same
> problem, KahaDB Scheduler deletes not used files well.
> Investigation also showed that the most old file contains pending message,
> it's ok. But there are a lot of files without any panding messages. I assumed
> that it contains ACK and added enableAckCompaction="true" and
> compactAcksIgnoresStoreGrowth="true" to the config:
>
>directory="${activemq.data}/static-broker/kahadb"
> journalMaxFileLength="1mb"
> cleanupInterval="6"
> enableIndexWriteAsync="true"
> journalDiskSyncStrategy="never"
> enableAckCompaction="true"
> compactAcksIgnoresStoreGrowth="true"
> indexCacheSize="10"
> indexWriteBatchSize="5000"
> checkForCorruptJournalFiles="true"
> ignoreMissingJournalfiles="true" />
>
> And yes, it looks like KahaDB started to move ACK, see 'kahadb_log_1.txt'.
> But it doesn't work with KahaDB Scheduler, it's not possible to specify ACK
> compaction options in 'jobSchedulerStore' config section:
>
> http://www.springframework.org/schema/beans;
> id="jobSchedulerStore"
> class="org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl">
> />
>
>
>
> How is it possible to solve this problem?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (ARTEMIS-2437) AMQP message conversion fails if annotations contain values outwith simple property types
[
https://issues.apache.org/jira/browse/ARTEMIS-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated ARTEMIS-2437:
--
Fix Version/s: 2.10.0
> AMQP message conversion fails if annotations contain values outwith simple
> property types
> -
>
> Key: ARTEMIS-2437
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2437
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.9.0
>Reporter: Jiri Daněk
>Assignee: Timothy Bish
>Priority: Major
> Fix For: 2.10.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> {noformat}
> $ bin/artemis browser --destination example
> Consumer:: filter = null
> Consumer ActiveMQQueue[example], thread=0 trying to browse 1000 messages
> [...]
> Consumer ActiveMQQueue[example], thread=0 browsing Alert!!!
> Consumer ActiveMQQueue[example], thread=0 browsed: 4 messages
> Consumer ActiveMQQueue[example], thread=0 Browser thread finished
> {noformat}
> In fact, there is 5 messages in the queue, and probably when browsing last
> one, the following error is printed to broker stdout.
> {noformat}
> 2019-07-31 15:07:30,742 ERROR [org.apache.activemq.artemis.core.server]
> AMQ224046: Exception while browser handled from
> Reference[627]:NON-RELIABLE:AMQPMessage [durable=false, messageID=627,
> address=example, size=121, applicationProperties=null,
> properties=Properties{messageId=null, userId=null, to='null', subject='null',
> replyTo='null', correlationId=null, contentType=null, contentEncoding=null,
> absoluteExpiryTime=null, creationTime=null, groupId='null',
> groupSequence=null, replyToGroupId='null'}, extraProperties =
> TypedProperties[_AMQ_AD=example]]: java.lang.RuntimeException: class
> java.util.LinkedHashMap is not a valid property type
> at
> org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage.toCore(AMQPMessage.java:695)
> [artemis-amqp-protocol-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.CoreSessionCallback.sendMessage(CoreSessionCallback.java:123)
> [artemis-server-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.deliverStandardMessage(ServerConsumerImpl.java:1168)
> [artemis-server-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:510)
> [artemis-server-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl$BrowserDeliverer.run(ServerConsumerImpl.java:1484)
> [artemis-server-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> [artemis-commons-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> [artemis-commons-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> [artemis-commons-2.9.0.jar:2.9.0]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_212]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_212]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.9.0.jar:2.9.0]
> Caused by:
> org.apache.activemq.artemis.api.core.ActiveMQPropertyConversionException:
> class java.util.LinkedHashMap is not a valid property type
> at
> org.apache.activemq.artemis.utils.collections.TypedProperties.setObjectProperty(TypedProperties.java:1112)
> [artemis-commons-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.putObjectProperty(CoreMessage.java:1014)
> [artemis-core-client-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.putObjectProperty(CoreMessage.java:1030)
> [artemis-core-client-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.putObjectProperty(CoreMessage.java:53)
> [artemis-core-client-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.reader.MessageUtil.setObjectProperty(MessageUtil.java:262)
> [artemis-core-client-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.jms.ServerJMSMessage.setObjectProperty(ServerJMSMessage.java:345)
> [artemis-amqp-protocol-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.AmqpCoreConverter.setProperty(AmqpCoreConverter.java:441)
> [artemis-amqp-protocol-2.9.0.jar:2.9.0]
> at
>
[jira] [Resolved] (ARTEMIS-2437) AMQP message conversion fails if annotations contain values outwith simple property types
[
https://issues.apache.org/jira/browse/ARTEMIS-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved ARTEMIS-2437.
---
Resolution: Fixed
This should now be fixed on master
> AMQP message conversion fails if annotations contain values outwith simple
> property types
> -
>
> Key: ARTEMIS-2437
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2437
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.9.0
>Reporter: Jiri Daněk
>Assignee: Timothy Bish
>Priority: Major
> Time Spent: 2h
> Remaining Estimate: 0h
>
> {noformat}
> $ bin/artemis browser --destination example
> Consumer:: filter = null
> Consumer ActiveMQQueue[example], thread=0 trying to browse 1000 messages
> [...]
> Consumer ActiveMQQueue[example], thread=0 browsing Alert!!!
> Consumer ActiveMQQueue[example], thread=0 browsed: 4 messages
> Consumer ActiveMQQueue[example], thread=0 Browser thread finished
> {noformat}
> In fact, there is 5 messages in the queue, and probably when browsing last
> one, the following error is printed to broker stdout.
> {noformat}
> 2019-07-31 15:07:30,742 ERROR [org.apache.activemq.artemis.core.server]
> AMQ224046: Exception while browser handled from
> Reference[627]:NON-RELIABLE:AMQPMessage [durable=false, messageID=627,
> address=example, size=121, applicationProperties=null,
> properties=Properties{messageId=null, userId=null, to='null', subject='null',
> replyTo='null', correlationId=null, contentType=null, contentEncoding=null,
> absoluteExpiryTime=null, creationTime=null, groupId='null',
> groupSequence=null, replyToGroupId='null'}, extraProperties =
> TypedProperties[_AMQ_AD=example]]: java.lang.RuntimeException: class
> java.util.LinkedHashMap is not a valid property type
> at
> org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage.toCore(AMQPMessage.java:695)
> [artemis-amqp-protocol-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.protocol.core.impl.CoreSessionCallback.sendMessage(CoreSessionCallback.java:123)
> [artemis-server-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.deliverStandardMessage(ServerConsumerImpl.java:1168)
> [artemis-server-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:510)
> [artemis-server-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl$BrowserDeliverer.run(ServerConsumerImpl.java:1484)
> [artemis-server-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> [artemis-commons-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> [artemis-commons-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> [artemis-commons-2.9.0.jar:2.9.0]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_212]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_212]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.9.0.jar:2.9.0]
> Caused by:
> org.apache.activemq.artemis.api.core.ActiveMQPropertyConversionException:
> class java.util.LinkedHashMap is not a valid property type
> at
> org.apache.activemq.artemis.utils.collections.TypedProperties.setObjectProperty(TypedProperties.java:1112)
> [artemis-commons-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.putObjectProperty(CoreMessage.java:1014)
> [artemis-core-client-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.putObjectProperty(CoreMessage.java:1030)
> [artemis-core-client-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.core.message.impl.CoreMessage.putObjectProperty(CoreMessage.java:53)
> [artemis-core-client-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.reader.MessageUtil.setObjectProperty(MessageUtil.java:262)
> [artemis-core-client-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.jms.ServerJMSMessage.setObjectProperty(ServerJMSMessage.java:345)
> [artemis-amqp-protocol-2.9.0.jar:2.9.0]
> at
> org.apache.activemq.artemis.protocol.amqp.converter.AmqpCoreConverter.setProperty(AmqpCoreConverter.java:441)
> [artemis-amqp-protocol-2.9.0.jar:2.9.0]
> at
>
[jira] [Commented] (AMQ-7276) Unable to establish mutual authentication through HTTPS transport
[
https://issues.apache.org/jira/browse/AMQ-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908204#comment-16908204
]
Timothy Bish commented on AMQ-7276:
---
5.11.0 is not a supported release so first thing to do is upgrade your broker
to the latest 5.15.9 and try from there.
> Unable to establish mutual authentication through HTTPS transport
> -
>
> Key: AMQ-7276
> URL: https://issues.apache.org/jira/browse/AMQ-7276
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.11.0
>Reporter: Diptesh Chakraborty
>Priority: Major
> Labels: mutualSSL
>
> I am trying to establish mutual authentication over HTTPS transport but found
> that only the one way authentication is established.
> Below is my code snippet:
>
> +*Client Java Program:*+
> {code:java}
> System.setProperty("javax.net.ssl.keyStore",
> "D://project//test//POC//client.ks");
> System.setProperty("javax.net.ssl.keyStorePassword", "password");
> System.setProperty("javax.net.ssl.trustStore",
> "D://project//test//POC//client.ts");
> System.setProperty("javax.net.ssl.trustStorePassword", "password");
> cf=new ActiveMQConnectionFactory("https://localhost:8443;);
> con=cf.createConnection();
> Session s=con.createSession(false,Session.AUTO_ACKNOWLEDGE);
> Destination d;
> d=s.createQueue("TestQueue");
> MessageProducer mp;
> mp=s.createProducer(d);
> con.start();
> // prepare the message
> mp.send(message){code}
> +*Active MQ configuration*+
>
> {code:java}
> uri="https://localhost:8443?transport.needClientAuth=true"/>
>
> keyStorePassword="password"
> trustStore="file:D:/project/test/POC/broker.ts"
> trustStorePassword="password"/>
> {code}
>
> While running the program, the message is being sent successfully but I am
> not finding any difference in the logs if "*needClientAuth*" is set to
> *false*.
> If the transport connector is changed from https to ssl, I can view the
> detailed ssl handshake logs which implies that "Mutual Authentication" has
> been established
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (AMQ-7276) Unable to establish mutual authentication through HTTPS transport
[
https://issues.apache.org/jira/browse/AMQ-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-7276:
--
Priority: Major (was: Critical)
> Unable to establish mutual authentication through HTTPS transport
> -
>
> Key: AMQ-7276
> URL: https://issues.apache.org/jira/browse/AMQ-7276
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.11.0
>Reporter: Diptesh Chakraborty
>Priority: Major
> Labels: mutualSSL
>
> I am trying to establish mutual authentication over HTTPS transport but found
> that only the one way authentication is established.
> Below is my code snippet:
>
> +*Client Java Program:*+
> {code:java}
> System.setProperty("javax.net.ssl.keyStore",
> "D://project//test//POC//client.ks");
> System.setProperty("javax.net.ssl.keyStorePassword", "password");
> System.setProperty("javax.net.ssl.trustStore",
> "D://project//test//POC//client.ts");
> System.setProperty("javax.net.ssl.trustStorePassword", "password");
> cf=new ActiveMQConnectionFactory("https://localhost:8443;);
> con=cf.createConnection();
> Session s=con.createSession(false,Session.AUTO_ACKNOWLEDGE);
> Destination d;
> d=s.createQueue("TestQueue");
> MessageProducer mp;
> mp=s.createProducer(d);
> con.start();
> // prepare the message
> mp.send(message){code}
> +*Active MQ configuration*+
>
> {code:java}
> uri="https://localhost:8443?transport.needClientAuth=true"/>
>
> keyStorePassword="password"
> trustStore="file:D:/project/test/POC/broker.ts"
> trustStorePassword="password"/>
> {code}
>
> While running the program, the message is being sent successfully but I am
> not finding any difference in the logs if "*needClientAuth*" is set to
> *false*.
> If the transport connector is changed from https to ssl, I can view the
> detailed ssl handshake logs which implies that "Mutual Authentication" has
> been established
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (AMQ-7274) Update to proton-j 0.33.2 and fix type used to recreate message Footer map
[ https://issues.apache.org/jira/browse/AMQ-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-7274. --- Resolution: Fixed > Update to proton-j 0.33.2 and fix type used to recreate message Footer map > -- > > Key: AMQ-7274 > URL: https://issues.apache.org/jira/browse/AMQ-7274 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.9 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 5.15.10 > > > Update to latest proton-j release to fix issue with encoding annotations with > embedded maps or other complex AMQP types and fix issue of using string key > in footer annotations map when converting back to an AMQP message. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (AMQ-7274) Update to proton-j 0.33.2 and fix type used to recreate message Footer map
Timothy Bish created AMQ-7274: - Summary: Update to proton-j 0.33.2 and fix type used to recreate message Footer map Key: AMQ-7274 URL: https://issues.apache.org/jira/browse/AMQ-7274 Project: ActiveMQ Issue Type: Task Components: AMQP Affects Versions: 5.15.9 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 5.15.10 Update to latest proton-j release to fix issue with encoding annotations with embedded maps or other complex AMQP types and fix issue of using string key in footer annotations map when converting back to an AMQP message. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (AMQ-7269) how to create duplicate queue in activemq 5.4.3 and please explain step by step in comments
[ https://issues.apache.org/jira/browse/AMQ-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7269. - Resolution: Invalid Please ask support questions on the users mailing list. > how to create duplicate queue in activemq 5.4.3 and please explain step by > step in comments > --- > > Key: AMQ-7269 > URL: https://issues.apache.org/jira/browse/AMQ-7269 > Project: ActiveMQ > Issue Type: Bug >Reporter: jyothikumar >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (AMQ-7256) ActiveMQ - dequeue not happening causing pile up messages
[ https://issues.apache.org/jira/browse/AMQ-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7256. - Resolution: Incomplete No information given to point to a specific problem > ActiveMQ - dequeue not happening causing pile up messages > - > > Key: AMQ-7256 > URL: https://issues.apache.org/jira/browse/AMQ-7256 > Project: ActiveMQ > Issue Type: Bug >Reporter: Niraj >Priority: Major > > Message are not de-queueing from activeMQ. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (AMQ-7255) Kahadb log datastore not cleaning up
[ https://issues.apache.org/jira/browse/AMQ-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7255. - Resolution: Invalid 5.8.0 is not a supported version so you'd need to upgrade to latest 5.15.9 release to validate issues still exist. For questions and support please consult the users mailing list. > Kahadb log datastore not cleaning up > > > Key: AMQ-7255 > URL: https://issues.apache.org/jira/browse/AMQ-7255 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.8.0 > Environment: [link title|http://example.com] >Reporter: Shane >Priority: Major > Attachments: activemq.jpg, activemq_log.jpg > > > Experienced an outage where kahadb datastore keeps growing. This stops > messages from being put on queues causing the downstream processes to be > waiting for incoming messages. > Need to understand > 1) if kahadb datastore has an issue with this clearing out logs on 5.8? > 2) Should the Kahadb datastore be cleared after a restart? We performed > several restarts and kahadb kept growing. > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (ARTEMIS-2431) [AMQP] Broker does not send security errors for unauthorized anonymous sasl with pipelined open
[
https://issues.apache.org/jira/browse/ARTEMIS-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893047#comment-16893047
]
Timothy Bish commented on ARTEMIS-2431:
---
There's seems to be a few issues at play in the Artemis code around processing
SASL exchanges. It appears that the broker is advertising ANONYMOUS as an
allowed mechanism even though an anonymous login isn't supported by the
security configuration. It further appears that even if the broker were to not
advertise the anonymous SASL mechanism it wouldn't end processing on the
connection following the failure of the SASL exchange if it were to shovel in
this same sequence of frames as Jiri's test is doing and would fail later on
the Attach processing. And finally in my poking around in the code it seems as
though even if you hard code (or configured via the accepter params) the broker
SASL mechanisms to offer none at all it would fallback into a case in the code
where it allowed the incoming anonymous mechanism and then later failed on the
session attach. So it seems like some overhaul of the SASL processing needs to
be done to handle these cases correctly and not process any pipelined data that
follows the SASL bits when authentication should be failing.
> [AMQP] Broker does not send security errors for unauthorized anonymous sasl
> with pipelined open
> ---
>
> Key: ARTEMIS-2431
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2431
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.9.0
>Reporter: Jiri Daněk
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> If a client sends open, begin and attach frames all at once, then the issue
> ARTEMIS-2344 still manifests itself. Sending the initial frames all at once
> is known as the pipelined open,
> http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#doc-idp157520
> and one client that does this is qpid-proton-cpp.
> {noformat}
> $ PN_TRACE_FRM=1 ./target/bin/aac3_sender -b "localhost:34949/examples"
> --log-msgs dict -c 1
> [0x9ea9d0]: -> SASL
> [0x9ea9d0]: <- SASL
> [0x9ea9d0]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:PLAIN, :ANONYMOUS]]
> [0x9ea9d0]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"anonymous@nixos"]
> [0x9ea9d0]:0 <- @sasl-outcome(68) [code=0]
> [0x9ea9d0]: -> AMQP
> [0x9ea9d0]:0 -> @open(16)
> [container-id="204c1d45-9c47-402d-809f-7d17a4d97d6e", hostname="localhost",
> channel-max=32767]
> [0x9ea9d0]:0 -> @begin(17) [next-outgoing-id=0, incoming-window=2147483647,
> outgoing-window=2147483647]
> [0x9ea9d0]:0 -> @attach(18) [name="2b46ad5b-834b-454e-a2f7-2e5e0e324e21",
> handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [durable=0, timeout=0, dynamic=false], target=@target(41)
> [address="examples", durable=0, timeout=0, dynamic=false],
> initial-delivery-count=0, max-message-size=0]
> [0x9ea9d0]: <- AMQP
> [0x9ea9d0]:0 <- @open(16) [container-id="localhost", max-frame-size=131072,
> channel-max=65535, idle-time-out=3,
> offered-capabilities=@PN_SYMBOL[:"sole-connection-for-container",
> :"DELAYED_DELIVERY", :"SHARED-SUBS", :"ANONYMOUS-RELAY"],
> properties={:product="apache-activemq-artemis", :version="2.9.0"}]
> [0x9ea9d0]:0 <- @close(24) [error=@error(29)
> [condition=:"amqp:internal-error", description="Unrecoverable error:
> NullPointerException"]]
> [0x9ea9d0]: <- EOS
> [error]: Failed to connect to localhost:34949
> [0x9ea9d0]:0 -> @close(24) []
> [0x9ea9d0]: -> EOS
> {noformat}
> The broker side then looks like this
> {noformat}
> DEBUG - -Dio.netty.recycler.maxCapacityPerThread: 4096
> DEBUG - -Dio.netty.recycler.maxSharedCapacityFactor: 2
> DEBUG - -Dio.netty.recycler.linkCapacity: 16
> DEBUG - -Dio.netty.recycler.ratio: 8
> DEBUG - onSaslInit: SaslImpl [_outcome=PN_SASL_NONE, state=PN_SASL_STEP,
> done=false, role=SERVER]
> DEBUG - saslComplete: SaslImpl [_outcome=PN_SASL_NONE, state=PN_SASL_STEP,
> done=false, role=SERVER]
> DEBUG - using hardware address 2:42:ffbb:ffa4:4d:-110
> INFO - AMQ601267: User anonymous is creating a core session on target
> resource ActiveMQServerImpl::serverUUID=85b3269d-8773-11e9-8808-c0b6f9980288
> [with parameters: [dbdce52b-ae0f-11e9-8b93-0242bba44d92, null, , 102400,
> org.apache.activemq.artemis.protocol.amqp.broker.ActiveMQProtonRemotingConnection@26c5379b,
> false, false, false, true, null,
> org.apache.activemq.artemis.protocol.amqp.broker.AMQPSessionCallback@673826ee,
> true, OperationContextImpl [834445691] [minimalStore=9223372036854775807,
> storeLineUp=0, stored=0, minimalReplicated=9223372036854775807,
> replicationLineUp=0, replicated=0, paged=0,
[jira] [Closed] (AMQ-7251) Application is not complaining any errors while ActiveMQ is not running
[ https://issues.apache.org/jira/browse/AMQ-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7251. - Resolution: Invalid Support questions should be asked on the ActiveMQ Users mailing list, although in this instance to get help with SJMS2 I'd also suggest turning to the Camel Mailing lists. > Application is not complaining any errors while ActiveMQ is not running > --- > > Key: AMQ-7251 > URL: https://issues.apache.org/jira/browse/AMQ-7251 > Project: ActiveMQ > Issue Type: Bug >Reporter: Surendra Kumar Chandolu >Priority: Major > > I'm using SJMS2 configuration for my ActiveMQ in my Application. I just > stopped my ActiveMQ which is already running and then started my application. > But my Application is not saying anything about the connection issues to > ActiveMQ. > > When I'm using Activemq configuration then it is returning some error message > saying Connection could not started. > Could you please help me on this "sjms2" component? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (AMQ-7248) Is it required to set the TimeToLive and Redelivery Policies for ActiveMQ Topics?
[ https://issues.apache.org/jira/browse/AMQ-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7248. - Resolution: Invalid Please ask support type questions on the users mailing list, Jira is where bugs are reported. https://activemq.apache.org/contact/ > Is it required to set the TimeToLive and Redelivery Policies for ActiveMQ > Topics? > - > > Key: AMQ-7248 > URL: https://issues.apache.org/jira/browse/AMQ-7248 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-camel >Affects Versions: 5.15.8 >Reporter: Surendra Kumar Chandolu >Priority: Major > > I'm implementing AMQ topics for my Inbound and Outbound configurations and I > would like to know more about the parameters like TimToLive and Redelivery > Policies of topic. > Is this really required to set these paramters separatly to the topic? > 1) If yes, then what is the use of durable-subscribers? > 2) If no, then what are the default parameter values for Topic and when the > message will expires in Topic? > > I'm using apache-activemq-5.15.8 for our implementations. > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-7246: -- Priority: Major (was: Critical) > Having a JMX counter for delayed messages > - > > Key: AMQ-7246 > URL: https://issues.apache.org/jira/browse/AMQ-7246 > Project: ActiveMQ > Issue Type: Improvement > Components: JMX >Affects Versions: 5.15.6 >Reporter: François Courtault >Priority: Major > > As of today there is no easy way to monitor the number of delayed messages. > One possibility is to use the getAllJobs() operation on JobScheduler MBean. > But we have to specify a timeframe so it's quite difficult to use. > Instead, could we have a new JMX counter which provides the number of delayed > messages ? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (AMQ-7240) Large Number of ActiveMQ Connection Executor Threads on client
[ https://issues.apache.org/jira/browse/AMQ-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7240. - Resolution: Invalid This doesn't appear to be a bug but a normal consequence of using JMSTemplate without a pooling solution: Refer to https://activemq.apache.org/jmstemplate-gotchas > Large Number of ActiveMQ Connection Executor Threads on client > -- > > Key: AMQ-7240 > URL: https://issues.apache.org/jira/browse/AMQ-7240 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.15.8 >Reporter: Sumit Bhardwaj >Priority: Major > > We are using ActiveMQ version 5.15.8, We are connecting to it using Spring > JMSTemplate. What we are seeing is in case of connection errors too many of > following threads get created > > "ActiveMQ Connection Executor.." > > In one instance around 1250 Threads for the above were active in our tomcat > hosting our web application, when maxConnections setting on activeMQ was > 1000. > > The behaviour is similar to the following defect > https://issues.apache.org/jira/browse/AMQ-6700 > which was fixed in 5.14.6, but we are seeing in 5.15.8 as well. > > Spring Version: 5.0.6.RELEASE > ActiveMQ Version 5.1.5.8 > > Spring Configuration > > > > > > > > > > > class="org.apache.activemq.ActiveMQConnectionFactory"> > > > > > > > > Is there any workaround for this bug? Or do we need to change any > configuration? > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (AMQ-7179) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
[ https://issues.apache.org/jira/browse/AMQ-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-7179. --- Resolution: Fixed > AMQP: Update Qpid JMS, Proton-J and Netty to latest releases > > > Key: AMQ-7179 > URL: https://issues.apache.org/jira/browse/AMQ-7179 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.9 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 5.15.10 > > > Update to version 0.43.0 of Qpid JMS and 0.33.1 of proton-j as well as > updating to matched Netty version for Qpid JMS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMQ-7179) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
[ https://issues.apache.org/jira/browse/AMQ-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQ-7179: - Assignee: Timothy Bish (was: Robbie Gemmell) > AMQP: Update Qpid JMS, Proton-J and Netty to latest releases > > > Key: AMQ-7179 > URL: https://issues.apache.org/jira/browse/AMQ-7179 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.9 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 5.15.10 > > > Update to version 0.43.0 of Qpid JMS and 0.33.1 of proton-j as well as > updating to matched Netty version for Qpid JMS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMQ-7179) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
[ https://issues.apache.org/jira/browse/AMQ-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened AMQ-7179: --- > AMQP: Update Qpid JMS, Proton-J and Netty to latest releases > > > Key: AMQ-7179 > URL: https://issues.apache.org/jira/browse/AMQ-7179 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.9 >Reporter: Timothy Bish >Assignee: Robbie Gemmell >Priority: Major > Fix For: 5.15.10 > > > Update to version 0.42.0 of Qpid JMS and 0.33.0 of proton-j as well as > updating to matched Netty version for Qpid JMS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7179) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
[ https://issues.apache.org/jira/browse/AMQ-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-7179: -- Description: Update to version 0.43.0 of Qpid JMS and 0.33.1 of proton-j as well as updating to matched Netty version for Qpid JMS (was: Update to version 0.42.0 of Qpid JMS and 0.33.0 of proton-j as well as updating to matched Netty version for Qpid JMS) > AMQP: Update Qpid JMS, Proton-J and Netty to latest releases > > > Key: AMQ-7179 > URL: https://issues.apache.org/jira/browse/AMQ-7179 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.9 >Reporter: Timothy Bish >Assignee: Robbie Gemmell >Priority: Major > Fix For: 5.15.10 > > > Update to version 0.43.0 of Qpid JMS and 0.33.1 of proton-j as well as > updating to matched Netty version for Qpid JMS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7224) apache-activemq with Java 7
[ https://issues.apache.org/jira/browse/AMQ-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7224. - Resolution: Invalid As noted in AMQ-7223 Jira is not the place to as questions, the users mailing list is the place to ask for help. http://activemq.apache.org/contact/#mailing > apache-activemq with Java 7 > --- > > Key: AMQ-7224 > URL: https://issues.apache.org/jira/browse/AMQ-7224 > Project: ActiveMQ > Issue Type: Bug > Environment: Testing/Development >Reporter: Abhijit Vikash >Priority: Major > > Please let know which - latest Apache AMQ version should be installed with > Java 1.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARTEMIS-2367) Test Data dir bening created outside the target dir in artemis-server
Timothy Bish created ARTEMIS-2367: - Summary: Test Data dir bening created outside the target dir in artemis-server Key: ARTEMIS-2367 URL: https://issues.apache.org/jira/browse/ARTEMIS-2367 Project: ActiveMQ Artemis Issue Type: Task Components: Broker Affects Versions: 2.9.0, 2.8.1 Reporter: Timothy Bish Fix For: 2.10.0 The tests in artemis-server (possibly others) creates a data dir outside the target dir which then excludes it from being cleaned by mvn clean and as such can result in the test data being packaged up in releases etc which shouldn't be happening. The tests should ideally not be doing this, or if they must the clean plugin should be configured to remove that dir. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7220) Docker container having ActiveMQ restart making Queues Tab on Console inaccessible
[ https://issues.apache.org/jira/browse/AMQ-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7220. - Resolution: Invalid Please ask support questions on the users mailing list > Docker container having ActiveMQ restart making Queues Tab on Console > inaccessible > -- > > Key: AMQ-7220 > URL: https://issues.apache.org/jira/browse/AMQ-7220 > Project: ActiveMQ > Issue Type: Bug > Components: webconsole >Affects Versions: 5.14.3 > Environment: Docker >Reporter: Rahul Kalkar >Priority: Blocker > Fix For: 5.14.3 > > > In my project we have ActiveMQ 5.14.3 embedded withing docker image. > After initial deployment ActiveMQ Web console work fine, however when I > restart container Queues Tab in Web Console throwing JSP exception on > Queues.jsp line 59. Hence unable to access queue details from Web Console. > If I delete 'data' folder within container then restart container, Web > Console Queue Tab is working fine. But deleting 'data' folder is not good > option as I loose all previous data. > Can you please help on issue? > Active MQ version: 5.14.3 > Java version: 8 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMQ-7218) STOMP: V1.2 client that acks inside a TX can lose ability to ack after TX abort
[ https://issues.apache.org/jira/browse/AMQ-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-7218. --- Resolution: Fixed > STOMP: V1.2 client that acks inside a TX can lose ability to ack after TX > abort > --- > > Key: AMQ-7218 > URL: https://issues.apache.org/jira/browse/AMQ-7218 > Project: ActiveMQ > Issue Type: Bug > Components: stomp >Affects Versions: 5.15.9 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 5.16.0, 5.15.10 > > > When acknowledgement occurs inside a transaction it is valid for the TX to be > aborted and the messages to be acknowledged a second time in a new TX or on > their own. The broker currently loses track of the acks that are removed > from the pending Acks index as it doesn't recover them on abort and > repopulate the pending index. > There is also a race that occurs on dispatch and ack that allows for loss of > ack Ids as the current code clears the full pending index on either boundary > when it should only be removing the involved transactionally enlisted > messages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7218) STOMP: V1.2 client that acks inside a TX can lose ability to ack after TX abort
[ https://issues.apache.org/jira/browse/AMQ-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-7218: -- Fix Version/s: 5.15.10 > STOMP: V1.2 client that acks inside a TX can lose ability to ack after TX > abort > --- > > Key: AMQ-7218 > URL: https://issues.apache.org/jira/browse/AMQ-7218 > Project: ActiveMQ > Issue Type: Bug > Components: stomp >Affects Versions: 5.15.9 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 5.16.0, 5.15.10 > > > When acknowledgement occurs inside a transaction it is valid for the TX to be > aborted and the messages to be acknowledged a second time in a new TX or on > their own. The broker currently loses track of the acks that are removed > from the pending Acks index as it doesn't recover them on abort and > repopulate the pending index. > There is also a race that occurs on dispatch and ack that allows for loss of > ack Ids as the current code clears the full pending index on either boundary > when it should only be removing the involved transactionally enlisted > messages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7211) Pending ACKs errantly being cleared on STOMP transaction COMMIT/ABORT
[
https://issues.apache.org/jira/browse/AMQ-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851314#comment-16851314
]
Timothy Bish commented on AMQ-7211:
---
This will be addressed along with fixes for TX abort losing track of Ack Ids
for messages still enlisted in the TX in commit:
https://gitbox.apache.org/repos/asf?p=activemq.git;a=commit;h=063d24e6d653bed3dd3c56302758de29143e5e82
> Pending ACKs errantly being cleared on STOMP transaction COMMIT/ABORT
> -
>
> Key: AMQ-7211
> URL: https://issues.apache.org/jira/browse/AMQ-7211
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
>Affects Versions: 5.15.6
>Reporter: Borgstrom
>Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Given a queue with many messages in it, and a client that is creating
> transactions for each message it is processing will lead to the following
> error:
> org.apache.activemq.transport.stomp.ProtocolException: Unexpected ACK
> received for message-id [null]\n\tat
> org.apache.activemq.transport.stomp.ProtocolConverter.onStompAck(ProtocolConverter.java:476)\n\tat
>
> org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommand(ProtocolConverter.java:251)\n\tat
>
> org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:85)\n\tat
>
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)\n\tat
>
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:233)\n\tat
>
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)\n\tat
> java.lang.Thread.run(Thread.java:748)\n
> The client has a prefetch value of 1.
> Here is the debug logs from my client showing frames sent & received. We end
> up processing a number of messages, but eventually this happens:
> {noformat}
> DEBU[0119] Read frame body="[123 34 101
> 110 118 101 108 111 112 101 34 58 123 34 101 120 99 104 97 110 103 101 73 100
> 34 58 34 89 65 75 95 72 69 65 82 84 66 69 65 84 34 44 34 117 110 116 114 117
> 115 116 101 100 95 115 111 117 114 99 101 34 58 102 97 108 115 101 44 34 105
> 100 34 58 34 56 50 49 53 52 100 98 55 45 102 102 53 99 45 52 98 57 49 45 98
> 52 98 52 45 101 57 49 52 54 54 99 52 100 50 54 102 34 44 34 109 101 115 115
> 97 103 101 95 116 105 109 101 115 116 97 109 112 34 58 49 53 53 56 49 50 52
> 57 57 54 57 49 51 125 44 34 112 97 121 108 111 97 100 34 58 123 34 120 34 58
> 51 55 44 34 98 121 116 101 115 34 58 34 120 108 52 61 34 125 44 34 97 99 116
> 105 111 110 34 58 34 119 111 114 107 34 125]" command=MESSAGE
> header="map[ack:ID\\c6e56db7da800-41539-1558117094401-130\\c12
> content-type:application/json destination:/queue/YAK_HEARTBEAT-YAK_HEARTBEAT
> expires:0
> message-id:ID\\c6e56db7da800-41539-1558117094401-5\\c68\\c-1\\c1\\c538
> persistent:true priority:4 subscription:1E81E7A4F3D6C40314373C0F20B9F1AF
> timestamp:1558124997013]"
> DEBU[0119] Writing frame body="[]"
> command=BEGIN header="map[transaction:55CE4B41F0CF0C86C0D95EA9C7182A26]"
> DEBU[0119] Writing frame body="[]"
> command=ACK header="map[id:ID\\c6e56db7da800-41539-1558117094401-130\\c12
> transaction:55CE4B41F0CF0C86C0D95EA9C7182A26]"
> DEBU[0119] Writing frame body="[]"
> command=COMMIT header="map[transaction:55CE4B41F0CF0C86C0D95EA9C7182A26]"
> DEBU[0119] Read frame body="[123 34 101
> 110 118 101 108 111 112 101 34 58 123 34 101 120 99 104 97 110 103 101 73 100
> 34 58 34 89 65 75 95 72 69 65 82 84 66 69 65 84 34 44 34 117 110 116 114 117
> 115 116 101 100 95 115 111 117 114 99 101 34 58 102 97 108 115 101 44 34 105
> 100 34 58 34 101 100 49 51 56 51 53 101 45 56 98 50 98 45 52 98 100 101 45 97
> 52 99 50 45 102 51 50 49 98 49 54 99 50 51 57 57 34 44 34 109 101 115 115 97
> 103 101 95 116 105 109 101 115 116 97 109 112 34 58 49 53 53 56 49 50 52 57
> 57 54 57 49 51 125 44 34 112 97 121 108 111 97 100 34 58 123 34 120 34 58 51
> 56 44 34 98 121 116 101 115 34 58 34 52 103 61 61 34 125 44 34 97 99 116 105
> 111 110 34 58 34 119 111 114 107 34 125]" command=MESSAGE
> header="map[ack:ID\\c6e56db7da800-41539-1558117094401-130\\c13
> content-type:application/json destination:/queue/YAK_HEARTBEAT-YAK_HEARTBEAT
> expires:0
> message-id:ID\\c6e56db7da800-41539-1558117094401-5\\c68\\c-1\\c1\\c539
> persistent:true priority:4 subscription:1E81E7A4F3D6C40314373C0F20B9F1AF
> timestamp:1558124997017]"
> DEBU[0119] Writing frame body="[]"
> command=BEGIN header="map[transaction:0082C668C3243EDBA05FE48D25728979]"
> DEBU[0119] Writing frame body="[]"
>
[jira] [Created] (AMQ-7218) STOMP: V1.2 client that acks inside a TX can lose ability to ack after TX abort
Timothy Bish created AMQ-7218: - Summary: STOMP: V1.2 client that acks inside a TX can lose ability to ack after TX abort Key: AMQ-7218 URL: https://issues.apache.org/jira/browse/AMQ-7218 Project: ActiveMQ Issue Type: Bug Components: stomp Affects Versions: 5.15.9 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 5.16.0 When acknowledgement occurs inside a transaction it is valid for the TX to be aborted and the messages to be acknowledged a second time in a new TX or on their own. The broker currently loses track of the acks that are removed from the pending Acks index as it doesn't recover them on abort and repopulate the pending index. There is also a race that occurs on dispatch and ack that allows for loss of ack Ids as the current code clears the full pending index on either boundary when it should only be removing the involved transactionally enlisted messages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7210) AMQ slows down due to high number of stale ActiveMQ Connection Executor threads
[ https://issues.apache.org/jira/browse/AMQ-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16842425#comment-16842425 ] Timothy Bish commented on AMQ-7210: --- Have you closed the connections you created to communicate with that broker you keep restarting? > AMQ slows down due to high number of stale ActiveMQ Connection Executor > threads > --- > > Key: AMQ-7210 > URL: https://issues.apache.org/jira/browse/AMQ-7210 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.15.9 >Reporter: Sahil Patayar >Priority: Critical > Attachments: ActiveMQ_Connector_Executor_threads.JPG, > executor_threads_comparison_from_different_thread_dumps.txt > > > We have an enterprise application, and we are using embedded ActiveMQ. > We are currently using 5.15.2 version. We tried the latest(5.15.9) version, > but the issue still persists. > ActiveMQ Connector Executor threads are being created in ActiveMQConnection > class. > > ActiveMQ Connection Executor threads are not going away even after restarting > the broker programmatically. Threads keep increasing and after bouncing the > Broker, they don't go away. > > Steps to reproduce: > 1. Run load test on ActiveMQ. > 2. Take thread dumps > 3. Stop the Broker multiple times > 4. Take thread dumps again. > Result: Compare the thread dumps, executor threads from the previous dump > will be present in all next dumps. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARTEMIS-2344) [AMQP] Broker does not send security errors for unauthorized anonymous sasl
[
https://issues.apache.org/jira/browse/ARTEMIS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated ARTEMIS-2344:
--
Affects Version/s: (was: 2.9.0)
2.8.0
2.8.1
> [AMQP] Broker does not send security errors for unauthorized anonymous sasl
> ---
>
> Key: ARTEMIS-2344
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2344
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.8.0, 2.8.1
>Reporter: Domenico Bruscino
>Priority: Major
>
> When user attempts unauthorized anonymous sasl, using AMQP protocol, the
> broker can return an internal error ("amqp:internal-error") instead of the
> security error ("amqp:unauthorized-access") that is expected in these cases.
>
> Source code to reproduce the issue using test
> testNoUserOrPasswordWithoutSaslRestrictions:
> https://github.com/brusdev/activemq-artemis/blob/amqp_security_error/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/amqp/JMSConnectionWithSecurityTest.java
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMQ-7196) During startup ActiveMq load all the scheduleDB.data on memory causing OOM
[ https://issues.apache.org/jira/browse/AMQ-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837508#comment-16837508 ] Timothy Bish commented on AMQ-7196: --- I took a quick look and this seems like a reasonable change given what the code is doing in this scenario. > During startup ActiveMq load all the scheduleDB.data on memory causing OOM > --- > > Key: AMQ-7196 > URL: https://issues.apache.org/jira/browse/AMQ-7196 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.16.0, 5.15.9 >Reporter: Alan Protasio >Assignee: Jean-Baptiste Onofré >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > I had a broker with lots of scheduled messages and I noticed that during > startup (clean or unclean) the broker was reading the whole index file and > storing it os memory: > [https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/scheduler/JobSchedulerImpl.java#L665] > In order to prevent the OOM, I changed this method to return a > Iterator instead of a List avoiding load all this > data into the heap. > > I also noticed that during the startup we read the index at least 3 times: > > [https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/scheduler/JobSchedulerStoreImpl.java#L829] > [https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/scheduler/JobSchedulerStoreImpl.java#L857] > and > [https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/scheduler/JobSchedulerStoreImpl.java#L940] > > Probably we can optimize this but this should be another Jira (also maybe we > dont need to call recover(tx) when its a clean shutdown) > [https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/scheduler/JobSchedulerStoreImpl.java#L787] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7194) Past Release Downloads Does Not Work
[ https://issues.apache.org/jira/browse/AMQ-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832832#comment-16832832 ] Timothy Bish commented on AMQ-7194: --- All old releases are available here: http://archive.apache.org/dist/activemq/ > Past Release Downloads Does Not Work > > > Key: AMQ-7194 > URL: https://issues.apache.org/jira/browse/AMQ-7194 > Project: ActiveMQ > Issue Type: Bug >Reporter: CHRISTOPHER GUDINO >Priority: Blocker > Attachments: image001.png > > > The links for any of the past release downloads don't work, in particular... > [http://archive.apache.org/dist/activemq/5.15.3/apache-activemq-5.15.3-bin.zip] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7194) Past Release Downloads Does Not Work
[ https://issues.apache.org/jira/browse/AMQ-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7194. - Resolution: Cannot Reproduce Tried a bunch of random download links for past releases and they are all working including this one. Possible there was an intermittent issue between you and the archive server or some such. > Past Release Downloads Does Not Work > > > Key: AMQ-7194 > URL: https://issues.apache.org/jira/browse/AMQ-7194 > Project: ActiveMQ > Issue Type: Bug >Reporter: CHRISTOPHER GUDINO >Priority: Blocker > > The links for any of the past release downloads don't work, in particular... > [http://archive.apache.org/dist/activemq/5.15.3/apache-activemq-5.15.3-bin.zip] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQCPP-645) Website seems to be broken, can not access the API docs
[ https://issues.apache.org/jira/browse/AMQCPP-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQCPP-645. --- Resolution: Fixed > Website seems to be broken, can not access the API docs > --- > > Key: AMQCPP-645 > URL: https://issues.apache.org/jira/browse/AMQCPP-645 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: CMS Impl, Example Code >Affects Versions: 3.9.4 >Reporter: S A >Assignee: Timothy Bish >Priority: Blocker > > Don't know where else to put this but the website: > [https://activemq.apache.org/components/cms/] > presents a link to "Read the Docs". When clicked you come to: > [http://activemq.apache.org/components/cms/documentation] > Which presents a link to view the API under "API Reference", yet when you > click on that link, it redirects you right back to the home page: > [https://activemq.apache.org/components/cms/] > SO, it appears you can't get to the API. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMQNET-584) CheckMessageListener throws error when any listener exists
[
https://issues.apache.org/jira/browse/AMQNET-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQNET-584.
-
Resolution: Not A Problem
The issue reported is expected behavior. Please feel free to open an new issue
with a PR to fix the incorrect error message details.
> CheckMessageListener throws error when any listener exists
> --
>
> Key: AMQNET-584
> URL: https://issues.apache.org/jira/browse/AMQNET-584
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: NMS
>Affects Versions: 1.7.2
>Reporter: Joshua Ingham
>Priority: Major
>
> When following the example provided at
> [https://activemq.apache.org/components/nms/examples/nms-simple-asynchronous-consumer-example],
> I find that the consumer asynchronous listener throws an error in every
> case. That is:
> {{consumer.Listener += new MessageListener(OnMessage);}}
> The error thrown is "Cannot set Async listeners on Consumers with a prefetch
> limit of zero". However, I have a prefetch limit that is not zero.
> I tracked down some code at
> [https://github.com/ThorTech/apache-nms/blob/master/Apache.NMS.ActiveMQ/1.5.0/src/main/csharp/MessageConsumer.cs]
> which suggests that the function that handles receiving messages and checks
> for listeners always throws an exception:
> {{private void CheckMessageListener()}}
> {
> {{ if(this.listener != null)}}
> {{ {}}
> {{ throw new NMSException("Cannot set Async listeners on Consumers with a
> prefetch limit of zero");}}
> }
> }
> I understand that this may not be the most up to date code, but it would
> explain why I am seeing this behavior. Are asynchronous consumers actually
> supported? This exception, clearly out of place, suggests not, or it is a bug
> and nobody has stumbled upon this behaviour before.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMQNET-584) CheckMessageListener throws error when any listener exists
[
https://issues.apache.org/jira/browse/AMQNET-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16824377#comment-16824377
]
Timothy Bish commented on AMQNET-584:
-
It isn't entirely clear from you description what you are doing but a quick
look at the code would indicate that the error message in CheckMessageListener
is not correct but the fact that it throws is correct. You cannot call the
synchronous receive methods when there is an asynchronous listener registered.
> CheckMessageListener throws error when any listener exists
> --
>
> Key: AMQNET-584
> URL: https://issues.apache.org/jira/browse/AMQNET-584
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: NMS
>Affects Versions: 1.7.2
>Reporter: Joshua Ingham
>Priority: Major
>
> When following the example provided at
> [https://activemq.apache.org/components/nms/examples/nms-simple-asynchronous-consumer-example],
> I find that the consumer asynchronous listener throws an error in every
> case. That is:
> {{consumer.Listener += new MessageListener(OnMessage);}}
> The error thrown is "Cannot set Async listeners on Consumers with a prefetch
> limit of zero". However, I have a prefetch limit that is not zero.
> I tracked down some code at
> [https://github.com/ThorTech/apache-nms/blob/master/Apache.NMS.ActiveMQ/1.5.0/src/main/csharp/MessageConsumer.cs]
> which suggests that the function that handles receiving messages and checks
> for listeners always throws an exception:
> {{private void CheckMessageListener()}}
> {
> {{ if(this.listener != null)}}
> {{ {}}
> {{ throw new NMSException("Cannot set Async listeners on Consumers with a
> prefetch limit of zero");}}
> }
> }
> I understand that this may not be the most up to date code, but it would
> explain why I am seeing this behavior. Are asynchronous consumers actually
> supported? This exception, clearly out of place, suggests not, or it is a bug
> and nobody has stumbled upon this behaviour before.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (AMQ-7183) Windows Server 2019 support
[ https://issues.apache.org/jira/browse/AMQ-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7183. - Resolution: Invalid v4.1.2 is not a supported version. Recommend moving to latest release 5.15.9 > Windows Server 2019 support > --- > > Key: AMQ-7183 > URL: https://issues.apache.org/jira/browse/AMQ-7183 > Project: ActiveMQ > Issue Type: Wish > Environment: Windows Server 2019 >Reporter: mengln >Priority: Major > Fix For: 4.1.2 > > > Hello, I am doing an investigation. Does Windows Server 2019 support the > following products: > ActiveMQ 4.1.2 > Is the other version supported? > Can you tell me, thank you very much. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7184) Windows Server 2019 support
[ https://issues.apache.org/jira/browse/AMQ-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7184. - Resolution: Invalid v4.1.2 is not a supported version. Recommend moving to latest release 5.15.9 > Windows Server 2019 support > --- > > Key: AMQ-7184 > URL: https://issues.apache.org/jira/browse/AMQ-7184 > Project: ActiveMQ > Issue Type: Wish >Reporter: mengln >Priority: Major > > Does Windows Server 2019 support the following products: > ActiveMQ 4.1.2 > Is the other version supported? > Can you tell me, thank you very much. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7181) Feature : Message to be available for consumption after given time elapsed
[ https://issues.apache.org/jira/browse/AMQ-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7181. - Resolution: Not A Problem > Feature : Message to be available for consumption after given time elapsed > -- > > Key: AMQ-7181 > URL: https://issues.apache.org/jira/browse/AMQ-7181 > Project: ActiveMQ > Issue Type: New Feature > Components: activemq-camel > Environment: Windows,*inux,Mac >Reporter: Sathish Kumar >Priority: Minor > Labels: newbie > > MQ Message to be available for consumption after given time elapsed(Message > Age) similar to file age in Apache camel component property. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7181) Feature : Message to be available for consumption after given time elapsed
[ https://issues.apache.org/jira/browse/AMQ-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815425#comment-16815425 ] Timothy Bish commented on AMQ-7181: --- There's already support for scheduling message delivery in the broker: http://activemq.apache.org/delay-and-schedule-message-delivery > Feature : Message to be available for consumption after given time elapsed > -- > > Key: AMQ-7181 > URL: https://issues.apache.org/jira/browse/AMQ-7181 > Project: ActiveMQ > Issue Type: New Feature > Components: activemq-camel > Environment: Windows,*inux,Mac >Reporter: Sathish Kumar >Priority: Minor > Labels: newbie > > MQ Message to be available for consumption after given time elapsed(Message > Age) similar to file age in Apache camel component property. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARTEMIS-2298) AMQP: Update Qpid JMS and Proton-J to latest releases
[ https://issues.apache.org/jira/browse/ARTEMIS-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved ARTEMIS-2298. --- Resolution: Fixed > AMQP: Update Qpid JMS and Proton-J to latest releases > - > > Key: ARTEMIS-2298 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2298 > Project: ActiveMQ Artemis > Issue Type: Task > Components: AMQP >Affects Versions: 2.7.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 2.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update to Qpid JMS 0.41.0 and proton-j 0.32.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARTEMIS-2298) AMQP: Update Qpid JMS and Proton-J to latest releases
Timothy Bish created ARTEMIS-2298: - Summary: AMQP: Update Qpid JMS and Proton-J to latest releases Key: ARTEMIS-2298 URL: https://issues.apache.org/jira/browse/ARTEMIS-2298 Project: ActiveMQ Artemis Issue Type: Task Components: AMQP Affects Versions: 2.7.0 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 2.8.0 Update to Qpid JMS 0.41.0 and proton-j 0.32.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMQ-7179) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
[ https://issues.apache.org/jira/browse/AMQ-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-7179. --- Resolution: Fixed > AMQP: Update Qpid JMS, Proton-J and Netty to latest releases > > > Key: AMQ-7179 > URL: https://issues.apache.org/jira/browse/AMQ-7179 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.9 >Reporter: Timothy Bish >Priority: Major > Fix For: 5.15.10 > > > Update to version 0.41.0 of Qpid JMS and 0.32.0 of proton-j as well as > updating to matched netty version for Qpid JMS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQ-7179) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
Timothy Bish created AMQ-7179: - Summary: AMQP: Update Qpid JMS, Proton-J and Netty to latest releases Key: AMQ-7179 URL: https://issues.apache.org/jira/browse/AMQ-7179 Project: ActiveMQ Issue Type: Task Components: AMQP Affects Versions: 5.15.9 Reporter: Timothy Bish Fix For: 5.15.10 Update to version 0.41.0 of Qpid JMS and 0.32.0 of proton-j as well as updating to matched netty version for Qpid JMS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7175) Bridge fails and reconnect while remoting service through NOB configuration
[ https://issues.apache.org/jira/browse/AMQ-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7175. - Resolution: Invalid Please ask for configuration help on the users mailing list, Jira is where you'd report an actual bug if one was uncovered. http://activemq.apache.org/contact/#mailing > Bridge fails and reconnect while remoting service through NOB configuration > --- > > Key: AMQ-7175 > URL: https://issues.apache.org/jira/browse/AMQ-7175 > Project: ActiveMQ > Issue Type: Bug > Components: networkbridge >Affects Versions: 5.15.9 > Environment: Tested on my laptop W7 > JDK Oracle 1.8 >Reporter: Denis BRONDY >Priority: Major > > Hi guys, > I'm facing a very strange problem. I tested multiple versions of ACTIVEMQ and > I'm still seeing this issue on 5.15.9. > The setup is the following. > I have component which exposes a service interface with one basic method > which only perform a println. The exporter reads either a queue or a topic to > perform the service call and answers back to consumer to a topic / or queue > depending on the consumer strategy (we use JMSReply concept) > I have a component consuming the service method using a proxy that connects > the topic or queue for the acknowledgement of the service call and writes the > RPC on the queue or topic to the service. Service call is synchronous. > I'm using a network of broker with two brokers. > I'm voluntary connecting the service provider on Broker 1 and the service > consumer on Broker 2 to test the message forwarding in between the two. I'm > performing 2000 service calls. > Setup 1: If I ONLY configure a full duplex bridge from B1 to B2, the test > passes. > Setup 2: If I configure two full duplex bridges from B1 to B2 and from B2 to > B1 (which I don't known if it's recommended), the test passes but I'm > observing network bridges disconnecting and reconnecting during the stress > test. > Setup 3: If I only configure two half duplex bridge from B1 to B2 and from B2 > to B1, the test fails after some calls. I see also my network bridge > disconnecting and reconnecting during the stress test > Do you have an idea of what is going wrong ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7172) Problems to download activemq 5.15.7 & 5.15.8 versions from web
[ https://issues.apache.org/jira/browse/AMQ-7172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7172. - Resolution: Not A Bug There is an temporary issue with the website which when resolved will fix the links. For now you can use the Apache Archives to grab those releases: http://archive.apache.org/dist/activemq/ > Problems to download activemq 5.15.7 & 5.15.8 versions from web > > > Key: AMQ-7172 > URL: https://issues.apache.org/jira/browse/AMQ-7172 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-camel >Affects Versions: 5.15.7, 5.15.8 >Reporter: German Ramos >Priority: Major > Fix For: 5.15.6 > > Attachments: image-2019-03-21-15-39-54-701.png > > > When I try to download > |Windows > Distribution|[apache-activemq-5.15.8-bin.zip|http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.15.8/apache-activemq-5.15.8-bin.zip=download]| > OR > |Windows > Distribution|[apache-activemq-5.15.7-bin.zip|http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.15.7/apache-activemq-5.15.7-bin.zip=download]| > web shows: "The requested URL /activemq/5.15.8/apache-activemq-5.15.8-bin.zip > was not found on this server." > The requested URL /activemq/5.15.7/apache-activemq-5.15.7-bin.zip was not > found on this server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7170) How to implement a comunication with Atlassian JIRA and Apache ActiveMQ
[ https://issues.apache.org/jira/browse/AMQ-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7170. - Resolution: Invalid Please ask questions on the users mailing list. > How to implement a comunication with Atlassian JIRA and Apache ActiveMQ > --- > > Key: AMQ-7170 > URL: https://issues.apache.org/jira/browse/AMQ-7170 > Project: ActiveMQ > Issue Type: Bug >Reporter: rafael de almeida oliveira >Priority: Major > > Dear Team, > How to implement a comunication with Atlassian JIRA and Apache ActiveMQ ? > I need to send issue information to AMQ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARTEMIS-2270) Artemis created my broker in a different directory
[
https://issues.apache.org/jira/browse/ARTEMIS-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed ARTEMIS-2270.
-
Resolution: Not A Problem
> Artemis created my broker in a different directory
> --
>
> Key: ARTEMIS-2270
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2270
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.6.4
>Reporter: Leo Provido
>Priority: Trivial
>
> After I type {{artemis create C:\Program Files\BrokerTEST}} in the command
> line while in {{C:\Program Files\apache-artemis-2.6.4\bin}} and do the user
> name, password and allow-anonymous settings, the creation process of the
> broker proceeds and Artemis says that:
> {noformat}
> You can now start the broker by executing:
>"C:\Program Files\apache-artemis-2.6.4\bin\Files\BrokerTEST\bin\artemis"
> run
> Or you can setup the broker as Windows service and run it in the background:
>"C:\Program
> Files\apache-artemis-2.6.4\bin\Files\BrokerTEST\bin\artemis-service.exe"
> install
>"C:\Program
> Files\apache-artemis-2.6.4\bin\Files\BrokerTEST\bin\artemis-service.exe" start
>To stop the windows service:
> "C:\Program
> Files\apache-artemis-2.6.4\bin\Files\BrokerTEST\bin\artemis-service.exe" stop
>To uninstall the windows service
> "C:\Program
> Files\apache-artemis-2.6.4\bin\Files\BrokerTEST\bin\artemis-service.exe"
> uninstall
> {noformat}
> Is there a particular reason why the Artemis app decided to create the broker
> in {{C:\Program Files\apache-artemis-2.6.4\bin\Files\}} instead of
> {{C:\Program Files\}}?
> Thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (AMQCLI-10) changeUserOrUserClientIdConfig
[ https://issues.apache.org/jira/browse/AMQCLI-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQCLI-10. -- Resolution: Incomplete > changeUserOrUserClientIdConfig > -- > > Key: AMQCLI-10 > URL: https://issues.apache.org/jira/browse/AMQCLI-10 > Project: ActiveMQ CLI Tools > Issue Type: New Feature >Reporter: Chris Bogan >Priority: Major > > Help -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQCPP-643) Add an option to time out connection attempts when blocked in ensureConnectionInfoSent
[ https://issues.apache.org/jira/browse/AMQCPP-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQCPP-643: Fix Version/s: 3.9.5 > Add an option to time out connection attempts when blocked in > ensureConnectionInfoSent > -- > > Key: AMQCPP-643 > URL: https://issues.apache.org/jira/browse/AMQCPP-643 > Project: ActiveMQ C++ Client > Issue Type: New Feature > Components: Transports >Affects Versions: 3.9.4 > Environment: HP-UX > Fedora 27 / gcc >Reporter: Roddie Kieley >Assignee: Timothy Bish >Priority: Major > Fix For: 3.9.5 > > Time Spent: 20m > Remaining Estimate: 0h > > In some rare cases client side stack traces show that the client can be stuck > in ensureConnectionInfoSent waiting forever for a response from the broker. > We will add an optional timeout to allow this operation to fail which > defaults to off via a default timeout of 0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMQCPP-643) Add an option to time out connection attempts when blocked in ensureConnectionInfoSent
[ https://issues.apache.org/jira/browse/AMQCPP-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-643. - Resolution: Fixed > Add an option to time out connection attempts when blocked in > ensureConnectionInfoSent > -- > > Key: AMQCPP-643 > URL: https://issues.apache.org/jira/browse/AMQCPP-643 > Project: ActiveMQ C++ Client > Issue Type: New Feature > Components: Transports >Affects Versions: 3.9.4 > Environment: HP-UX > Fedora 27 / gcc >Reporter: Roddie Kieley >Assignee: Timothy Bish >Priority: Major > Fix For: 3.9.5 > > Time Spent: 20m > Remaining Estimate: 0h > > In some rare cases client side stack traces show that the client can be stuck > in ensureConnectionInfoSent waiting forever for a response from the broker. > We will add an optional timeout to allow this operation to fail which > defaults to off via a default timeout of 0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQCPP-638) Add Support for OpenSSL 1.1.1
[ https://issues.apache.org/jira/browse/AMQCPP-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQCPP-638: Fix Version/s: (was: 3.9.5) > Add Support for OpenSSL 1.1.1 > - > > Key: AMQCPP-638 > URL: https://issues.apache.org/jira/browse/AMQCPP-638 > Project: ActiveMQ C++ Client > Issue Type: Improvement > Components: Transports >Affects Versions: 3.9.4 >Reporter: Jeff Gullett >Assignee: Timothy Bish >Priority: Major > > Currently, compiling the OpenSSL-enabled versions of ActiveMQ-CPP with any > version of OpenSSL newer than 1.0.2 results in compile-time errors. OpenSSL > is dropping support for 1.0.2 on 2019-12-31. The next long-term support > version of OpenSSL, 1.1.1, has been released. Please update ActiveMQ-CPP so > it can be built using OpenSSL 1.1.1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7131) ActiveMQ JMS pool has no borrow timeout causing starvation
[ https://issues.apache.org/jira/browse/AMQ-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745230#comment-16745230 ] Timothy Bish commented on AMQ-7131: --- [~graben] while the change looks a bit odd it isn't much worse than some of the other code in there that works around behaviours in the commons pool that clash with how a Connection pool needs to operate so that isn't as bad as one might think. The connect timeout fix seems more awkward to me because it forces a lengthy wait on something we can know is going to fail and then puts the requirement on the caller to respond appropriately to that failure. It doesn't appear there is anything else we can do in the pool configuration to prevent the key from being removed when the entries hit zero due to the single connection being evicted but maybe you want to poke around in there to see for sure. > ActiveMQ JMS pool has no borrow timeout causing starvation > -- > > Key: AMQ-7131 > URL: https://issues.apache.org/jira/browse/AMQ-7131 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-pool >Affects Versions: 5.15.8 >Reporter: Benjamin Graf >Assignee: Benjamin Graf >Priority: Major > > A maxPoolSize of 1 can cause starvation during createConnection if the only > connection gets evicted concurrently since borrow method of pool has no > timeout waiting forever. > Maybe introduce a new variable connectionTimeout with default 3ms. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7131) ActiveMQ JMS pool has no borrow timeout causing starvation
[ https://issues.apache.org/jira/browse/AMQ-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739808#comment-16739808 ] Timothy Bish commented on AMQ-7131: --- Blocking and throwing an error seems like the wrong thing to do, if the connection timed out it should be replaced by a new one. Perhaps not blocking and handling the NoSuchElementException to replenish the pool entry would be a better idea. Do you have a test for this? > ActiveMQ JMS pool has no borrow timeout causing starvation > -- > > Key: AMQ-7131 > URL: https://issues.apache.org/jira/browse/AMQ-7131 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-pool >Affects Versions: 5.15.8 >Reporter: Benjamin Graf >Assignee: Benjamin Graf >Priority: Major > > A maxPoolSize of 1 can cause starvation during createConnection if the only > connection gets evicted concurrently since borrow method of pool has no > timeout waiting forever. > Maybe introduce a new variable connectionTimeout with default 3ms. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7123) Integrating Apache ActiveMQ with Tibco EMS: Error: Not allowed to create destination
[ https://issues.apache.org/jira/browse/AMQ-7123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7123. - Resolution: Invalid Please ask for configuration support on the users mailing list. > Integrating Apache ActiveMQ with Tibco EMS: Error: Not allowed to create > destination > > > Key: AMQ-7123 > URL: https://issues.apache.org/jira/browse/AMQ-7123 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.6.0 > Environment: More details about the error: > > 2018-12-11 16:49:21,738 | ERROR | Failed to load: class path resource > [activemq.xml], reason: Error creating bean with name > 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class path > resource [activemq.xml]: Invocation of init method failed; nested exception > is javax.jms.InvalidDestinationException: Not allowed to create destination | > org.apache.activemq.xbean.XBeanBrokerFactory | main > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class > path resource [activemq.xml]: Invocation of init method failed; nested > exception is javax.jms.InvalidDestinationException: Not allowed to create > destination > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1420) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293) > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192) > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585) > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425) > at > org.apache.xbean.spring.context.ResourceXmlApplicationContext.(ResourceXmlApplicationContext.java:64) > at > org.apache.xbean.spring.context.ResourceXmlApplicationContext.(ResourceXmlApplicationContext.java:52) > at > org.apache.activemq.xbean.XBeanBrokerFactory$1.(XBeanBrokerFactory.java:108) > at > org.apache.activemq.xbean.XBeanBrokerFactory.createApplicationContext(XBeanBrokerFactory.java:108) > at > org.apache.activemq.xbean.XBeanBrokerFactory.createBroker(XBeanBrokerFactory.java:72) > at > org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:71) > at > org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:54) > at > org.apache.activemq.console.command.StartCommand.startBroker(StartCommand.java:115) > at > org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:74) > at > org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57) > at > org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:148) > at > org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57) > at > org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.activemq.console.Main.runTaskClass(Main.java:257) > at org.apache.activemq.console.Main.main(Main.java:111) > Caused by: javax.jms.InvalidDestinationException: Not allowed to create > destination > at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:540) > at > com.tibco.tibjms.TibjmsxSessionImp._createConsumer(TibjmsxSessionImp.java:425) > at > com.tibco.tibjms.TibjmsxSessionImp._createConsumer(TibjmsxSessionImp.java:347) > at > com.tibco.tibjms.TibjmsQueueSession.createReceiver(TibjmsQueueSession.java:68) > at > org.apache.activemq.network.jms.QueueBridge.createConsumer(QueueBridge.java:63) > at > org.apache.activemq.network.jms.DestinationBridge.start(DestinationBridge.java:85) >
[jira] [Updated] (AMQCPP-642) Create 3.10.x branch based upon 3.9.x code.
[ https://issues.apache.org/jira/browse/AMQCPP-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQCPP-642: Fix Version/s: (was: 3.10) 3.10.0 > Create 3.10.x branch based upon 3.9.x code. > --- > > Key: AMQCPP-642 > URL: https://issues.apache.org/jira/browse/AMQCPP-642 > Project: ActiveMQ C++ Client > Issue Type: Task >Affects Versions: 3.10.0 >Reporter: Jamie goodyear >Assignee: Jamie goodyear >Priority: Major > Fix For: 3.10.0 > > > Create 3.10.x branch based upon 3.9.x code base. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQCPP-642) Create 3.10.x branch based upon 3.9.x code.
[ https://issues.apache.org/jira/browse/AMQCPP-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQCPP-642: Affects Version/s: (was: 3.10) 3.10.0 > Create 3.10.x branch based upon 3.9.x code. > --- > > Key: AMQCPP-642 > URL: https://issues.apache.org/jira/browse/AMQCPP-642 > Project: ActiveMQ C++ Client > Issue Type: Task >Affects Versions: 3.10.0 >Reporter: Jamie goodyear >Assignee: Jamie goodyear >Priority: Major > Fix For: 3.10.0 > > > Create 3.10.x branch based upon 3.9.x code base. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQCPP-619) Support for SSL wilcard certificate
[ https://issues.apache.org/jira/browse/AMQCPP-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712946#comment-16712946 ] Timothy Bish commented on AMQCPP-619: - Please revert from 3.9.x Code uses tabs which makes it unreadable when I look at it, please format according the the surrounding code to make it easier to review. > Support for SSL wilcard certificate > --- > > Key: AMQCPP-619 > URL: https://issues.apache.org/jira/browse/AMQCPP-619 > Project: ActiveMQ C++ Client > Issue Type: New Feature >Affects Versions: 3.9.4 >Reporter: Francois Godin >Assignee: Jamie goodyear >Priority: Major > Attachments: amqcpp-619.patch, sslCertificateWildcard.patch > > > SSL certificate can contain wildcard in the hostname. For example, the > certificate URL "*.proxy.app.com" should match the following address: > * 1.proxy.app.com > * 2.proxy.app.com > Sadly, ActiveMQ-CPP simply compare the two values and thus does not accept > such certificates. > The Openssl page https://wiki.openssl.org/index.php/Hostname_validation > describe some possible implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQCPP-619) Support for SSL wilcard certificate
[ https://issues.apache.org/jira/browse/AMQCPP-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712928#comment-16712928 ] Timothy Bish commented on AMQCPP-619: - -1 on merge to 3.9.x as this break compat with older versions of OpenSSL on this version. Also please fix the code formatting to match the other parts of the code. Please revert this from 3.9.x > Support for SSL wilcard certificate > --- > > Key: AMQCPP-619 > URL: https://issues.apache.org/jira/browse/AMQCPP-619 > Project: ActiveMQ C++ Client > Issue Type: New Feature >Affects Versions: 3.9.4 >Reporter: Francois Godin >Assignee: Timothy Bish >Priority: Major > Attachments: amqcpp-619.patch, sslCertificateWildcard.patch > > > SSL certificate can contain wildcard in the hostname. For example, the > certificate URL "*.proxy.app.com" should match the following address: > * 1.proxy.app.com > * 2.proxy.app.com > Sadly, ActiveMQ-CPP simply compare the two values and thus does not accept > such certificates. > The Openssl page https://wiki.openssl.org/index.php/Hostname_validation > describe some possible implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7119) Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ??
[ https://issues.apache.org/jira/browse/AMQ-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7119. - Resolution: Fixed > Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ?? > --- > > Key: AMQ-7119 > URL: https://issues.apache.org/jira/browse/AMQ-7119 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.15.7 > Environment: ActiveMQ from 5.5.1 and ActiveMQ 5.15.7 >Reporter: sunil kumar >Priority: Major > > We are upgrading activeMQ from 5.5.1 to 5.15.7. But we didn't find > replacement jar for KahaDB-5.7.0.jar in ActiveMQ 5.15.7. > Do we need to use activemq-kahadb-store-5.15.7.jar , is this direct > replacement for kahaDB-5.7.0.jar ? > Please help us in finding right replacement of jar. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7114) The inactive queues deleted via gcInactiveDestinations reappear on activemq restart
[
https://issues.apache.org/jira/browse/AMQ-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-7114:
--
Fix Version/s: WAITING_FOR_TEST
> The inactive queues deleted via gcInactiveDestinations reappear on activemq
> restart
> ---
>
> Key: AMQ-7114
> URL: https://issues.apache.org/jira/browse/AMQ-7114
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.8
>Reporter: AKSHAY C KITHANI
>Priority: Major
> Fix For: WAITING_FOR_TEST
>
>
> The inactive queues deleted via gcInactiveDestinations reappear on activemq
> restart
> -Activemq version-5.15.8
> -Persistent store default kahaDB
> {noformat}
> schedulePeriodForDestinationPurge="15000" {noformat}
> {noformat}
> inactiveTimoutBeforeGC="15000"/>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMQ-7114) The inactive queues deleted via gcInactiveDestinations reappear on activemq restart
[
https://issues.apache.org/jira/browse/AMQ-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708762#comment-16708762
]
Timothy Bish commented on AMQ-7114:
---
You will need to provide a unit test to reproduce this issue or it will likely
get closed in the future
> The inactive queues deleted via gcInactiveDestinations reappear on activemq
> restart
> ---
>
> Key: AMQ-7114
> URL: https://issues.apache.org/jira/browse/AMQ-7114
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.15.8
>Reporter: AKSHAY C KITHANI
>Priority: Major
> Fix For: WAITING_FOR_TEST
>
>
> The inactive queues deleted via gcInactiveDestinations reappear on activemq
> restart
> -Activemq version-5.15.8
> -Persistent store default kahaDB
> {noformat}
> schedulePeriodForDestinationPurge="15000" {noformat}
> {noformat}
> inactiveTimoutBeforeGC="15000"/>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (AMQ-7119) Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ??
[ https://issues.apache.org/jira/browse/AMQ-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7119. - Resolution: Invalid In the future support questions should be asked on the users mailing list. The activemq-kahadb-store jar is the current library to use when running with the latest broker and you want KahaDB > Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ?? > --- > > Key: AMQ-7119 > URL: https://issues.apache.org/jira/browse/AMQ-7119 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.15.7 > Environment: ActiveMQ from 5.5.1 and ActiveMQ 5.15.7 >Reporter: sunil kumar >Priority: Major > > We are upgrading activeMQ from 5.5.1 to 5.15.7. But we didn't find > replacement jar for KahaDB-5.7.0.jar in ActiveMQ 5.15.7. > Do we need to use activemq-kahadb-store-5.15.7.jar , is this direct > replacement for kahaDB-5.7.0.jar ? > Please help us in finding right replacement of jar. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMQ-7119) Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ??
[ https://issues.apache.org/jira/browse/AMQ-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened AMQ-7119: --- > Which is the replacement for kahaDB-5.7.0.jar in ActiveMQ 5.15.7 ?? > --- > > Key: AMQ-7119 > URL: https://issues.apache.org/jira/browse/AMQ-7119 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.15.7 > Environment: ActiveMQ from 5.5.1 and ActiveMQ 5.15.7 >Reporter: sunil kumar >Priority: Major > > We are upgrading activeMQ from 5.5.1 to 5.15.7. But we didn't find > replacement jar for KahaDB-5.7.0.jar in ActiveMQ 5.15.7. > Do we need to use activemq-kahadb-store-5.15.7.jar , is this direct > replacement for kahaDB-5.7.0.jar ? > Please help us in finding right replacement of jar. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARTEMIS-2189) Deleting JMS temporary destination with a closed session should throw an exception
[
https://issues.apache.org/jira/browse/ARTEMIS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707457#comment-16707457
]
Timothy Bish commented on ARTEMIS-2189:
---
A JMS Temporary Destination has a lifetime that is tied to the connection upon
which it was created, not to the Session that was used to create it, so in
actuality the delete method should be usable on a Temporary Destination right
up to the point where the Connection is closed. So the premise of this issue
seems a bit incorrect.
> Deleting JMS temporary destination with a closed session should throw an
> exception
> --
>
> Key: ARTEMIS-2189
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2189
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Affects Versions: 2.6.3
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
>
> If a client closes its JMS session (intentionally or not) and then invokes
> {{javax.jms.TemporaryQueue.delete()}} or
> {{javax.jms.TemporaryTopic.delete()}} these methods will return without
> actually deleting the destination (because the underlying session was
> closed). This can be confusing and/or mask programming errors.
> The [JavaDoc for
> {{javax.jms.TemporaryQueue}}|https://docs.oracle.com/javaee/7/api/javax/jms/TemporaryQueue.html#delete--]
> states that a {{JMSException}} should be thrown, "if the JMS provider fails
> to delete the temporary queue due to some internal error."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (AMQ-7117) some bug with the failover mode,help！
[ https://issues.apache.org/jira/browse/AMQ-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7117. - Resolution: Invalid Please ask for help on the users mailing list. The version you are using is quite old and not supported so you'd need to update to the latest if a real bug is uncovered. > some bug with the failover mode,help！ > - > > Key: AMQ-7117 > URL: https://issues.apache.org/jira/browse/AMQ-7117 > Project: ActiveMQ > Issue Type: Bug > Components: Connector, Distribution >Affects Versions: 5.10.2 >Reporter: wuzhiyong >Priority: Major > > i have create a consumer for test use the failover mode,such as > failover:(tcp://ip1:61616,ip2://61616) > 1) when the amq service in the ip1 and ip2 both normal , test success; > 2) then i shutdown the one of the amq service, console print switch the other > amq; > 3) then i start the amq service just closed, and shutdown the another > 4) After a few repetitions 3), the Consumer will quit Automatically ， only > needs two or three times generally. > how to solve this question? is a bug Or designed originally ? > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7113) a lot of "BrokerService" threads are blocked by another thread which is doing the operation of java.util.regex.Matcher.matches in the context of org.apache.activemq.filter
[ https://issues.apache.org/jira/browse/AMQ-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-7113: -- Priority: Major (was: Blocker) > a lot of "BrokerService" threads are blocked by another thread which is doing > the operation of java.util.regex.Matcher.matches in the context of > org.apache.activemq.filter.ComparisonExpression$LikeExpression.evaluate > - > > Key: AMQ-7113 > URL: https://issues.apache.org/jira/browse/AMQ-7113 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.14.4 > Environment: Linux version 3.10.0-327.el7.x86_64 > JDK Version: open-jdk 1.8 >Reporter: chenyouxing >Priority: Major > > thread dump of the blocking thread as below: > "ActiveMQ BrokerService[databus_amq_crm] Task-26508" #203818 daemon prio=5 > os_prio=0 tid=0x7f9138297800 nid=0x5910 runnable [0x7f90b43fe000] > java.lang.Thread.State: RUNNABLE > at java.util.regex.Pattern$Curly.match1(Pattern.java:4300) > at java.util.regex.Pattern$Curly.match(Pattern.java:4236) > at java.util.regex.Pattern$Begin.match(Pattern.java:3525) > at java.util.regex.Matcher.match(Matcher.java:1270) > at java.util.regex.Matcher.matches(Matcher.java:604) > at > org.apache.activemq.filter.ComparisonExpression$LikeExpression.evaluate(ComparisonExpression.java:151) > at > org.apache.activemq.filter.LogicExpression$1.evaluate(LogicExpression.java:45) > at > org.apache.activemq.filter.LogicExpression.matches(LogicExpression.java:90) > at > org.apache.activemq.broker.region.AbstractSubscription.matches(AbstractSubscription.java:108) > at > org.apache.activemq.broker.region.policy.SimpleDispatchSelector.canDispatch(SimpleDispatchSelector.java:46) > at > org.apache.activemq.broker.region.QueueDispatchSelector.canSelect(QueueDispatchSelector.java:56) > at org.apache.activemq.broker.region.Queue.doActualDispatch(Queue.java:2139) > at org.apache.activemq.broker.region.Queue.doDispatch(Queue.java:2084) > at org.apache.activemq.broker.region.Queue.removeSubscription(Queue.java:593) > at > org.apache.activemq.broker.region.DestinationFilter.removeSubscription(DestinationFilter.java:127) > at > org.apache.activemq.broker.region.virtual.MappedQueueFilter.removeSubscription(MappedQueueFilter.java:97) > - locked <0x0005c1775be0> (a > org.apache.activemq.broker.region.virtual.MappedQueueFilter) > at > org.apache.activemq.broker.region.AbstractRegion.removeConsumer(AbstractRegion.java:477) > at > org.apache.activemq.broker.region.RegionBroker.removeConsumer(RegionBroker.java:438) > at > org.apache.activemq.broker.jmx.ManagedRegionBroker.removeConsumer(ManagedRegionBroker.java:258) > at > org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:138) > at > org.apache.activemq.broker.BrokerFilter.removeConsumer(BrokerFilter.java:138) > at > org.apache.activemq.broker.MutableBrokerFilter.removeConsumer(MutableBrokerFilter.java:143) > at > org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:738) > at > org.apache.activemq.broker.TransportConnection.processRemoveSession(TransportConnection.java:777) > at > org.apache.activemq.broker.TransportConnection.processRemoveConnection(TransportConnection.java:888) > - locked <0x0005ddde7a68> (a > org.apache.activemq.broker.jmx.ManagedTransportConnection) > at > org.apache.activemq.broker.TransportConnection.doStop(TransportConnection.java:1234) > at > org.apache.activemq.broker.TransportConnection$4.run(TransportConnection.java:1164) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Locked ownable synchronizers: > - <0x0005c0d9c7a0> (a > java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync) > - <0x0005c3328390> (a > java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync) > - <0x0005ddc64a38> (a java.util.concurrent.ThreadPoolExecutor$Worker) > - <0x0005dddeba10> (a > java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync) > > and typical blocked threads'(count: 1400+) dump as below: > "ActiveMQ BrokerService[databus_amq_crm] Task-26418" #197084 daemon prio=5 > os_prio=0 tid=0x7f91b40cb000 nid=0x3b3c waiting for monitor entry > [0x7f9086321000] > java.lang.Thread.State: BLOCKED (on object monitor) > at > org.apache.activemq.broker.region.virtual.MappedQueueFilter.removeSubscription(MappedQueueFilter.java:97) > - waiting to lock <0x0005c1775be0> (a >
[jira] [Closed] (AMQ-7111) ActiveMQ print multiple log on console
[
https://issues.apache.org/jira/browse/AMQ-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-7111.
-
Resolution: Invalid
Please ask for help on the users mailing list
> ActiveMQ print multiple log on console
> --
>
> Key: AMQ-7111
> URL: https://issues.apache.org/jira/browse/AMQ-7111
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.15.8
>Reporter: Mahdi
>Priority: Major
>
> Hello .
> I write example authentication code for my own application .
> but can not understand why logger wrote dual time logs on console .
> this is my example test code :
> {code:java}
> import org.apache.activemq.broker.Broker;
> import org.apache.activemq.broker.BrokerFilter;
> import org.apache.activemq.broker.ConnectionContext;
> import org.apache.activemq.command.ConnectionInfo;
> import java.util.logging.Logger;
> public class AuthenticationFilter extends BrokerFilter {
> private static final Logger logger =
> Logger.getLogger(AuthenticationFilter.class.getName());
> public AuthenticationFilter(Broker next) {
> super(next);
> }
> @Override
> public void addConnection(ConnectionContext context, ConnectionInfo info)
> throws Exception {
> String username = info.getUserName() ;
> String password = info.getPassword() ;
> if (username.equals("EXAMPLE_USER_NAME") &&
> password.equals("EXAMPLE_PASSWORD")) {
> logger.info("Authentication Success .");
> super.addConnection(context, info);
> } else {
> logger.info("Authentication failed .");
> throw new SecurityException();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (AMQ-7104) java.io.IOException: Input/output error on ActiveMQ
[ https://issues.apache.org/jira/browse/AMQ-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7104. - Resolution: Not A Problem You can ask for help on the users forum, SMB is not a good option though no > java.io.IOException: Input/output error on ActiveMQ > --- > > Key: AMQ-7104 > URL: https://issues.apache.org/jira/browse/AMQ-7104 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.15.3 >Reporter: Siddardha >Priority: Major > Fix For: 5.15.3 > > Attachments: activemq.log > > > There is an error related to 'java.io.IOException: Input/output error ' on > Active MQ Cluster Setup (Master/Slave) which is stopping the BrokerService. > Also, It is not failing over the service to other node due to the same. > Active MQ Version: apache-activemq-5.15.3 > Java Version: 1.8.0_181 > OS: RHEL 7.4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQ-7109) Issues with configuring authorizationPlugin
[ https://issues.apache.org/jira/browse/AMQ-7109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7109. - Resolution: Invalid Please ask for help on the users mailing list: http://activemq.apache.org/discussion-forums.html > Issues with configuring authorizationPlugin > --- > > Key: AMQ-7109 > URL: https://issues.apache.org/jira/browse/AMQ-7109 > Project: ActiveMQ > Issue Type: Bug > Components: runtime configuration plugin >Affects Versions: 5.9.0 >Reporter: Abhijit Vikash >Priority: Critical > Fix For: 5.9.0 > > Attachments: apache_amq_config.zip > > > Unable to configure authorizationPlugin. > Can you please held or guide how to configure it correctly for Apache AMQ > 5.9.0? > Tried all combinations :(! > > > > > write="jmsUsers,admins" admin="jmsUsers,admins" /> > write="jmsUsers,admins" admin="jmsUsers,admins" /> > write="admins,producers" admin="admins" /> > write="admins,producers" admin="admins" /> > write="admins,producers,consumers" admin="admins,producers,consumers" /> > write="admins,producers,consumers" admin="admins,producers,consumers" /> > > > admin="admins"/> > > > >
[jira] [Commented] (AMQ-7108) Scheduled job scheduling occasionally fails with java.lang.ClassCastException: org.apache.activemq.store.kahadb.data.KahaTraceCommand cannot be cast to org.apache.activem
[
https://issues.apache.org/jira/browse/AMQ-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695443#comment-16695443
]
Timothy Bish commented on AMQ-7108:
---
You need to test using the latest release (5.15.8) as your version is quite old
and is not supported. It's rather likely this issue has already been fixed in
a newer release.
> Scheduled job scheduling occasionally fails with
> java.lang.ClassCastException:
> org.apache.activemq.store.kahadb.data.KahaTraceCommand cannot be cast to
> org.apache.activemq.store.kahadb.data.KahaAddScheduledJobCommand
>
>
> Key: AMQ-7108
> URL: https://issues.apache.org/jira/browse/AMQ-7108
> Project: ActiveMQ
> Issue Type: Bug
> Components: Job Scheduler, KahaDB
>Affects Versions: 5.11.1
> Environment: *OS*: Linux ip-10-88-2-47 3.13.0-125-generic #174-Ubuntu
> SMP Mon Jul 10 18:51:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> *AMQ*: 5.11.1
> *glusterfs*: 3.8.15
> *java*: 1.8.0_144-b01
>
>Reporter: Ben D'Herville
>Priority: Minor
> Attachments: activemq.xml
>
>
> *Issue*
> We have been running the stack with the same stated versions mentioned in
> this ticket's environment details for over a year. Recently we have
> experienced ActiveMQ outages as a result of the exception below. There has
> been a increase in load but not significant.
> Scheduled messages are being used as a polling mechanism in a workflow
> system. A workflow will execute a step then schedule a small object message,
> containing just an identifier, to check for a result in a number of seconds.
> The consumer of the message will schedule another message if the task is not
> complete yet. We also have a batch process that can start a number of
> workflows concurrently. Usually in the order of 100's which means 100's of
> scheduled messages can be created concurrently.
> The most recent failure occurred with a batch of only 64.
> We haven't noticed any data loss as a result of this but it doesn't cause a
> complete outage of our production system.
> *Recovery*
> The only way we have been able to recover from this error is to restart the
> broker. kahadb is configured to check for corrupt journal which would
> recover the journal on startup. It is unclear if the journal is corrupted
> though.
> *Reproduction*
> We have tried to reproduce this issue using the ActiveMQ performance maven
> plugin but was unable to. We had 1 producers concurrently schedule 500
> messages each.
>
> Note there are two stack traces here. The second one is possibly a
> side-effect of the first one.
> {code:java}
> 2018-Nov-21 15:16:48 JobScheduler:JMS
> [org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl] ERROR: JMS
> Failed to schedule job
> java.lang.ClassCastException:
> org.apache.activemq.store.kahadb.data.KahaTraceCommand cannot be cast to
> org.apache.activemq.store.kahadb.data.KahaAddScheduledJobCommand
> at
> org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl.getPayload(JobSchedulerStoreImpl.java:529)
> at
> org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl.fireJob(JobSchedulerImpl.java:789)
> at
> org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl.mainLoop(JobSchedulerImpl.java:720)
> at
> org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl.run(JobSchedulerImpl.java:673)
> at java.lang.Thread.run(Thread.java:748)
> 2018-Nov-21 15:24:45 ActiveMQ Transport: tcp:///10.88.2.113:54256@61616
> [org.apache.activemq.transaction.LocalTransaction] WARN: POST COMMIT FAILED:
> java.lang.NullPointerException
> at
> org.apache.activemq.store.kahadb.AbstractKahaDBStore.store(AbstractKahaDBStore.java:482)
> at
> org.apache.activemq.store.kahadb.AbstractKahaDBStore.store(AbstractKahaDBStore.java:394)
> at
> org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl.doSchedule(JobSchedulerImpl.java:264)
> at
> org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl.schedule(JobSchedulerImpl.java:99)
> at
> org.apache.activemq.broker.scheduler.SchedulerBroker.doSchedule(SchedulerBroker.java:197)
> at
> org.apache.activemq.broker.scheduler.SchedulerBroker.access$000(SchedulerBroker.java:48)
> at
> org.apache.activemq.broker.scheduler.SchedulerBroker$1.afterCommit(SchedulerBroker.java:162)
> at
> org.apache.activemq.transaction.Transaction.fireAfterCommit(Transaction.java:126)
> at
> org.apache.activemq.transaction.Transaction.doPostCommit(Transaction.java:195)
> at
>
[jira] [Resolved] (AMQ-7097) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
[ https://issues.apache.org/jira/browse/AMQ-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-7097. --- Resolution: Fixed > AMQP: Update Qpid JMS, Proton-J and Netty to latest releases > > > Key: AMQ-7097 > URL: https://issues.apache.org/jira/browse/AMQ-7097 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.7 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 5.15.9 > > > Update AMQP libraries to latest > * Qpid JMS 0.38.0 > * Proton-j 0.30.0 > * Netty 4.1.31.Final -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7099) After upgrading activemq 5.5.1 to activemq 5.13.1, issues with java.security.Security.insertProviderAt/org.apache.activemq.broker.BrokerService
[ https://issues.apache.org/jira/browse/AMQ-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-7099: -- Priority: Minor (was: Blocker) > After upgrading activemq 5.5.1 to activemq 5.13.1, issues with > java.security.Security.insertProviderAt/org.apache.activemq.broker.BrokerService > > > Key: AMQ-7099 > URL: https://issues.apache.org/jira/browse/AMQ-7099 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.13.1 > Environment: OS: All platforms > Products involved are : > WAS 8.5.5.9 - 8.5.5.14 > LDAP/Active directory > JazzSM(DASH) 3.1.3 CP5 -CP7 >Reporter: sunil kumar >Priority: Minor > > We upgraded activemq 5.5.1 to activemq 5.13.1 to over come the security > vulnerable to CVE-2015-5254 and CVE-2014-3612. for ref: here are the links > for each CVE: > [http://activemq.apache.org/security-advisories.data/CVE-2015-5254-announcement.txt?version=1=1449589734000=v2] > > [http://activemq.apache.org/security-advisories.data/CVE-2014-3612-announcement.txt?version=2=1423051365000=v2] > > After upgrading we hit with following issues while getting LDAP user > informations . > Following are the stack trace : > *16:06:07.353 0x33fb300 j9trc_aux.0 - jstacktrace:* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [1] > java.security.Security.insertProviderAt (Security.java:369)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [2] > org.apache.activemq.broker.BrokerService. (BrokerService.java:275)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [3] > com.ibm.tivoli.rest.event.amq.AMQPropertiesBrokerFactory.createBroker > (AMQPropertiesBrokerFactory.java:30)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [4] > org.apache.activemq.broker.BrokerFactory.createBroker (BrokerFactory.java:71)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [5] > org.apache.activemq.broker.BrokerFactory.createBroker (BrokerFactory.java:54)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [6] > com.ibm.tivoli.rest.event.amq.AMQEventRouterFactory.startBroker > (AMQEventRouterFactory.java:430)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [7] > com.ibm.tivoli.rest.event.amq.AMQEventRouterFactory.start > (AMQEventRouterFactory.java:151)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [8] > com.ibm.tivoli.rest.event.EventRouterFactory.getInstance > (EventRouterFactory.java:43)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [9] > com.ibm.tivoli.rest.amq.AjaxServlet. (AjaxServlet.java:59)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [10] > java.lang.J9VMInternals.newInstanceImpl (Native Method)* > 16:06:07.353 0x33fb300 j9trc_aux.1 - [11] java.lang.Class.newInstance > (Class.java:1843) (Compiled Code) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [12] java.beans.Beans.instantiate > (Beans.java:240) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [13] java.beans.Beans.instantiate > (Beans.java:88) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [14] > com.ibm.ws.webcontainer.servlet.ServletWrapper$1.run > (ServletWrapper.java:1489) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [15] > com.ibm.ws.security.util.AccessController.doPrivileged > (AccessController.java:118) (Compiled Code) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [16] > com.ibm.ws.webcontainer.servlet.ServletWrapper.loadServlet > (ServletWrapper.java:1478) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [17] > com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck > (ServletWrapper.java:1357) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [18] > com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions (WebApp.java:642) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [19] > com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally > (WebApp.java:608) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [20] > com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize (WebAppImpl.java:426) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [21] > com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication > (WebGroupImpl.java:88) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [22] > com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication > (VirtualHostImpl.java:171) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [23] > com.ibm.ws.webcontainer.WSWebContainer.addWebApp (WSWebContainer.java:904) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [24] > com.ibm.ws.webcontainer.WSWebContainer.addWebApplication > (WSWebContainer.java:789) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [25] > com.ibm.ws.webcontainer.component.WebContainerImpl.install > (WebContainerImpl.java:427) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [26] > com.ibm.ws.webcontainer.component.WebContainerImpl.start > (WebContainerImpl.java:719) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [27] > com.ibm.ws.runtime.component.ApplicationMgrImpl.start >
[jira] [Closed] (AMQ-7099) After upgrading activemq 5.5.1 to activemq 5.13.1, issues with java.security.Security.insertProviderAt/org.apache.activemq.broker.BrokerService
[ https://issues.apache.org/jira/browse/AMQ-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7099. - Resolution: Invalid Please use the users mailing list to ask for help with working out a configuration that works with IBM this does not appear to be a bug, and the version being tried is not a supported version. > After upgrading activemq 5.5.1 to activemq 5.13.1, issues with > java.security.Security.insertProviderAt/org.apache.activemq.broker.BrokerService > > > Key: AMQ-7099 > URL: https://issues.apache.org/jira/browse/AMQ-7099 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.13.1 > Environment: OS: All platforms > Products involved are : > WAS 8.5.5.9 - 8.5.5.14 > LDAP/Active directory > JazzSM(DASH) 3.1.3 CP5 -CP7 >Reporter: sunil kumar >Priority: Minor > > We upgraded activemq 5.5.1 to activemq 5.13.1 to over come the security > vulnerable to CVE-2015-5254 and CVE-2014-3612. for ref: here are the links > for each CVE: > [http://activemq.apache.org/security-advisories.data/CVE-2015-5254-announcement.txt?version=1=1449589734000=v2] > > [http://activemq.apache.org/security-advisories.data/CVE-2014-3612-announcement.txt?version=2=1423051365000=v2] > > After upgrading we hit with following issues while getting LDAP user > informations . > Following are the stack trace : > *16:06:07.353 0x33fb300 j9trc_aux.0 - jstacktrace:* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [1] > java.security.Security.insertProviderAt (Security.java:369)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [2] > org.apache.activemq.broker.BrokerService. (BrokerService.java:275)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [3] > com.ibm.tivoli.rest.event.amq.AMQPropertiesBrokerFactory.createBroker > (AMQPropertiesBrokerFactory.java:30)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [4] > org.apache.activemq.broker.BrokerFactory.createBroker (BrokerFactory.java:71)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [5] > org.apache.activemq.broker.BrokerFactory.createBroker (BrokerFactory.java:54)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [6] > com.ibm.tivoli.rest.event.amq.AMQEventRouterFactory.startBroker > (AMQEventRouterFactory.java:430)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [7] > com.ibm.tivoli.rest.event.amq.AMQEventRouterFactory.start > (AMQEventRouterFactory.java:151)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [8] > com.ibm.tivoli.rest.event.EventRouterFactory.getInstance > (EventRouterFactory.java:43)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [9] > com.ibm.tivoli.rest.amq.AjaxServlet. (AjaxServlet.java:59)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [10] > java.lang.J9VMInternals.newInstanceImpl (Native Method)* > 16:06:07.353 0x33fb300 j9trc_aux.1 - [11] java.lang.Class.newInstance > (Class.java:1843) (Compiled Code) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [12] java.beans.Beans.instantiate > (Beans.java:240) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [13] java.beans.Beans.instantiate > (Beans.java:88) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [14] > com.ibm.ws.webcontainer.servlet.ServletWrapper$1.run > (ServletWrapper.java:1489) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [15] > com.ibm.ws.security.util.AccessController.doPrivileged > (AccessController.java:118) (Compiled Code) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [16] > com.ibm.ws.webcontainer.servlet.ServletWrapper.loadServlet > (ServletWrapper.java:1478) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [17] > com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck > (ServletWrapper.java:1357) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [18] > com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions (WebApp.java:642) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [19] > com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally > (WebApp.java:608) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [20] > com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize (WebAppImpl.java:426) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [21] > com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication > (WebGroupImpl.java:88) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [22] > com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication > (VirtualHostImpl.java:171) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [23] > com.ibm.ws.webcontainer.WSWebContainer.addWebApp (WSWebContainer.java:904) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [24] > com.ibm.ws.webcontainer.WSWebContainer.addWebApplication > (WSWebContainer.java:789) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [25] > com.ibm.ws.webcontainer.component.WebContainerImpl.install > (WebContainerImpl.java:427) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [26] >
[jira] [Closed] (AMQCPP-496) Number Of Connections Limited By DECAF_MAX_TLS_SLOTS in ThreadingTypes.h
[ https://issues.apache.org/jira/browse/AMQCPP-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQCPP-496. --- Resolution: Won't Fix > Number Of Connections Limited By DECAF_MAX_TLS_SLOTS in ThreadingTypes.h > > > Key: AMQCPP-496 > URL: https://issues.apache.org/jira/browse/AMQCPP-496 > Project: ActiveMQ C++ Client > Issue Type: Improvement > Components: CMS Impl >Affects Versions: 3.6.0 > Environment: All >Reporter: Kevin Urciolo >Assignee: Timothy Bish >Priority: Minor > > #define DECAF_MAX_TLS_SLOTS 256 in ThreadTypes.h seems to impose a limit of > 51 connections for a CMS client on our systems because of its use with > threading. We would like to request this number be increased a larger value, > such as 1536, to allow a client to maintain additional connections. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQCPP-628) std::auto_ptr has been removed in C++17
[ https://issues.apache.org/jira/browse/AMQCPP-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQCPP-628. --- Resolution: Won't Fix > std::auto_ptr has been removed in C++17 > --- > > Key: AMQCPP-628 > URL: https://issues.apache.org/jira/browse/AMQCPP-628 > Project: ActiveMQ C++ Client > Issue Type: Improvement > Components: CMS Impl >Reporter: Hermann Walth >Priority: Major > Attachments: AMQCPP-628.patch > > > Compiling ActiveMQ-cpp when the compiler flag to enable the C++ 17 standard > is set will result in compiler errors because ActiveMQ-cpp uses auto_ptr, > which has been removed in C++ 17. > More importantly, compiling any project that _uses_ ActiveMQ-cpp with a > C++17-compliant compiler will fail because std::auto_ptr is used in the > ActiveMQ headers. > Please replace all occurrences of std::auto_ptr with std::unique_ptr. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQCPP-606) CMS: Add support for AMQP
[ https://issues.apache.org/jira/browse/AMQCPP-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQCPP-606. --- Resolution: Won't Fix > CMS: Add support for AMQP > - > > Key: AMQCPP-606 > URL: https://issues.apache.org/jira/browse/AMQCPP-606 > Project: ActiveMQ C++ Client > Issue Type: New Feature > Components: CMS Impl >Reporter: Matt Pavlovich >Priority: Minor > > Add AMQP support to CMS in order to close a gap and provide uniform > programming API options for users looking to use the AMQP protocol. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQCPP-599) Support for proxy
[ https://issues.apache.org/jira/browse/AMQCPP-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQCPP-599. --- Resolution: Won't Fix > Support for proxy > - > > Key: AMQCPP-599 > URL: https://issues.apache.org/jira/browse/AMQCPP-599 > Project: ActiveMQ C++ Client > Issue Type: New Feature > Components: Decaf, Transports >Affects Versions: 3.9.2, 3.9.3 >Reporter: Francois Godin >Assignee: Timothy Bish >Priority: Major > Attachments: proxy.patch > > > ActiveMQ C++ does not support connecting to the broker via a HTTP (or sock, > or other) proxy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQCPP-605) ActiveMQ CPP clients don't support IPv6
[ https://issues.apache.org/jira/browse/AMQCPP-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQCPP-605. --- Resolution: Won't Fix > ActiveMQ CPP clients don't support IPv6 > --- > > Key: AMQCPP-605 > URL: https://issues.apache.org/jira/browse/AMQCPP-605 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: Decaf, Transports >Affects Versions: 3.9.3 >Reporter: MARIUS KAPEA >Assignee: Timothy Bish >Priority: Blocker > Attachments: feature_IPv6.patch > > > #ActiveMQ CPP 3.9.3 > We want to use ActiveMQ Cpp client with the IPv6 but we are facing an issue. > => There is no syntax error, but the client(Producer) is not sending > packets. > ActiveMQ broker supports IPv6 protocol. But the current ActiveMQ-CPP clients > don't. > I am wondering if today there is an issue related to the IPv6 on > ActiveMQ-CPP client? > Could you please help us? > Kind regards, > Marius -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AMQCPP-641) Getting core dump on activemq-cpp-library-3.7.0
[
https://issues.apache.org/jira/browse/AMQCPP-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQCPP-641.
---
Resolution: Invalid
Upgrade to the latest version and open issue based on that release, this
release is out of date
> Getting core dump on activemq-cpp-library-3.7.0
> ---
>
> Key: AMQCPP-641
> URL: https://issues.apache.org/jira/browse/AMQCPP-641
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Other C++ Clients
>Affects Versions: 3.7.0
> Environment: Linux RHEL6.10
>Reporter: Gaurav
>Assignee: Timothy Bish
>Priority: Major
>
> Hello,
> We are getting below core-dump sometime on our system running
> activemq-cpp-library-3.7.0.
> Any idea what can be done to resolve it?
>
> Thank you in advance.
>
> coredump backtrack:
> =
>
> #0 0x00337ebd in __dynamic_cast () from /usr/lib/libstdc++.so.6
> No symbol table info available.
> #1 0x016b0c8a in activemq::core::ActiveMQConnection::syncRequest
> (this=0xf4a10100, command=..., timeout=1) at
> activemq/core/ActiveMQConnection.cpp:1276
> response = \{ =
> {_vptr.AtomicRefCounter = 0x1d449a8, counter = 0xf3e27678}, value =
> 0xf6c20128, onDelete = 0x16c0430
> decaf::util::concurrent::atomic::AtomicRefCounter>::onDeleteFunc(activemq::commands::Response*)>}
> #2 0x016bd6c8 in activemq::core::ActiveMQConnection::disconnect
> (this=0xf4a10100, lastDeliveredSequenceId=0) at
> activemq/core/ActiveMQConnection.cpp:925
> hasException = false
> e = \{ = { =
> { = {}, }, data =
> 0xf3e276e8}, }
> #3 0x016be848 in activemq::core::ActiveMQConnection::close (this=0xf4a10100)
> at activemq/core/ActiveMQConnection.cpp:783
> ex = \{ = { = { fields>}, }, data = 0xf3e273a0}
> hasException = false
> lastDeliveredSequenceId = 0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (AMQ-7099) After upgrading activemq 5.5.1 to activemq 5.13.1, issues with java.security.Security.insertProviderAt/org.apache.activemq.broker.BrokerService
[ https://issues.apache.org/jira/browse/AMQ-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-7099. - Resolution: Invalid Please ask for support on the users mailing list > After upgrading activemq 5.5.1 to activemq 5.13.1, issues with > java.security.Security.insertProviderAt/org.apache.activemq.broker.BrokerService > > > Key: AMQ-7099 > URL: https://issues.apache.org/jira/browse/AMQ-7099 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.13.1 > Environment: OS: All platforms > Products involved are : > WAS 8.5.5.9 - 8.5.5.14 > LDAP/Active directory > JazzSM(DASH) 3.1.3 CP5 -CP7 >Reporter: sunil kumar >Priority: Blocker > > We upgraded activemq 5.5.1 to activemq 5.13.1 to over come the security > vulnerable to CVE-2015-5254 and CVE-2014-3612. for ref: here are the links > for each CVE: > [http://activemq.apache.org/security-advisories.data/CVE-2015-5254-announcement.txt?version=1=1449589734000=v2] > > [http://activemq.apache.org/security-advisories.data/CVE-2014-3612-announcement.txt?version=2=1423051365000=v2] > > After upgrading we hit with following issues while getting LDAP user > informations . > Following are the stack trace : > *16:06:07.353 0x33fb300 j9trc_aux.0 - jstacktrace:* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [1] > java.security.Security.insertProviderAt (Security.java:369)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [2] > org.apache.activemq.broker.BrokerService. (BrokerService.java:275)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [3] > com.ibm.tivoli.rest.event.amq.AMQPropertiesBrokerFactory.createBroker > (AMQPropertiesBrokerFactory.java:30)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [4] > org.apache.activemq.broker.BrokerFactory.createBroker (BrokerFactory.java:71)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [5] > org.apache.activemq.broker.BrokerFactory.createBroker (BrokerFactory.java:54)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [6] > com.ibm.tivoli.rest.event.amq.AMQEventRouterFactory.startBroker > (AMQEventRouterFactory.java:430)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [7] > com.ibm.tivoli.rest.event.amq.AMQEventRouterFactory.start > (AMQEventRouterFactory.java:151)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [8] > com.ibm.tivoli.rest.event.EventRouterFactory.getInstance > (EventRouterFactory.java:43)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [9] > com.ibm.tivoli.rest.amq.AjaxServlet. (AjaxServlet.java:59)* > *16:06:07.353 0x33fb300 j9trc_aux.1 - [10] > java.lang.J9VMInternals.newInstanceImpl (Native Method)* > 16:06:07.353 0x33fb300 j9trc_aux.1 - [11] java.lang.Class.newInstance > (Class.java:1843) (Compiled Code) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [12] java.beans.Beans.instantiate > (Beans.java:240) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [13] java.beans.Beans.instantiate > (Beans.java:88) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [14] > com.ibm.ws.webcontainer.servlet.ServletWrapper$1.run > (ServletWrapper.java:1489) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [15] > com.ibm.ws.security.util.AccessController.doPrivileged > (AccessController.java:118) (Compiled Code) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [16] > com.ibm.ws.webcontainer.servlet.ServletWrapper.loadServlet > (ServletWrapper.java:1478) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [17] > com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck > (ServletWrapper.java:1357) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [18] > com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions (WebApp.java:642) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [19] > com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally > (WebApp.java:608) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [20] > com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize (WebAppImpl.java:426) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [21] > com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication > (WebGroupImpl.java:88) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [22] > com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication > (VirtualHostImpl.java:171) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [23] > com.ibm.ws.webcontainer.WSWebContainer.addWebApp (WSWebContainer.java:904) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [24] > com.ibm.ws.webcontainer.WSWebContainer.addWebApplication > (WSWebContainer.java:789) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [25] > com.ibm.ws.webcontainer.component.WebContainerImpl.install > (WebContainerImpl.java:427) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [26] > com.ibm.ws.webcontainer.component.WebContainerImpl.start > (WebContainerImpl.java:719) > 16:06:07.353 0x33fb300 j9trc_aux.1 - [27] >
[jira] [Commented] (AMQCPP-641) Getting core dump on activemq-cpp-library-3.7.0
[
https://issues.apache.org/jira/browse/AMQCPP-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687989#comment-16687989
]
Timothy Bish commented on AMQCPP-641:
-
Could be AMQCPP-490 or one of the other fixes that have gone into releases that
came later, I'd recommend updating to the latest release
> Getting core dump on activemq-cpp-library-3.7.0
> ---
>
> Key: AMQCPP-641
> URL: https://issues.apache.org/jira/browse/AMQCPP-641
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Other C++ Clients
>Affects Versions: 3.7.0
> Environment: Linux RHEL6.10
>Reporter: Gaurav
>Assignee: Timothy Bish
>Priority: Major
>
> Hello,
> We are getting below core-dump sometime on our system running
> activemq-cpp-library-3.7.0.
> Any idea what can be done to resolve it?
>
> Thank you in advance.
>
> coredump backtrack:
> =
>
> #0 0x00337ebd in __dynamic_cast () from /usr/lib/libstdc++.so.6
> No symbol table info available.
> #1 0x016b0c8a in activemq::core::ActiveMQConnection::syncRequest
> (this=0xf4a10100, command=..., timeout=1) at
> activemq/core/ActiveMQConnection.cpp:1276
> response = \{ =
> {_vptr.AtomicRefCounter = 0x1d449a8, counter = 0xf3e27678}, value =
> 0xf6c20128, onDelete = 0x16c0430
> decaf::util::concurrent::atomic::AtomicRefCounter>::onDeleteFunc(activemq::commands::Response*)>}
> #2 0x016bd6c8 in activemq::core::ActiveMQConnection::disconnect
> (this=0xf4a10100, lastDeliveredSequenceId=0) at
> activemq/core/ActiveMQConnection.cpp:925
> hasException = false
> e = \{ = { =
> { = {}, }, data =
> 0xf3e276e8}, }
> #3 0x016be848 in activemq::core::ActiveMQConnection::close (this=0xf4a10100)
> at activemq/core/ActiveMQConnection.cpp:783
> ex = \{ = { = { fields>}, }, data = 0xf3e273a0}
> hasException = false
> lastDeliveredSequenceId = 0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMQ-7097) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
[ https://issues.apache.org/jira/browse/AMQ-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686517#comment-16686517 ] Timothy Bish commented on AMQ-7097: --- This can wait until the next release as the JMS release is still a day or two away. > AMQP: Update Qpid JMS, Proton-J and Netty to latest releases > > > Key: AMQ-7097 > URL: https://issues.apache.org/jira/browse/AMQ-7097 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.7 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 5.15.9 > > > Update AMQP libraries to latest > * Qpid JMS 0.38.0 > * Proton-j 0.30.0 > * Netty 4.1.31.Final -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7097) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
[ https://issues.apache.org/jira/browse/AMQ-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-7097: -- Fix Version/s: (was: 5.15.8) 5.15.9 > AMQP: Update Qpid JMS, Proton-J and Netty to latest releases > > > Key: AMQ-7097 > URL: https://issues.apache.org/jira/browse/AMQ-7097 > Project: ActiveMQ > Issue Type: Task > Components: AMQP >Affects Versions: 5.15.7 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 5.15.9 > > > Update AMQP libraries to latest > * Qpid JMS 0.38.0 > * Proton-j 0.30.0 > * Netty 4.1.31.Final -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQ-7097) AMQP: Update Qpid JMS, Proton-J and Netty to latest releases
Timothy Bish created AMQ-7097: - Summary: AMQP: Update Qpid JMS, Proton-J and Netty to latest releases Key: AMQ-7097 URL: https://issues.apache.org/jira/browse/AMQ-7097 Project: ActiveMQ Issue Type: Task Components: AMQP Affects Versions: 5.15.7 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 5.15.8 Update AMQP libraries to latest * Qpid JMS 0.38.0 * Proton-j 0.30.0 * Netty 4.1.31.Final -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7091) O(n) Memory consumption when broker has inactive durable subscribes causing OOM
[ https://issues.apache.org/jira/browse/AMQ-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16684019#comment-16684019 ] Timothy Bish commented on AMQ-7091: --- [~gtully] I'm afraid I don't recall any longer what the context was for that work. > O(n) Memory consumption when broker has inactive durable subscribes causing > OOM > --- > > Key: AMQ-7091 > URL: https://issues.apache.org/jira/browse/AMQ-7091 > Project: ActiveMQ > Issue Type: Bug > Components: KahaDB >Affects Versions: 5.15.7 >Reporter: Alan Protasio >Priority: Major > Attachments: After.png, Before.png, > InactiveDurableSubscriberTest.java, memoryAllocation.jpg > > > Hi :D > One of our brokers was bouncing indefinitely due OOM even though the load > (TPS) was pretty low. > Getting the memory dump I could see that almost 90% of the memory was being > used by > [messageReferences|https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/MessageDatabase.java#L2368] > TreeMap to keep track of what messages were already acked by all Subscribes > in order to delete them. > This seems to be a problem as if the broker has an inactive durable > subscribe, the memory footprint increase proportionally (O) with the number > of messages sent to the topic in question, causing the broker to die due OOM > sooner or later (the high memory footprint continue even after a restart). > You can find attached (memoryAllocation.jpg) a screen shot showing my broker > using 90% of the memory to keep track of those messages, making it barely > usable. > Looking at the code, I could do a change to change the messageReferences to > use a BTreeIndex: > final TreeMap messageReferences = new TreeMap<>(); > + BTreeIndex messageReferences; > Making this change, the memory allocation of the broker stabilized and the > broker didn't run OOM anymore. > Attached you can see the code that I used to reproduce this scenario, also > the memory utilization (HEAP and GC graphs) before and after this change. > Before the change the broker died in 5 minutes and I could send 48. After > then change the broker was still pretty healthy after 5 minutes and i could > send 2265000 to the topic (almost 5x more due high GC pauses). > > All test are passing: mvn clean install -Dactivemq.tests=all -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARTEMIS-2146) Broker throws exception and becomes unresponsive during AMQP messaging
[
https://issues.apache.org/jira/browse/ARTEMIS-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved ARTEMIS-2146.
---
Resolution: Fixed
> Broker throws exception and becomes unresponsive during AMQP messaging
> --
>
> Key: ARTEMIS-2146
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2146
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.6.3
>Reporter: Timothy Bish
>Assignee: clebert suconic
>Priority: Major
> Fix For: 2.7.0, 2.6.4
>
>
> While testing two different AMQP clients communicating on a single broker
> instance the broker can throw the below error and become crippled afterwards
> requiring a restart to get back to normal operation.
> {noformat}
> 2018-10-23 10:29:49,863 INFO [org.apache.activemq.artemis.core.server]
> AMQ221007: Server is now live
> 2018-10-23 10:29:49,863 INFO [org.apache.activemq.artemis.core.server]
> AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.7.0-SNAPSHOT
> [0.0.0.0, nodeID=18aef23b-d6d0-11e8-b6ff-2c56dc3896a2]
> 2018-10-23 10:29:50,008 INFO
> [org.apache.activemq.hawtio.branding.PluginContextListener] Initialized
> activemq-branding plugin
> 2018-10-23 10:29:50,042 INFO
> [org.apache.activemq.hawtio.plugin.PluginContextListener] Initialized
> artemis-plugin plugin
> 2018-10-23 10:29:50,247 INFO [io.hawt.HawtioContextListener] Initialising
> hawtio services
> 2018-10-23 10:29:50,257 INFO [io.hawt.system.ConfigManager] Configuration
> will be discovered via system properties
> 2018-10-23 10:29:50,259 INFO [io.hawt.jmx.JmxTreeWatcher] Welcome to hawtio
> 1.5.5 : http://hawt.io/ : Don't cha wish your console was hawt like me? ;-)
> 2018-10-23 10:29:50,261 INFO [io.hawt.jmx.UploadManager] Using file upload
> directory: /home/timothy/dev/activemq-artemis/amqp/tmp/uploads
> 2018-10-23 10:29:50,272 INFO [io.hawt.web.AuthenticationFilter] Starting
> hawtio authentication filter, JAAS realm: "activemq" authorized role(s):
> "amq" role principal classes:
> "org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal"
> 2018-10-23 10:29:50,293 INFO [io.hawt.web.JolokiaConfiguredAgentServlet]
> Jolokia overridden property: [key=policyLocation,
> value=file:/home/timothy/dev/activemq-artemis/amqp/etc/jolokia-access.xml]
> 2018-10-23 10:29:50,311 INFO [io.hawt.web.RBACMBeanInvoker] Using MBean
> [hawtio:type=security,area=jmx,rank=0,name=HawtioDummyJMXSecurity] for role
> based access control
> 2018-10-23 10:29:50,521 INFO [io.hawt.system.ProxyWhitelist] Initial proxy
> whitelist: [localhost, 127.0.0.1, 192.168.2.150, 10.10.124.116,
> ovpn-124-116.rdu2.redhat.com]
> 2018-10-23 10:29:50,666 INFO [org.apache.activemq.artemis] AMQ241001: HTTP
> Server started at http://localhost:8161
> 2018-10-23 10:29:50,666 INFO [org.apache.activemq.artemis] AMQ241002:
> Artemis Jolokia REST API available at http://localhost:8161/console/jolokia
> 2018-10-23 10:29:50,666 INFO [org.apache.activemq.artemis] AMQ241004:
> Artemis Console available at http://localhost:8161/console
> 2018-10-23 10:37:53,162 WARN [org.apache.activemq.artemis.core.server]
> AMQ222151: removing consumer which did not handle a message,
> consumer=ServerConsumerImpl [id=0, filter=null, binding=LocalQueueBinding
> [address=q0, queue=QueueImpl[name=q0, postOffice=PostOfficeImpl
> [server=ActiveMQServerImpl::serverUUID=18aef23b-d6d0-11e8-b6ff-2c56dc3896a2],
> temp=false]@31eabbcf, filter=null, name=q0,
> clusterName=q018aef23b-d6d0-11e8-b6ff-2c56dc3896a2]],
> message=Reference[4080]:NON-RELIABLE:AMQPMessage [durable=false,
> messageID=4080, address=q0, size=271, applicationProperties=null,
> properties=Properties{messageId=ID:822fd816-a7dc-4a54-a39f-ea9798995135:1:1:1-1,
> userId=null, to='q0', subject='null', replyTo='null', correlationId=null,
> contentType=application/octet-stream, contentEncoding=null,
> absoluteExpiryTime=null, creationTime=null, groupId='null',
> groupSequence=null, replyToGroupId='null'}, extraProperties =
> TypedProperties[_AMQ_AD=q0]]: java.lang.NullPointerException
> at
> org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.handle(ServerConsumerImpl.java:352)
> [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.handle(QueueImpl.java:3173)
> [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.deliver(QueueImpl.java:2515)
> [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.access$2100(QueueImpl.java:111)
> [artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
> at
>
[jira] [Created] (ARTEMIS-2146) Broker throws exception and becomes unresponsive during AMQP messaging
Timothy Bish created ARTEMIS-2146:
-
Summary: Broker throws exception and becomes unresponsive during
AMQP messaging
Key: ARTEMIS-2146
URL: https://issues.apache.org/jira/browse/ARTEMIS-2146
Project: ActiveMQ Artemis
Issue Type: Bug
Components: AMQP
Affects Versions: 2.6.3
Reporter: Timothy Bish
Fix For: 2.6.4
While testing two different AMQP clients communicating on a single broker
instance the broker can throw the below error and become crippled afterwards
requiring a restart to get back to normal operation.
{noformat}
2018-10-23 10:29:49,863 INFO [org.apache.activemq.artemis.core.server]
AMQ221007: Server is now live
2018-10-23 10:29:49,863 INFO [org.apache.activemq.artemis.core.server]
AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.7.0-SNAPSHOT
[0.0.0.0, nodeID=18aef23b-d6d0-11e8-b6ff-2c56dc3896a2]
2018-10-23 10:29:50,008 INFO
[org.apache.activemq.hawtio.branding.PluginContextListener] Initialized
activemq-branding plugin
2018-10-23 10:29:50,042 INFO
[org.apache.activemq.hawtio.plugin.PluginContextListener] Initialized
artemis-plugin plugin
2018-10-23 10:29:50,247 INFO [io.hawt.HawtioContextListener] Initialising
hawtio services
2018-10-23 10:29:50,257 INFO [io.hawt.system.ConfigManager] Configuration will
be discovered via system properties
2018-10-23 10:29:50,259 INFO [io.hawt.jmx.JmxTreeWatcher] Welcome to hawtio
1.5.5 : http://hawt.io/ : Don't cha wish your console was hawt like me? ;-)
2018-10-23 10:29:50,261 INFO [io.hawt.jmx.UploadManager] Using file upload
directory: /home/timothy/dev/activemq-artemis/amqp/tmp/uploads
2018-10-23 10:29:50,272 INFO [io.hawt.web.AuthenticationFilter] Starting
hawtio authentication filter, JAAS realm: "activemq" authorized role(s): "amq"
role principal classes:
"org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal"
2018-10-23 10:29:50,293 INFO [io.hawt.web.JolokiaConfiguredAgentServlet]
Jolokia overridden property: [key=policyLocation,
value=file:/home/timothy/dev/activemq-artemis/amqp/etc/jolokia-access.xml]
2018-10-23 10:29:50,311 INFO [io.hawt.web.RBACMBeanInvoker] Using MBean
[hawtio:type=security,area=jmx,rank=0,name=HawtioDummyJMXSecurity] for role
based access control
2018-10-23 10:29:50,521 INFO [io.hawt.system.ProxyWhitelist] Initial proxy
whitelist: [localhost, 127.0.0.1, 192.168.2.150, 10.10.124.116,
ovpn-124-116.rdu2.redhat.com]
2018-10-23 10:29:50,666 INFO [org.apache.activemq.artemis] AMQ241001: HTTP
Server started at http://localhost:8161
2018-10-23 10:29:50,666 INFO [org.apache.activemq.artemis] AMQ241002: Artemis
Jolokia REST API available at http://localhost:8161/console/jolokia
2018-10-23 10:29:50,666 INFO [org.apache.activemq.artemis] AMQ241004: Artemis
Console available at http://localhost:8161/console
2018-10-23 10:37:53,162 WARN [org.apache.activemq.artemis.core.server]
AMQ222151: removing consumer which did not handle a message,
consumer=ServerConsumerImpl [id=0, filter=null, binding=LocalQueueBinding
[address=q0, queue=QueueImpl[name=q0, postOffice=PostOfficeImpl
[server=ActiveMQServerImpl::serverUUID=18aef23b-d6d0-11e8-b6ff-2c56dc3896a2],
temp=false]@31eabbcf, filter=null, name=q0,
clusterName=q018aef23b-d6d0-11e8-b6ff-2c56dc3896a2]],
message=Reference[4080]:NON-RELIABLE:AMQPMessage [durable=false,
messageID=4080, address=q0, size=271, applicationProperties=null,
properties=Properties{messageId=ID:822fd816-a7dc-4a54-a39f-ea9798995135:1:1:1-1,
userId=null, to='q0', subject='null', replyTo='null', correlationId=null,
contentType=application/octet-stream, contentEncoding=null,
absoluteExpiryTime=null, creationTime=null, groupId='null', groupSequence=null,
replyToGroupId='null'}, extraProperties = TypedProperties[_AMQ_AD=q0]]:
java.lang.NullPointerException
at
org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.handle(ServerConsumerImpl.java:352)
[artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.handle(QueueImpl.java:3173)
[artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.deliver(QueueImpl.java:2515)
[artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl.access$2100(QueueImpl.java:111)
[artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at
org.apache.activemq.artemis.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:3410)
[artemis-server-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
[artemis-commons-2.7.0-SNAPSHOT.jar:2.7.0-SNAPSHOT]
at
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
[jira] [Commented] (AMQ-7072) ActiveMQ shouldn't import jackson but use JSON-B instead of jackson to support impl switch
[
https://issues.apache.org/jira/browse/AMQ-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650313#comment-16650313
]
Timothy Bish commented on AMQ-7072:
---
Agree with [~cshannon] on this, the default ought to remain as it is now
Jackson. We could make the provider implementation swappable on master for a
future 5.16.0 release, that makes sense.
We shouldn't be changing out things like this on the patch branch though.
> ActiveMQ shouldn't import jackson but use JSON-B instead of jackson to
> support impl switch
> --
>
> Key: AMQ-7072
> URL: https://issues.apache.org/jira/browse/AMQ-7072
> Project: ActiveMQ
> Issue Type: Improvement
>Reporter: Romain Manni-Bucau
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.16.0
>
>
> The regression we hit at the moment is that activemq enforces TomEE to import
> jackson whereas it wants to keep johnzon as JSON mapper impl. Since JSON-B
> spec is out and implemented by both I guess it can be the way to solve that
> issue.
> The most blocking thing is
> ./activemq-broker/src/main/java/org/apache/activemq/broker/jmx/DestinationsViewFilter.java
> - which can already not create a mapper if json is empty ;) - but here is
> the list of code location which would be neat to fix:
> {code}
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.annotation.JsonInclude;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.DeserializationFeature;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.ObjectMapper;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.DeserializationConfig;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.SerializationFeature;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.annotation.JsonDeserialize;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.annotation.JsonSerialize;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.annotation.JsonProperty;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Target.java:import
> com.fasterxml.jackson.annotation.JsonProperty;
> ./activemq-broker/src/main/java/org/apache/activemq/broker/jmx/DestinationsViewFilter.java:import
> com.fasterxml.jackson.databind.ObjectMapper;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/LogWrite.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/WalAck.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/LogDelete.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/Transfer.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/Login.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMQ-7072) ActiveMQ shouldn't import jackson but use JSON-B instead of jackson to support impl switch
[
https://issues.apache.org/jira/browse/AMQ-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-7072:
--
Fix Version/s: (was: 5.15.7)
> ActiveMQ shouldn't import jackson but use JSON-B instead of jackson to
> support impl switch
> --
>
> Key: AMQ-7072
> URL: https://issues.apache.org/jira/browse/AMQ-7072
> Project: ActiveMQ
> Issue Type: Improvement
>Reporter: Romain Manni-Bucau
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.16.0
>
>
> The regression we hit at the moment is that activemq enforces TomEE to import
> jackson whereas it wants to keep johnzon as JSON mapper impl. Since JSON-B
> spec is out and implemented by both I guess it can be the way to solve that
> issue.
> The most blocking thing is
> ./activemq-broker/src/main/java/org/apache/activemq/broker/jmx/DestinationsViewFilter.java
> - which can already not create a mapper if json is empty ;) - but here is
> the list of code location which would be neat to fix:
> {code}
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.annotation.JsonInclude;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.DeserializationFeature;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.ObjectMapper;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.DeserializationConfig;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.SerializationFeature;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.annotation.JsonDeserialize;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.databind.annotation.JsonSerialize;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Partitioning.java:import
> com.fasterxml.jackson.annotation.JsonProperty;
> ./activemq-partition/src/main/java/org/apache/activemq/partition/dto/Target.java:import
> com.fasterxml.jackson.annotation.JsonProperty;
> ./activemq-broker/src/main/java/org/apache/activemq/broker/jmx/DestinationsViewFilter.java:import
> com.fasterxml.jackson.databind.ObjectMapper;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/LogWrite.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/WalAck.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/LogDelete.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/Transfer.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> ./activemq-leveldb-store/src/main/java/org/apache/activemq/leveldb/replicated/dto/Login.java:import
> com.fasterxml.jackson.annotation.JsonIgnoreProperties;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMQ-7068) Advisory messages are empty when received with a AMQP subscription
[ https://issues.apache.org/jira/browse/AMQ-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643449#comment-16643449 ] Timothy Bish commented on AMQ-7068: --- Yes, you can send PRs to the github repository for review > Advisory messages are empty when received with a AMQP subscription > -- > > Key: AMQ-7068 > URL: https://issues.apache.org/jira/browse/AMQ-7068 > Project: ActiveMQ > Issue Type: New Feature > Components: AMQP, Transport >Affects Versions: 5.15.6 > Environment: ActiveMQ 5.15.6, JDK 1.8.0_161, Windows 10, AMQPNetLite > 2.1.4 >Reporter: Johannes Baeurle >Priority: Minor > Attachments: issueamq.PNG, issueamq2.PNG, issueamq3.PNG > > > We are currently moving from OpenWire to AMQP with .NET Library amqpnetlite > ([https://github.com/Azure/amqpnetlite)] to communicate. So far most things > work fine, but we actively used and need the advisory messages in order to > recognize if other clients disconnect for example. > Accessing the advisory messages through the topic is not the problem, but the > body is null for the ActiveMQ.Advisory.Connection topic. There are some > properties set, but no body set and I'm not able to find any important > information, like the RemoveInfo. I attached a few screenshots from debugger. > To be honest, I don't know if this is the desired behavior, but I think if > there are messages on the advisory topic they should be useful. > I know that a byte representation wouldn't be that useful, but you could > present the information in json or xml format, like in Stomp? > (https://issues.apache.org/jira/browse/AMQ-2098) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7068) Advisory messages are empty when received with a AMQP subscription
[ https://issues.apache.org/jira/browse/AMQ-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641728#comment-16641728 ] Timothy Bish commented on AMQ-7068: --- Representing the OpenWire protocol objects in the AMQP body requires some work to produce conversions of the data into some types that can be marshalled in the AMQP protocol's type system. Currently no proper mapping has been done but if you want to contribute it we'd be happy to accept the patches. You'd likely need to convert the types into Map representations for the broadest comparability, XML would work but would be harder for folks to deal with than a simple mapping. > Advisory messages are empty when received with a AMQP subscription > -- > > Key: AMQ-7068 > URL: https://issues.apache.org/jira/browse/AMQ-7068 > Project: ActiveMQ > Issue Type: New Feature > Components: AMQP, Transport >Affects Versions: 5.15.6 > Environment: ActiveMQ 5.15.6, JDK 1.8.0_161, Windows 10, AMQPNetLite > 2.1.4 >Reporter: Johannes Baeurle >Priority: Minor > Attachments: issueamq.PNG, issueamq2.PNG, issueamq3.PNG > > > We are currently moving from OpenWire to AMQP with .NET Library amqpnetlite > ([https://github.com/Azure/amqpnetlite)] to communicate. So far most things > work fine, but we actively used and need the advisory messages in order to > recognize if other clients disconnect for example. > Accessing the advisory messages through the topic is not the problem, but the > body is null for the ActiveMQ.Advisory.Connection topic. There are some > properties set, but no body set and I'm not able to find any important > information, like the RemoveInfo. I attached a few screenshots from debugger. > To be honest, I don't know if this is the desired behavior, but I think if > there are messages on the advisory topic they should be useful. > I know that a byte representation wouldn't be that useful, but you could > present the information in json or xml format, like in Stomp? > (https://issues.apache.org/jira/browse/AMQ-2098) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7068) Advisory messages are empty when received with a AMQP subscription
[ https://issues.apache.org/jira/browse/AMQ-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-7068: -- Priority: Minor (was: Major) > Advisory messages are empty when received with a AMQP subscription > -- > > Key: AMQ-7068 > URL: https://issues.apache.org/jira/browse/AMQ-7068 > Project: ActiveMQ > Issue Type: New Feature > Components: AMQP, Transport >Affects Versions: 5.15.6 > Environment: ActiveMQ 5.15.6, JDK 1.8.0_161, Windows 10, AMQPNetLite > 2.1.4 >Reporter: Johannes Baeurle >Priority: Minor > Attachments: issueamq.PNG, issueamq2.PNG, issueamq3.PNG > > > We are currently moving from OpenWire to AMQP with .NET Library amqpnetlite > ([https://github.com/Azure/amqpnetlite)] to communicate. So far most things > work fine, but we actively used and need the advisory messages in order to > recognize if other clients disconnect for example. > Accessing the advisory messages through the topic is not the problem, but the > body is null for the ActiveMQ.Advisory.Connection topic. There are some > properties set, but no body set and I'm not able to find any important > information, like the RemoveInfo. I attached a few screenshots from debugger. > To be honest, I don't know if this is the desired behavior, but I think if > there are messages on the advisory topic they should be useful. > I know that a byte representation wouldn't be that useful, but you could > present the information in json or xml format, like in Stomp? > (https://issues.apache.org/jira/browse/AMQ-2098) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
