[jira] [Resolved] (AMQ-5360) mqtt-doc: Wild card mapping tables in the doc is wrong

[ https://issues.apache.org/jira/browse/AMQ-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5360. --- Resolution: Fixed > mqtt-doc: Wild card mapping tables in the doc is wr

[ANNOUNCE] Apache.NMS.ActiveMQ 1.6.4 Released

Hello The Apache.NMS.ActiveMQ 1.6.4 Release bundle is now available. This is a bugfix release that includes some stability fixes for issues found since the v1.6.3 release along with a hardening of the local transaction support for MessageConsumer instances. The Wiki Page for this release is

[jira] [Commented] (AMQ-5358) MQTT Durable subscription broken in 5.10 and 5.11

[ https://issues.apache.org/jira/browse/AMQ-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134794#comment-14134794 ] Timothy Bish commented on AMQ-5358: --- You'd need to confirm that with the MQTT s

[jira] [Commented] (AMQ-5358) MQTT Durable subscription broken in 5.10 and 5.11

[ https://issues.apache.org/jira/browse/AMQ-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134608#comment-14134608 ] Timothy Bish commented on AMQ-5358: --- Your subscription is actually only se

[jira] [Commented] (AMQ-5358) MQTT Durable subscription broken in 5.10 and 5.11

[ https://issues.apache.org/jira/browse/AMQ-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134543#comment-14134543 ] Timothy Bish commented on AMQ-5358: --- Ran your test against 5.11-SNAPSHOT and it pa

[jira] [Commented] (AMQ-5358) MQTT Durable subscription broken in 5.10 and 5.11

[ https://issues.apache.org/jira/browse/AMQ-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134522#comment-14134522 ] Timothy Bish commented on AMQ-5358: --- When you say, "does not work" what be

[jira] [Commented] (AMQ-5357) Race conditions in ActiveMQ Connection Pooling

[ https://issues.apache.org/jira/browse/AMQ-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133992#comment-14133992 ] Timothy Bish commented on AMQ-5357: --- Would recommend you test against 5.11-SNAPSHO

[jira] [Commented] (AMQ-5357) Race conditions in ActiveMQ Connection Pooling

[ https://issues.apache.org/jira/browse/AMQ-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133943#comment-14133943 ] Timothy Bish commented on AMQ-5357: --- >From the information given it seems li

[jira] [Commented] (AMQ-5357) Race conditions in ActiveMQ Connection Pooling

[ https://issues.apache.org/jira/browse/AMQ-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133878#comment-14133878 ] Timothy Bish commented on AMQ-5357: --- Recommend you create a unit test that demonstr

[jira] [Closed] (AMQ-5355) Problem in making JNDI connection - Apachive ActiveMQ 5.10.0

[ https://issues.apache.org/jira/browse/AMQ-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5355. - Resolution: Invalid This should go to the Users mailing list. > Problem in making JNDI connect

[RESULT][VOTE] Release Apache.NMS.ActiveMQ 1.6.4

Results of the Apache.NMS.ActiveMQ 1.6.4 vote: Vote passes with 6 +1 and no other votes. The following votes were received: Timothy Bish Jim Gomes Claus Ibsen Dejan Bosanac Gary Tully Hiram Chirino I'll start pushing out the release bundles and update the Wiki. -- Tim Bish Sr Sof

Re: Confluence and publication

On 09/10/2014 01:29 PM, vromero wrote: Last weekend I tried my confluence kung-fu improving a little bit the Queue consumer cluster section of the clustering page . My change has been saved in confluence for a few days and it does appear as lastest

[jira] [Commented] (AMQ-5185) Duplicate messages occur for MQTT cleanSession=false client with network of brokers

[ https://issues.apache.org/jira/browse/AMQ-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127845#comment-14127845 ] Timothy Bish commented on AMQ-5185: --- The workaround transparently subscribes the con

[jira] [Resolved] (AMQ-5352) AMQP messages published transactionally should be accepted using a TransactionalState

[ https://issues.apache.org/jira/browse/AMQ-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5352. --- Resolution: Fixed Fix Version/s: 5.11.0 Fixed on trunk. > AMQP messages publis

[jira] [Assigned] (AMQ-5352) AMQP messages published transactionally should be accepted using a TransactionalState

[ https://issues.apache.org/jira/browse/AMQ-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQ-5352: - Assignee: Timothy Bish > AMQP messages published transactionally should be accepted usin

[jira] [Commented] (AMQ-5350) Separate the AMQP maxFrameSize setting from the WireFormat maxFrameSize setting.

[ https://issues.apache.org/jira/browse/AMQ-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127126#comment-14127126 ] Timothy Bish commented on AMQ-5350: --- No, it's not set unless the U

[jira] [Resolved] (AMQ-5350) Separate the AMQP maxFrameSize setting from the WireFormat maxFrameSize setting.

[ https://issues.apache.org/jira/browse/AMQ-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5350. --- Resolution: Fixed Fixed on trunk. > Separate the AMQP maxFrameSize setting from the WireFor

[jira] [Created] (AMQ-5350) Separate the AMQP maxFrameSize setting from the WireFormat maxFrameSize setting.

Timothy Bish created AMQ-5350: - Summary: Separate the AMQP maxFrameSize setting from the WireFormat maxFrameSize setting. Key: AMQ-5350 URL: https://issues.apache.org/jira/browse/AMQ-5350 Project

[jira] [Created] (AMQ-5346) Update Proton to version 0.8

Timothy Bish created AMQ-5346: - Summary: Update Proton to version 0.8 Key: AMQ-5346 URL: https://issues.apache.org/jira/browse/AMQ-5346 Project: ActiveMQ Issue Type: Improvement

{VOTE] Release Apache.NMS.ActiveMQ 1.6.4

Hello This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.4 This is a bug fix only release focusing on some issues with Consumers in local transacted sessions where messages were getting marked as duplicates in error after failover and some other edge cases that could lead to

[jira] [Commented] (AMQ-5343) org.apache.activemq.thread.PooledTaskRunner.shutdown Waiting state

[ https://issues.apache.org/jira/browse/AMQ-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122021#comment-14122021 ] Timothy Bish commented on AMQ-5343: --- A unit test to reproduce this will help anyone

[jira] [Closed] (AMQ-5330) MQTT unsubscribe command doesn't remove durable subscriber from topic

[ https://issues.apache.org/jira/browse/AMQ-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5330. - Resolution: Fixed > MQTT unsubscribe command doesn't remove durable subscriber fr

Re: "wireFormat.host" option for StompSslTransportFactory

On 08/29/2014 05:54 PM, opks wrote: I got the following error message: "Invalid connect parameters: {wireFormat.host=localhost}" jmsTemplate is configured using stomp+ssl: jmsTemplate.setConnectionFactory(new ActiveMQConnectionFactory("stomp+ssl://localhost:61614?trace=true")); The error ha

Re: Documentation edit rights

On 09/02/2014 11:12 AM, vromero wrote: tabish...@gmail.com wrote Sorry for the delay in getting back to you on this, what's your account on the Apache Confluence Wiki? vromero? No worries at all, yes my account is: vromero. Thanks! -- View this message in context: http://activemq.2283324

Re: Documentation edit rights

On 09/02/2014 10:22 AM, vromero wrote: Any help would be greatly appretiated. -- View this message in context: http://activemq.2283324.n4.nabble.com/Documentation-edit-rights-tp4685055p4685232.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. Sorry for the delay in gettin

[jira] [Resolved] (AMQ-5337) Bug in ConcurrentLinkedQueue leads to excessive CPU-consumption by ActiveMQ process

[ https://issues.apache.org/jira/browse/AMQ-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5337. --- Resolution: Fixed Fix Version/s: 5.11.0 In light of the concerns here about OOM issues with the

[jira] [Commented] (AMQNET-472) Synchronous DTC Consumer will experience duplicates on transaction rollback

[ https://issues.apache.org/jira/browse/AMQNET-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115461#comment-14115461 ] Timothy Bish commented on AMQNET-472: - Took a stab at applying this patch an

[jira] [Resolved] (AMQNET-474) DTC Consumer is forcibly closed if a transaction is in progress and connection to the broker is interrupted

[ https://issues.apache.org/jira/browse/AMQNET-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-474. - Resolution: Fixed Fix Version/s: 1.7.0 1.6.4 Fire error events via

[jira] [Assigned] (AMQNET-474) DTC Consumer is forcibly closed if a transaction is in progress and connection to the broker is interrupted

[ https://issues.apache.org/jira/browse/AMQNET-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQNET-474: --- Assignee: Timothy Bish (was: Jim Gomes) > DTC Consumer is forcibly closed if a transact

[jira] [Resolved] (AMQ-5315) NullPointerException in DemandForwardingBridgeSupport.collectBrokerInfos

[ https://issues.apache.org/jira/browse/AMQ-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5315. --- Resolution: Fixed Should be fixed now, thanks for the test case. > NullPointerException

[jira] [Closed] (AMQNET-461) FailoverTransport PoisonAcks Rollbacked messages

[ https://issues.apache.org/jira/browse/AMQNET-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQNET-461. --- Resolution: Cannot Reproduce Assignee: Timothy Bish (was: Jim Gomes) Attempted to reproduce

[jira] [Resolved] (AMQNET-471) Synchronous message consumer will lose a message that failed to commit whilst the broker was unavailable

[ https://issues.apache.org/jira/browse/AMQNET-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-471. - Resolution: Fixed Fixed on trunk and 1.6.x branch. The separate rollback call in the exception

[jira] [Updated] (AMQNET-471) Synchronous message consumer will lose a message that failed to commit whilst the broker was unavailable

[ https://issues.apache.org/jira/browse/AMQNET-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-471: Fix Version/s: 1.7.0 1.6.4 > Synchronous message consumer will lose a mess

[jira] [Updated] (AMQ-5334) map massage properties with surrogates failing against JDK 8

[ https://issues.apache.org/jira/browse/AMQ-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5334: -- Priority: Minor (was: Major) > map massage properties with surrogates failing against JD

[jira] [Updated] (AMQ-5334) map massage properties with surrogates failing against JDK 8

[ https://issues.apache.org/jira/browse/AMQ-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5334: -- Fix Version/s: (was: 5.10.0) > map massage properties with surrogates failing against JD

[jira] [Assigned] (AMQNET-471) Synchronous message consumer will lose a message that failed to commit whilst the broker was unavailable

[ https://issues.apache.org/jira/browse/AMQNET-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQNET-471: --- Assignee: Timothy Bish (was: Jim Gomes) > Synchronous message consumer will lose a mess

[jira] [Created] (AMQCPP-552) Honor RedeliveryPolicy for message redelivered by the Broker.

Timothy Bish created AMQCPP-552: --- Summary: Honor RedeliveryPolicy for message redelivered by the Broker. Key: AMQCPP-552 URL: https://issues.apache.org/jira/browse/AMQCPP-552 Project: ActiveMQ C

[jira] [Commented] (AMQ-5330) MQTT unsubscribe command doesn't remove durable subscriber from topic

[ https://issues.apache.org/jira/browse/AMQ-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106681#comment-14106681 ] Timothy Bish commented on AMQ-5330: --- Please retest against v5.10.0 as there are many

[jira] [Resolved] (AMQNET-489) Port fixes from AMQ-5146 to NMS.ActiveMQ

[ https://issues.apache.org/jira/browse/AMQNET-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-489. - Resolution: Fixed Fixed on trunk and the 1.6.x branch. > Port fixes from AMQ-5146

[jira] [Closed] (AMQ-5326) SslTransport doesn't support soWriteTimeout

[ https://issues.apache.org/jira/browse/AMQ-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5326. - Resolution: Duplicate Already fixed by: AMQ-3300 > SslTransport doesn't support soWrit

[jira] [Comment Edited] (AMQ-5326) SslTransport doesn't support soWriteTimeout

[ https://issues.apache.org/jira/browse/AMQ-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105011#comment-14105011 ] Timothy Bish edited comment on AMQ-5326 at 8/21/14 8:5

[jira] [Closed] (AMQ-5328) Store limit reset to a smaller value than the current size

[ https://issues.apache.org/jira/browse/AMQ-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5328. - Resolution: Duplicate This issue is fixed in 5.10, see AMQ-4832 > Store limit reset to a smaller va

[jira] [Resolved] (AMQCPP-551) EOFException when sending char in MapMessage between Java and C++

[ https://issues.apache.org/jira/browse/AMQCPP-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-551. - Resolution: Fixed Fix Version/s: 3.9.0 3.8.4 Fixed on trunk and the

[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS

[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104577#comment-14104577 ] Timothy Bish commented on AMQNET-454: - @Chuck. Before there could be a release

[jira] [Resolved] (AMQCPP-550) CMS (C++ client) crashed if getLocalHost failed

[ https://issues.apache.org/jira/browse/AMQCPP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-550. - Resolution: Fixed Fix Version/s: 3.9.0 3.8.4 Assignee: Timothy

[jira] [Moved] (AMQCPP-550) CMS (C++ client) crashed if getLocalHost failed

[ https://issues.apache.org/jira/browse/AMQCPP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish moved AMQ-5325 to AMQCPP-550: -- Component/s: (was: CMS (C++ client)) Decaf

[jira] [Created] (AMQNET-489) Port fixes from AMQ-5146 to NMS.ActiveMQ

Timothy Bish created AMQNET-489: --- Summary: Port fixes from AMQ-5146 to NMS.ActiveMQ Key: AMQNET-489 URL: https://issues.apache.org/jira/browse/AMQNET-489 Project: ActiveMQ .Net Issue Type: Bug

[jira] [Commented] (AMQ-5153) LevelDB does not store subscribedDestination for durable subscriptions

[ https://issues.apache.org/jira/browse/AMQ-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103862#comment-14103862 ] Timothy Bish commented on AMQ-5153: --- Recommend you create a unit test and try it aga

[jira] [Closed] (AMQNET-457) WCF Dispatching/Execution of messages happens in "ActiveMQ Task" thread

[ https://issues.apache.org/jira/browse/AMQNET-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQNET-457. --- Resolution: Incomplete Doesn't seem to be anyone willing to support the WCF provider.

[jira] [Resolved] (AMQ-4836) Calling Connection.commit() on a Connection with setAutoCommit(true) throws SQLException

[ https://issues.apache.org/jira/browse/AMQ-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-4836. --- Resolution: Fixed Fix Version/s: 5.11.0 This is resolved with the fixes in AMQ-5318 > Call

[jira] [Closed] (AMQ-4891) ActiveMQ does not honor redeliveryPolicy

[ https://issues.apache.org/jira/browse/AMQ-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-4891. - Resolution: Not a Problem The redelivery policy only applies to the local redelivery of messages to the

[jira] [Closed] (AMQ-4051) IOException: Could not locate data file .\db-10.log

[ https://issues.apache.org/jira/browse/AMQ-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-4051. - Resolution: Cannot Reproduce Without additional information on how to reproduce or evidence that this

[jira] [Commented] (AMQ-5153) LevelDB does not store subscribedDestination for durable subscriptions

[ https://issues.apache.org/jira/browse/AMQ-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102252#comment-14102252 ] Timothy Bish commented on AMQ-5153: --- Do you have a test case or some additi

[jira] [Commented] (AMQ-5237) Link stealing doesn't work for MQTT + Webscokets

[ https://issues.apache.org/jira/browse/AMQ-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101365#comment-14101365 ] Timothy Bish commented on AMQ-5237: --- On the WS and WSS transports you need to add

[jira] [Resolved] (AMQ-5237) Link stealing doesn't work for MQTT + Webscokets

[ https://issues.apache.org/jira/browse/AMQ-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5237. --- Resolution: Fixed Fix Version/s: 5.11.0 Assignee: Timothy Bish This should be working

[jira] [Closed] (AMQ-5249) "cursor got duplicate" error after upgrade

[ https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5249. - Resolution: Incomplete The use case and broker configuration are not given. There is not enough

[jira] [Resolved] (AMQ-5281) Incorrect handling of unknown values in selectors

[ https://issues.apache.org/jira/browse/AMQ-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5281. --- Resolution: Fixed Fix Version/s: 5.11.0 Patch applied with thanks. > Incorrect handling

[jira] [Assigned] (AMQ-5281) Incorrect handling of unknown values in selectors

[ https://issues.apache.org/jira/browse/AMQ-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQ-5281: - Assignee: Timothy Bish > Incorrect handling of unknown values in select

[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS

[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100644#comment-14100644 ] Timothy Bish commented on AMQNET-454: - Applied patch 29 > Add Apache Qpid p

[jira] [Closed] (AMQ-4985) java.util.ConcurrentModificationException while sending message

[ https://issues.apache.org/jira/browse/AMQ-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-4985. - Resolution: Cannot Reproduce > java.util.ConcurrentModificationException while sending mess

[jira] [Closed] (AMQ-3432) Slave broker able to start together with Master broker (shared file system master/slave setup)

[ https://issues.apache.org/jira/browse/AMQ-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3432. - Resolution: Incomplete > Slave broker able to start together with Master broker (shared file sys

[jira] [Closed] (AMQ-3240) load balance on a VirtualTopic queue broken where there are consumers subscribining to both the VT queue and VirtualTopic itself

[ https://issues.apache.org/jira/browse/AMQ-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3240. - Resolution: Cannot Reproduce > load balance on a VirtualTopic queue broken where there are consum

[jira] [Resolved] (AMQ-5323) ActiveMQ Message getProperty and setProperty inconsistent behaviour

[ https://issues.apache.org/jira/browse/AMQ-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5323. --- Resolution: Fixed Fix Version/s: 5.11.0 Fixed on trunk. > ActiveMQ Message getProperty

[jira] [Updated] (AMQ-5323) ActiveMQ Message getProperty and setProperty inconsistent behaviour

[ https://issues.apache.org/jira/browse/AMQ-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5323: -- Priority: Trivial (was: Major) > ActiveMQ Message getProperty and setProperty inconsistent behavi

[jira] [Commented] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID

[ https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098569#comment-14098569 ] Timothy Bish commented on AMQ-5322: --- You can configure the cache size in your Br

[jira] [Updated] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID

[ https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5322: -- Attachment: AMQ5322Test.java Test that passes using indicated scenario. > Message is assigned

[jira] [Resolved] (AMQCPP-543) message producer send never blocking when using producer flow control

[ https://issues.apache.org/jira/browse/AMQCPP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-543. - Resolution: Fixed Fix Version/s: 3.9.0 Applied fix on trunk. > message producer s

[jira] [Closed] (AMQ-5034) ActiveMQ xsd missing readThreads attribute on LevelDB store

[ https://issues.apache.org/jira/browse/AMQ-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5034. - Resolution: Not a Problem Removed non-existent property from LevelDB documentation. > ActiveMQ

[jira] [Closed] (AMQ-5040) Issue with Eclipse Paho mobile client and reconnecting due to failure.

[ https://issues.apache.org/jira/browse/AMQ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5040. - Resolution: Not a Problem The latest release has many improvements in the area of MQTT. Try the latest

[jira] [Commented] (AMQ-5185) Duplicate messages occur for MQTT cleanSession=false client with network of brokers

[ https://issues.apache.org/jira/browse/AMQ-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097317#comment-14097317 ] Timothy Bish commented on AMQ-5185: --- This can be worked around by using the virtual t

[jira] [Commented] (AMQ-5322) Message is assigned to different client with the same JMSXGroupID

[ https://issues.apache.org/jira/browse/AMQ-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097261#comment-14097261 ] Timothy Bish commented on AMQ-5322: --- It would be a good idea for you to try and crea

[jira] [Resolved] (AMQCPP-549) Potential memory leak in consumer when delivering delayed ack.

[ https://issues.apache.org/jira/browse/AMQCPP-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-549. - Resolution: Fixed Ensure that returned future pointer gets deleted. Fixed on trunk and 3.8.x

[jira] [Created] (AMQCPP-549) Potential memory leak in consumer when delivering delayed ack.

Timothy Bish created AMQCPP-549: --- Summary: Potential memory leak in consumer when delivering delayed ack. Key: AMQCPP-549 URL: https://issues.apache.org/jira/browse/AMQCPP-549 Project: ActiveMQ C

[jira] [Resolved] (AMQ-5072) Support configuring a different directory for the KahaDB index files.

[ https://issues.apache.org/jira/browse/AMQ-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5072. --- Resolution: Fixed Fixed on trunk, test added. > Support configuring a different directory for

[jira] [Reopened] (AMQ-5072) Support configuring a different directory for the KahaDB index files.

[ https://issues.apache.org/jira/browse/AMQ-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened AMQ-5072: --- Assignee: Timothy Bish (was: Hiram Chirino) Fix needs accessors added to the

[jira] [Updated] (AMQ-5072) Support configuring a different directory for the KahaDB index files.

[ https://issues.apache.org/jira/browse/AMQ-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5072: -- Fix Version/s: (was: 5.10.0) 5.11.0 > Support configuring a different direct

[jira] [Closed] (AMQNET-462) Failover transport: Deduplication algorithm is wrong (1)

[ https://issues.apache.org/jira/browse/AMQNET-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQNET-462. --- Resolution: Incomplete > Failover transport: Deduplication algorithm is wrong

[jira] [Closed] (AMQNET-485) Messages are being marked as duplicate in error

[ https://issues.apache.org/jira/browse/AMQNET-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQNET-485. --- Resolution: Cannot Reproduce Can't reproduce this one with the provided information. Reopen

[jira] [Comment Edited] (AMQNET-485) Messages are being marked as duplicate in error

[ https://issues.apache.org/jira/browse/AMQNET-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096068#comment-14096068 ] Timothy Bish edited comment on AMQNET-485 at 8/13/14 8:3

[jira] [Commented] (AMQNET-485) Messages are being marked as duplicate in error

[ https://issues.apache.org/jira/browse/AMQNET-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096068#comment-14096068 ] Timothy Bish commented on AMQNET-485: - Attempted to reproduce with no luck: {

[jira] [Closed] (AMQ-5133) Selector Worker thread consumes significant CPU when broker is idle

[ https://issues.apache.org/jira/browse/AMQ-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5133. - Resolution: Cannot Reproduce > Selector Worker thread consumes significant CPU when broker is i

[jira] [Updated] (AMQ-5295) HTTPS Network Connector doesn't work with Mutual authentication- HTTPSClientTransport uses wrong SSLSocketFactory

[ https://issues.apache.org/jira/browse/AMQ-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5295: -- Fix Version/s: 5.11.0 > HTTPS Network Connector doesn't work with Mutual authen

[jira] [Resolved] (AMQ-5295) HTTPS Network Connector doesn't work with Mutual authentication- HTTPSClientTransport uses wrong SSLSocketFactory

[ https://issues.apache.org/jira/browse/AMQ-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5295. --- Resolution: Fixed Patch applied, thanks. > HTTPS Network Connector doesn't work wit

[jira] [Resolved] (AMQ-5320) Incorrect Documentation in org.apache.activemq.management.SizeStatisticImpl

[ https://issues.apache.org/jira/browse/AMQ-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5320. --- Resolution: Fixed Fix Version/s: 5.11.0 updated the docs a bit. > Incorrect Documentation

[jira] [Closed] (AMQ-5250) temp queue not working after long run of activemq

[ https://issues.apache.org/jira/browse/AMQ-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5250. - Resolution: Cannot Reproduce No test case to investigate and from the description it sounds like normal

[jira] [Commented] (AMQ-4652) Test failed under Java 8

[ https://issues.apache.org/jira/browse/AMQ-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094597#comment-14094597 ] Timothy Bish commented on AMQ-4652: --- I think we can close this one now, the tests u

[jira] [Commented] (AMQ-5290) MQTT clients using durable subscriptions on networked brokers received duplicates

[ https://issues.apache.org/jira/browse/AMQ-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094516#comment-14094516 ] Timothy Bish commented on AMQ-5290: --- Cleaned up a little and shortened the trans

[jira] [Resolved] (AMQ-5290) MQTT clients using durable subscriptions on networked brokers received duplicates

[ https://issues.apache.org/jira/browse/AMQ-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5290. --- Resolution: Fixed Assignee: Timothy Bish Implemented an initial solution which is to use a

[jira] [Comment Edited] (AMQ-5290) MQTT clients using durable subscriptions on networked brokers received duplicates

[ https://issues.apache.org/jira/browse/AMQ-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088318#comment-14088318 ] Timothy Bish edited comment on AMQ-5290 at 8/12/14 7:0

[jira] [Resolved] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-488. - Resolution: Fixed Assignee: Timothy Bish (was: Jim Gomes) Fixed > Deadlock

[jira] [Updated] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-488: Fix Version/s: 1.7.0 > Deadlock in InactivityMonitor when using Failo

[jira] [Updated] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-488: Affects Version/s: 1.6.3 > Deadlock in InactivityMonitor when using Failo

[jira] [Updated] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-488: Fix Version/s: 1.6.4 > Deadlock in InactivityMonitor when using Failo

[jira] [Commented] (AMQNET-488) Deadlock in InactivityMonitor when using Failover

[ https://issues.apache.org/jira/browse/AMQNET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094380#comment-14094380 ] Timothy Bish commented on AMQNET-488: - Reviewed and tested, looks good. P

[jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS

[ https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094223#comment-14094223 ] Timothy Bish commented on AMQNET-454: - Patches applied. > Add Apache Qpid p

[jira] [Commented] (AMQ-5319) Message Redelivery Does Not Work As Expected With Concurrent Connections

[ https://issues.apache.org/jira/browse/AMQ-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093455#comment-14093455 ] Timothy Bish commented on AMQ-5319: --- At most this would be a new feature request, how

[jira] [Updated] (AMQ-5319) Message Redelivery Does Not Work As Expected With Concurrent Connections

[ https://issues.apache.org/jira/browse/AMQ-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5319: -- Issue Type: New Feature (was: Bug) > Message Redelivery Does Not Work As Expected With Concurr

[jira] [Updated] (AMQ-5319) Message Redelivery Does Not Work As Expected With Concurrent Connections

[ https://issues.apache.org/jira/browse/AMQ-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5319: -- Priority: Minor (was: Major) > Message Redelivery Does Not Work As Expected With Concurrent Connecti

[jira] [Closed] (AMQ-5319) Message Redelivery Does Not Work As Expected With Concurrent Connections

[ https://issues.apache.org/jira/browse/AMQ-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5319. - Resolution: Invalid This sort of thing belongs as a question on the user list. > Message Redelivery D

[jira] [Resolved] (AMQNET-487) Deadlock in Failover Transport when reconnecting

[ https://issues.apache.org/jira/browse/AMQNET-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-487. - Resolution: Fixed Fix Version/s: 1.7.0 1.6.4 Assignee: Timothy

<    4   5   6   7   8   9   10   11   12   13   >