[jira] [Commented] (AMQ-5192) Add a statistic for showing how many messages every scheduler job triggered

[ https://issues.apache.org/jira/browse/AMQ-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025372#comment-14025372 ] Timothy Bish commented on AMQ-5192: --- There isn't any way to query for informati

[jira] [Commented] (AMQ-5219) Deadlock between JMS Job Scheduler and broker initialization

[ https://issues.apache.org/jira/browse/AMQ-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025358#comment-14025358 ] Timothy Bish commented on AMQ-5219: --- You need to test this against a current releas

[jira] [Updated] (AMQ-5219) Deadlock between JMS Job Scheduler and broker initialization

[ https://issues.apache.org/jira/browse/AMQ-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5219: -- Priority: Major (was: Critical) > Deadlock between JMS Job Scheduler and broker initializat

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

+1 On 06/05/2014 10:08 AM, Dejan Bosanac wrote: Hi folks, I've just cut a second release candidate for the 5.10.0 release. This release has 232 bug fixes and improvements. Could you review the artifacts and vote? The list of resolved issues is here: https://issues.apache.org/jira/issues/?jql=

[jira] [Resolved] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

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

[jira] [Commented] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[ https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019250#comment-14019250 ] Timothy Bish commented on AMQ-5211: --- This seems sensible enough. Empty destination n

[jira] [Resolved] (AMQ-5214) Security errors for sync commands are only logged at debug levels

[ https://issues.apache.org/jira/browse/AMQ-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5214. --- Resolution: Fixed Fixed on trunk. > Security errors for sync commands are only logged at debug lev

[jira] [Created] (AMQ-5214) Security errors for sync commands are only logged at debug levels

Timothy Bish created AMQ-5214: - Summary: Security errors for sync commands are only logged at debug levels Key: AMQ-5214 URL: https://issues.apache.org/jira/browse/AMQ-5214 Project: ActiveMQ

[jira] [Resolved] (AMQ-5213) Allow for changing logger levels via JMX

[ https://issues.apache.org/jira/browse/AMQ-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5213. --- Resolution: Fixed Feature added on trunk. > Allow for changing logger levels via

[jira] [Created] (AMQ-5213) Allow for changing logger levels via JMX

Timothy Bish created AMQ-5213: - Summary: Allow for changing logger levels via JMX Key: AMQ-5213 URL: https://issues.apache.org/jira/browse/AMQ-5213 Project: ActiveMQ Issue Type: New Feature

Re: [VOTE] Apache ActiveMQ 5.10.0

On 06/04/2014 09:10 AM, Dejan Bosanac wrote: Hi folks, I've just cut a release candidate for the long-awaited 5.10.0 release. This release has 229 bug fixes and improvements. Could you review the artifacts and vote? The list of resolved issues is here: https://issues.apache.org/jira/secure/Rel

[jira] [Resolved] (AMQ-5193) Java Files Started Appearing in activemq-all jar starting in 5.9.0

[ https://issues.apache.org/jira/browse/AMQ-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5193. --- Resolution: Fixed Fix Version/s: 5.11.0 added shade transformer that ensures the sources are

[jira] [Commented] (AMQ-5193) Java Files Started Appearing in activemq-all jar starting in 5.9.0

[ https://issues.apache.org/jira/browse/AMQ-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017993#comment-14017993 ] Timothy Bish commented on AMQ-5193: --- I think this is related to the change for: AMQ-

[jira] [Resolved] (AMQ-5209) Add additional properties to advisory for consumed, delivered and discarded

[ https://issues.apache.org/jira/browse/AMQ-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5209. --- Resolution: Fixed Fixed on trunk. > Add additional properties to advisory for consumed, delive

[jira] [Created] (AMQ-5209) Add additional properties to advisory for consumed, delivered and discarded

Timothy Bish created AMQ-5209: - Summary: Add additional properties to advisory for consumed, delivered and discarded Key: AMQ-5209 URL: https://issues.apache.org/jira/browse/AMQ-5209 Project: ActiveMQ

[jira] [Commented] (AMQ-5207) advisoryforConsumed does not contain original messageID

[ https://issues.apache.org/jira/browse/AMQ-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017899#comment-14017899 ] Timothy Bish commented on AMQ-5207: --- An enhancement issue has been cre

[jira] [Resolved] (AMQ-5043) Improve MQTT spec compatibility

[ https://issues.apache.org/jira/browse/AMQ-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5043. --- Resolution: Fixed Marking this as fixed following all the work that's gone into MQTT over the

[jira] [Closed] (AMQ-5207) advisoryforConsumed does not contain original messageID

[ https://issues.apache.org/jira/browse/AMQ-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5207. - Resolution: Not a Problem The advisory does indeed contain all the needed information

[jira] [Commented] (AMQ-5207) advisoryforConsumed does not contain original messageID

[ https://issues.apache.org/jira/browse/AMQ-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017724#comment-14017724 ] Timothy Bish commented on AMQ-5207: --- The Advisory for consumed messages contains

[jira] [Commented] (AMQ-5198) MessageConsumer and Producer are not thread safe

[ https://issues.apache.org/jira/browse/AMQ-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017707#comment-14017707 ] Timothy Bish commented on AMQ-5198: --- Haven't had time to investigate as the test

[jira] [Deleted] (AMQ-5206) niraj1018 hi

[ https://issues.apache.org/jira/browse/AMQ-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish deleted AMQ-5206: -- > niraj1018 hi > > > Key: AMQ-5206 >

[jira] [Closed] (AMQ-4812) Rebalance not working on 5.8.0

[ https://issues.apache.org/jira/browse/AMQ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-4812. - Resolution: Incomplete No test case provided that demonstrates an actual issue with this functionality

[jira] [Resolved] (AMQ-5189) Rollback on XASession when closing back to pool

[ https://issues.apache.org/jira/browse/AMQ-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5189. --- Resolution: Fixed Fix Version/s: 5.10.0 Assignee: Timothy Bish Nice idea, patch looks

[jira] [Deleted] (AMQ-5203) test

[ https://issues.apache.org/jira/browse/AMQ-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish deleted AMQ-5203: -- > test > > > Key: AMQ-5203 > URL: https://issues.apache.

[jira] [Commented] (AMQ-4977) Memory leak in ConnectionStateTracker when browsing non-empty queues

[ https://issues.apache.org/jira/browse/AMQ-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009768#comment-14009768 ] Timothy Bish commented on AMQ-4977: --- v5.9.1 was released quite some time ago. >

[jira] [Resolved] (AMQ-5199) Outdated links on the "How can I see what destinations are used"

[ https://issues.apache.org/jira/browse/AMQ-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5199. --- Resolution: Fixed > Outdated links on the "How can I see what destinations

[jira] [Closed] (AMQ-5190) deadlock between producer and consumer

[ https://issues.apache.org/jira/browse/AMQ-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5190. - Resolution: Incomplete No test case provided to validate this against a current broker release, 5.5.0 is

[jira] [Commented] (AMQ-5198) MessageConsumer and Producer are not thread safe

[ https://issues.apache.org/jira/browse/AMQ-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006011#comment-14006011 ] Timothy Bish commented on AMQ-5198: --- Do you have a test case that can reproduce

[jira] [Commented] (AMQ-5193) Java Files Started Appearing in activemq-all jar starting in 5.9.0

[ https://issues.apache.org/jira/browse/AMQ-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006013#comment-14006013 ] Timothy Bish commented on AMQ-5193: --- What are the Java files you see appearing in the

[jira] [Closed] (AMQ-5194) 5.8.0 Source Files Missing from sources jar and zip

[ https://issues.apache.org/jira/browse/AMQ-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5194. - Resolution: Not a Problem only the parent source bundle is intended to contain source, the others will be

[jira] [Resolved] (AMQ-5195) AMQP protocol handler doesn't set session incoming capacity

[ https://issues.apache.org/jira/browse/AMQ-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5195. --- Resolution: Fixed Fixed on trunk. > AMQP protocol handler doesn't set session incoming

[jira] [Created] (AMQ-5195) AMQP protocol handler doesn't set session incoming capacity

Timothy Bish created AMQ-5195: - Summary: AMQP protocol handler doesn't set session incoming capacity Key: AMQ-5195 URL: https://issues.apache.org/jira/browse/AMQ-5195 Project: ActiveMQ

[jira] [Commented] (AMQ-5194) 5.8.0 Source Files Missing from sources jar and zip

[ https://issues.apache.org/jira/browse/AMQ-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003891#comment-14003891 ] Timothy Bish commented on AMQ-5194: --- I just downloaded the activemq-parent-5.8.0-so

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13999389#comment-13999389 ] Timothy Bish commented on AMQCPP-543: - You'd need to inspect the Java OpenWi

[jira] [Updated] (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 updated AMQCPP-543: Component/s: Openwire Priority: Minor (was: Major) Issue Type: New Feature (was: Bug

[jira] [Commented] (AMQ-5188) AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed

[ https://issues.apache.org/jira/browse/AMQ-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999834#comment-13999834 ] Timothy Bish commented on AMQ-5188: --- You should run your tests against a 5.10-SNAPSHO

[jira] [Resolved] (AMQ-5183) Switch to using Proton's Event logic for detecting AMQP state changes

[ https://issues.apache.org/jira/browse/AMQ-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5183. --- Resolution: Fixed implemented on trunk > Switch to using Proton's Event logic for detect

[jira] [Created] (AMQ-5183) Switch to using Proton's Event logic for detecting AMQP state changes

Timothy Bish created AMQ-5183: - Summary: Switch to using Proton's Event logic for detecting AMQP state changes Key: AMQ-5183 URL: https://issues.apache.org/jira/browse/AMQ-5183 Project: Act

[jira] [Resolved] (AMQ-5180) Links on http://activemq.apache.org/security.html out of date

[ https://issues.apache.org/jira/browse/AMQ-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5180. --- Resolution: Fixed Links fixed > Links on http://activemq.apache.org/security.html out of d

[jira] [Resolved] (AMQ-5144) stomp+nio+ssl very slow message sending

[ https://issues.apache.org/jira/browse/AMQ-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5144. --- Resolution: Fixed Fix Version/s: 5.10.0 Assignee: Timothy Bish Found the trouble spot

[jira] [Commented] (AMQ-5161) NullPointerException during async startup

[ https://issues.apache.org/jira/browse/AMQ-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994526#comment-13994526 ] Timothy Bish commented on AMQ-5161: --- One way to start is to try and find the commit

[jira] [Resolved] (AMQ-5166) MessageDatabase does not consistently apply tracker settings

[ https://issues.apache.org/jira/browse/AMQ-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5166. --- Resolution: Fixed Tested against trunk and doesn't seem to break any tests locally. Patch ap

[jira] [Updated] (AMQ-5166) MessageDatabase does not consistently apply tracker settings

[ https://issues.apache.org/jira/browse/AMQ-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5166: -- Fix Version/s: 5.10.0 > MessageDatabase does not consistently apply tracker setti

[jira] [Commented] (AMQ-5173) Kaha DB cleanup fails to reclaim disk space after some time

[ https://issues.apache.org/jira/browse/AMQ-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990976#comment-13990976 ] Timothy Bish commented on AMQ-5173: --- Have you tested with a current release of Acti

[jira] [Resolved] (AMQ-5175) exclude bouncycastle dependency from unit tests run

[ https://issues.apache.org/jira/browse/AMQ-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5175. --- Resolution: Fixed fixed > exclude bouncycastle dependency from unit tests

[jira] [Created] (AMQ-5175) exclude bouncycastle dependency from unit tests run

Timothy Bish created AMQ-5175: - Summary: exclude bouncycastle dependency from unit tests run Key: AMQ-5175 URL: https://issues.apache.org/jira/browse/AMQ-5175 Project: ActiveMQ Issue Type

[jira] [Resolved] (AMQ-5140) ArithmeticException: / by zero in HealthView.healthList() when using JMX-Health-Operations

[ https://issues.apache.org/jira/browse/AMQ-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5140. --- Resolution: Fixed Fix Version/s: 5.10.0 Couldn't reproduce this but I went ahead and added

[jira] [Commented] (AMQ-5144) stomp+nio+ssl very slow message sending

[ https://issues.apache.org/jira/browse/AMQ-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989912#comment-13989912 ] Timothy Bish commented on AMQ-5144: --- I'd recommend looking at the STOMP unit

[jira] [Commented] (AMQ-5161) NullPointerException during async startup

[ https://issues.apache.org/jira/browse/AMQ-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989907#comment-13989907 ] Timothy Bish commented on AMQ-5161: --- If you can provide a unit test that reproduces

[jira] [Commented] (AMQ-5086) vm transport create=false&waitForStart race condition

[ https://issues.apache.org/jira/browse/AMQ-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989694#comment-13989694 ] Timothy Bish commented on AMQ-5086: --- Would be great if you could come up with a test

[jira] [Updated] (AMQ-5086) vm transport create=false&waitForStart race condition

[ https://issues.apache.org/jira/browse/AMQ-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5086: -- Attachment: AMQ5086.patch > vm transport create=false&waitForStart race co

[jira] [Commented] (AMQ-5172) Race conditions in ActiveMQ broker

[ https://issues.apache.org/jira/browse/AMQ-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989695#comment-13989695 ] Timothy Bish commented on AMQ-5172: --- Would need a test case to reproduce the issue s

[jira] [Resolved] (AMQ-5171) Boreker configured as zeroconf service is not discovered by Bonjour browser running in ios

[ https://issues.apache.org/jira/browse/AMQ-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5171. --- Resolution: Fixed Fix Version/s: 5.10.0 Made the type value configurable via setter setType

[jira] [Commented] (AMQ-5171) Boreker configured as zeroconf service is not discovered by Bonjour browser running in ios

[ https://issues.apache.org/jira/browse/AMQ-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989587#comment-13989587 ] Timothy Bish commented on AMQ-5171: --- It seems the simpler fix would be to make the

[jira] [Closed] (AMQCPP-541) Crash found when closing ActiveMQConnection

[ https://issues.apache.org/jira/browse/AMQCPP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQCPP-541. --- Resolution: Invalid Questions belong on the user list. This old version is not supported any

[jira] [Resolved] (AMQ-5092) MQTT uses duplicate packet IDs for PUBLISH messages

[ https://issues.apache.org/jira/browse/AMQ-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5092. --- Resolution: Fixed Fixed on trun > MQTT uses duplicate packet IDs for PUBLISH messa

[jira] [Updated] (AMQ-4710) The first heart-beat after a connection becomes idle isn't sent as quickly as it should be

[ https://issues.apache.org/jira/browse/AMQ-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-4710: -- Fix Version/s: (was: 5.10.0) 5.11.0 > The first heart-beat after a connect

[jira] [Resolved] (AMQ-5004) Dispatching large messages over AMQP is very slow.

[ https://issues.apache.org/jira/browse/AMQ-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5004. --- Resolution: Fixed fixed on trunk, all tests passing > Dispatching large messages over AMQP is v

[jira] [Commented] (AMQ-5004) Dispatching large messages over AMQP is very slow.

[ https://issues.apache.org/jira/browse/AMQ-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985568#comment-13985568 ] Timothy Bish commented on AMQ-5004: --- Updated trunk to proton 0.7 need to fix fai

[jira] [Updated] (AMQ-5032) AMQP Message Expiry Time not mapped correctly in many case to / from JMS

[ https://issues.apache.org/jira/browse/AMQ-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5032: -- Priority: Major (was: Blocker) Fix Version/s: (was: 5.10.0) 5.10.1

Re: why there is not support amqPersistenceAdapter in ActiveMQ 5.9 anymore ?

On 04/29/2014 11:10 AM, wuzhaoxue wrote: Hi all Who know why there is not support amqPersistenceAdapter in ActiveMQ 5.9 anymore ? I configure the AMQ DB in ActiveMQ 5.9 , got the following error: ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: org.sprin

[jira] [Closed] (AMQ-4996) org.apache.activemq.transport.RequestTimedOutIOException thrown by producer.send() for no obvious reason. Message is actually sent.

[ https://issues.apache.org/jira/browse/AMQ-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-4996. - Resolution: Incomplete No test case to reproduce this and the version is quite old so you would need to

[jira] [Closed] (AMQ-4966) ActiveMQ 5.9.0 Hawtio is Extremely slow when accessed from http://localhost:8162

[ https://issues.apache.org/jira/browse/AMQ-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-4966. - Resolution: Invalid Hawtio removed from ActiveMQ distro as of 5.9.1 > ActiveMQ 5.9.0 Hawtio is Extrem

[jira] [Assigned] (AMQ-5004) Dispatching large messages over AMQP is very slow.

[ https://issues.apache.org/jira/browse/AMQ-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQ-5004: - Assignee: Timothy Bish > Dispatching large messages over AMQP is very s

[jira] [Commented] (AMQ-5004) Dispatching large messages over AMQP is very slow.

[ https://issues.apache.org/jira/browse/AMQ-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984402#comment-13984402 ] Timothy Bish commented on AMQ-5004: --- Awaiting publish of the released Proton v0.7 lib

[jira] [Closed] (AMQ-5056) Can't not use slash (/) in the queue destination name .

[ https://issues.apache.org/jira/browse/AMQ-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5056. - Resolution: Incomplete Need a test case to test against a version of the broker that's more current

[jira] [Commented] (AMQ-5043) Improve MQTT spec compatibility

[ https://issues.apache.org/jira/browse/AMQ-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984399#comment-13984399 ] Timothy Bish commented on AMQ-5043: --- Can we close this out now given all of @Dhir

[jira] [Closed] (AMQ-5083) Cannot consume messages. Failed to fill batch . cased by NegativeArraySizeException

[ https://issues.apache.org/jira/browse/AMQ-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5083. - Resolution: Incomplete The issue here appears to be related to fixes that have gone in since the v5.7.0

[jira] [Commented] (AMQ-5092) MQTT uses duplicate packet IDs for PUBLISH messages

[ https://issues.apache.org/jira/browse/AMQ-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984394#comment-13984394 ] Timothy Bish commented on AMQ-5092: --- Dhiraj, can we consider this resolved now? &g

[jira] [Resolved] (AMQ-5101) MQTT SUBACK packet MUST use return code 0x80 to report failed topic subscriptions

[ https://issues.apache.org/jira/browse/AMQ-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5101. --- Resolution: Fixed Test appears to be stable now with all the other MQTT fixes that have gone in. Can

[jira] [Commented] (AMQ-5124) Exception logged on startup: jolokia-agent: Cannot start discovery multicast handler

[ https://issues.apache.org/jira/browse/AMQ-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984379#comment-13984379 ] Timothy Bish commented on AMQ-5124: --- With the release of v1.2.1 this could probably

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13984373#comment-13984373 ] Timothy Bish commented on AMQ-5133: --- Without some way to reproduce this it's go

[jira] [Closed] (AMQ-5158) Non persistent Messages not getting expired

[ https://issues.apache.org/jira/browse/AMQ-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5158. - Resolution: Duplicate > Non persistent Messages not getting expi

[jira] [Commented] (AMQ-4575) JDBCIOExceptionHandler does not restart TransportConnector when JMX is enabled on broker - java.io.IOException: Transport Connector could not be registered in JMX

[ https://issues.apache.org/jira/browse/AMQ-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984331#comment-13984331 ] Timothy Bish commented on AMQ-4575: --- The file you attached actually appears to be a

[jira] [Commented] (AMQ-5143) Lost Message with LevelDB

[ https://issues.apache.org/jira/browse/AMQ-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983460#comment-13983460 ] Timothy Bish commented on AMQ-5143: --- Have you tested against 5.9.1 or a 5.10-SNAP

[jira] [Commented] (AMQ-5144) stomp+nio+ssl very slow message sending

[ https://issues.apache.org/jira/browse/AMQ-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983457#comment-13983457 ] Timothy Bish commented on AMQ-5144: --- Have you tried using a profiler to see where

[jira] [Commented] (AMQ-4575) JDBCIOExceptionHandler does not restart TransportConnector when JMX is enabled on broker - java.io.IOException: Transport Connector could not be registered in JMX

[ https://issues.apache.org/jira/browse/AMQ-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983396#comment-13983396 ] Timothy Bish commented on AMQ-4575: --- Can you create a JUnit test along the lines of

[jira] [Resolved] (AMQ-5163) Enable durable topic subscriptions using individual ack mode.

[ https://issues.apache.org/jira/browse/AMQ-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5163. --- Resolution: Fixed fixed on trunk. > Enable durable topic subscriptions using individual ack m

[jira] [Resolved] (AMQ-3486) Add check to prevent Durable Subscriptions on Session that are in Individual Ack mode.

[ https://issues.apache.org/jira/browse/AMQ-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-3486. --- Resolution: Fixed Now re-enabled in trunk > Add check to prevent Durable Subscriptions on Sess

[jira] [Created] (AMQ-5163) Enable durable topic subscriptions using individual ack mode.

Timothy Bish created AMQ-5163: - Summary: Enable durable topic subscriptions using individual ack mode. Key: AMQ-5163 URL: https://issues.apache.org/jira/browse/AMQ-5163 Project: ActiveMQ Issue

[jira] [Commented] (AMQ-3486) Add check to prevent Durable Subscriptions on Session that are in Individual Ack mode.

[ https://issues.apache.org/jira/browse/AMQ-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983252#comment-13983252 ] Timothy Bish commented on AMQ-3486: --- Tested with a basic individual acknowledge scen

[jira] [Closed] (AMQ-5134) scheduler/db-x.log can not delele

[ https://issues.apache.org/jira/browse/AMQ-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5134. - Resolution: Incomplete This appears to be working as designed. Submit a test case if you really think

[jira] [Closed] (AMQ-5150) ActiveMQ failover seems not to work in 5.9.1 on MacOSX

[ https://issues.apache.org/jira/browse/AMQ-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5150. - Resolution: Not a Problem The is expected behaviour with failover. You need to ensure you application

[jira] [Closed] (AMQ-5145) JMS Failed to schedule job Chunk stream does not exist

[ https://issues.apache.org/jira/browse/AMQ-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5145. - Resolution: Incomplete This is a very old version of ActiveMQ and there have been many fixes and

[jira] [Resolved] (AMQCPP-540) Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp

[ https://issues.apache.org/jira/browse/AMQCPP-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-540. - Resolution: Fixed Fix Version/s: 3.9.0 > Ambiguous usage of Math::min

[jira] [Resolved] (AMQCPP-539) Can't build GIT master on MSVC

[ https://issues.apache.org/jira/browse/AMQCPP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-539. - Resolution: Fixed Fix Version/s: 3.9.0 > Can't build GIT master

[jira] [Resolved] (AMQ-5159) STOMP browse gets null pointer exception if ACK mode is not AUTO

[ https://issues.apache.org/jira/browse/AMQ-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5159. --- Resolution: Fixed Fixed on trunk > STOMP browse gets null pointer exception if ACK mode is not A

[jira] [Created] (AMQ-5159) STOMP browse gets null pointer exception if ACK mode is not AUTO

Timothy Bish created AMQ-5159: - Summary: STOMP browse gets null pointer exception if ACK mode is not AUTO Key: AMQ-5159 URL: https://issues.apache.org/jira/browse/AMQ-5159 Project: ActiveMQ

Re: [jira] [Updated] (AMQNET-338) TcpTransport.cs - Close() taking 30 seconds

On 04/17/2014 03:12 AM, GoodLuck wrote: > I met the same problem "TcpTransport.cs - close() taking 30 seconds" in my > program with Apache.NMS.ActiveMQ 1.6.2. > My C# client is using .NET 4.0, ActiveMQ 5.6.0 and NMS 1.6.0 in Windows 7 64 > bits OS. > > In the forum, I read the message said vers

[jira] [Commented] (AMQ-5097) ElectingLevelDBStore - NPE in doStop

[ https://issues.apache.org/jira/browse/AMQ-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971380#comment-13971380 ] Timothy Bish commented on AMQ-5097: --- Try creating a unit test to repro

[jira] [Resolved] (AMQCPP-538) Catch exception by value in FailoverTransport

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

[jira] [Closed] (AMQ-5142) Behavior when message expires while it's being processed

[ https://issues.apache.org/jira/browse/AMQ-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5142. - Resolution: Invalid This is a user list question not a bug report. > Behavior when message expires wh

[jira] [Commented] (AMQ-5134) scheduler/db-x.log can not delele

[ https://issues.apache.org/jira/browse/AMQ-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961899#comment-13961899 ] Timothy Bish commented on AMQ-5134: --- The scheduler store is based on KahaDB and

[jira] [Resolved] (AMQ-5138) Useless code in VMTransport class

[ https://issues.apache.org/jira/browse/AMQ-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5138. --- Resolution: Fixed > Useless code in VMTransport cl

[jira] [Updated] (AMQ-5138) Useless code in VMTransport class

[ https://issues.apache.org/jira/browse/AMQ-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5138: -- Fix Version/s: 5.10.0 > Useless code in VMTransport cl

[jira] [Resolved] (AMQ-5131) Add proton META_INF/services to the activemq-osgi bundle definition so AMQP works inside Karaf

[ https://issues.apache.org/jira/browse/AMQ-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5131. --- Resolution: Fixed > Add proton META_INF/services to the activemq-osgi bundle definition so A

[jira] [Updated] (AMQ-5127) MQTT Subscriber with QoS.EXACTLY_ONCE receives messages even after unsubscribing from topic

[ https://issues.apache.org/jira/browse/AMQ-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5127: -- Fix Version/s: (was: 5.10.0) NEEDS_REVIEW > MQTT Subscriber with QoS.EXACTLY_O

[jira] [Created] (AMQ-5131) Add proton META_INF/services to the activemq-osgi bundle definition so AMQP works inside Karaf

Timothy Bish created AMQ-5131: - Summary: Add proton META_INF/services to the activemq-osgi bundle definition so AMQP works inside Karaf Key: AMQ-5131 URL: https://issues.apache.org/jira/browse/AMQ-5131

[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=13958216#comment-13958216 ] Timothy Bish commented on AMQNET-454: - Patch applied. > Add Apache Qpid prov

[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=13956929#comment-13956929 ] Timothy Bish commented on AMQNET-454: - All new patch applied without issue. &

<    7   8   9   10   11   12   13   14   15   16   >