[jira] [Closed] (AMQ-5660) Dequeue count for Topics does not increase for durable subscribers

[ https://issues.apache.org/jira/browse/AMQ-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5660. - Resolution: Duplicate Fix Version/s: AMQ-4965 Same issue being reported as AMQ-4965 > Dequeue co

[jira] [Updated] (AMQ-5646) AMQP: Second receiver attaching to queue hangs

[ https://issues.apache.org/jira/browse/AMQ-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5646: -- Fix Version/s: 5.12.0 > AMQP: Second receiver attaching to queue ha

[jira] [Resolved] (AMQ-5646) AMQP: Second receiver attaching to queue hangs

[ https://issues.apache.org/jira/browse/AMQ-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5646. --- Resolution: Fixed Fixed by changes in AMQ-5661 > AMQP: Second receiver attaching to queue ha

[jira] [Resolved] (AMQ-5661) AMQP: Honor receiver flow as the true prefetch value on a link.

[ https://issues.apache.org/jira/browse/AMQ-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5661. --- Resolution: Fixed Link credit now configures subscription prefetch. Old prefetch value on the AMQP

[jira] [Commented] (AMQ-5661) AMQP: Honor receiver flow as the true prefetch value on a link.

[ https://issues.apache.org/jira/browse/AMQ-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361187#comment-14361187 ] Timothy Bish commented on AMQ-5661: --- Root cause for this related issue. > AMQP

[jira] [Created] (AMQ-5661) AMQP: Honor receiver flow as the true prefetch value on a link.

Timothy Bish created AMQ-5661: - Summary: AMQP: Honor receiver flow as the true prefetch value on a link. Key: AMQ-5661 URL: https://issues.apache.org/jira/browse/AMQ-5661 Project: ActiveMQ

[jira] [Resolved] (AMQ-5602) AMQP: Create simple Proton based client to be used in testing

[ https://issues.apache.org/jira/browse/AMQ-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5602. --- Resolution: Fixed added new proton-j based test client on master along some initial work on validation

Re: ActiveMQ DSLs

On 03/13/2015 12:13 PM, Jakub Korab wrote: Hi All, In working on a separate project, I found the need to instantiate multiple different ActiveMQ configurations. Rather than writing up a lot of different XML configs or messing around with assembling BrokerService instances, I wrote a DSL that

[jira] [Commented] (AMQCPP-553) Deadlock and memory leak under stress

[ https://issues.apache.org/jira/browse/AMQCPP-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359103#comment-14359103 ] Timothy Bish commented on AMQCPP-553: - If you are convinced there is a leak in Bi

[jira] [Assigned] (AMQ-5646) AMQP: Second receiver attaching to queue hangs

[ https://issues.apache.org/jira/browse/AMQ-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQ-5646: - Assignee: Timothy Bish > AMQP: Second receiver attaching to queue ha

[jira] [Commented] (AMQ-5646) AMQP: Second receiver attaching to queue hangs

[ https://issues.apache.org/jira/browse/AMQ-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357619#comment-14357619 ] Timothy Bish commented on AMQ-5646: --- I've created a test case to reproduce this

[jira] [Resolved] (AMQCPP-567) activemq-cpp.pc contains wrong package name for APR

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

[jira] [Commented] (AMQ-5641) Failed to add Connection ID

[ https://issues.apache.org/jira/browse/AMQ-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356852#comment-14356852 ] Timothy Bish commented on AMQ-5641: --- Still does not appear to be an ActiveMQ issue.

[jira] [Comment Edited] (AMQ-5641) Failed to add Connection ID

[ https://issues.apache.org/jira/browse/AMQ-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356359#comment-14356359 ] Timothy Bish edited comment on AMQ-5641 at 3/11/15 1:17 PM:

[jira] [Resolved] (AMQ-5655) AMQP: Add connection property to open frame when connection attempt has failed

[ https://issues.apache.org/jira/browse/AMQ-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5655. --- Resolution: Fixed fix added to master > AMQP: Add connection property to open frame when connect

[jira] [Created] (AMQ-5655) AMQP: Add connection property to open frame when connection attempt has failed

Timothy Bish created AMQ-5655: - Summary: AMQP: Add connection property to open frame when connection attempt has failed Key: AMQ-5655 URL: https://issues.apache.org/jira/browse/AMQ-5655 Project: ActiveMQ

[jira] [Commented] (AMQCPP-567) activemq-cpp.pc contains wrong package name for APR

[ https://issues.apache.org/jira/browse/AMQCPP-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354842#comment-14354842 ] Timothy Bish commented on AMQCPP-567: - If you have a patch that gets it workin

[jira] [Moved] (AMQCPP-567) activemq-cpp.pc contains wrong package name for APR

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

[jira] [Commented] (AMQ-5555) Memory leak around ProducerView/State and AnnotatedMBeans

[ https://issues.apache.org/jira/browse/AMQ-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353600#comment-14353600 ] Timothy Bish commented on AMQ-: --- Was there a PooledConnectionFactory in use

[jira] [Closed] (AMQ-5641) Failed to add Connection ID

[ https://issues.apache.org/jira/browse/AMQ-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5641. - Resolution: Not a Problem With only the limited information in the issue there appears to be no problem

[jira] [Resolved] (AMQ-5645) CronParser.getNextScheduledTime() for the first day of every month

[ https://issues.apache.org/jira/browse/AMQ-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5645. --- Resolution: Fixed Fix Version/s: 5.12.0 Assignee: Timothy Bish Nice catch. Reviewed

[jira] [Commented] (AMQ-5647) AMQP: Close busy receiver link to queue and open new link: new link never receives

[ https://issues.apache.org/jira/browse/AMQ-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353064#comment-14353064 ] Timothy Bish commented on AMQ-5647: --- Some similarities in behavior of both issues &g

[jira] [Commented] (AMQ-5598) MQTT+NIO+SSL: Concurrent connections lead to 100% CPU usage

[ https://issues.apache.org/jira/browse/AMQ-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351565#comment-14351565 ] Timothy Bish commented on AMQ-5598: --- No, the MQTT code does not move through the

[jira] [Commented] (AMQ-5588) Failover transport should not hang on startup if it cannot connect & Failover transport timeout options overrides reconnection strategy

[ https://issues.apache.org/jira/browse/AMQ-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350937#comment-14350937 ] Timothy Bish commented on AMQ-5588: --- This is how it works, if startMaxReconnectAtte

[jira] [Commented] (AMQ-5598) MQTT+NIO+SSL: Concurrent connections lead to 100% CPU usage

[ https://issues.apache.org/jira/browse/AMQ-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350921#comment-14350921 ] Timothy Bish commented on AMQ-5598: --- I attempted to recreate this but could not. Add

[jira] [Created] (AMQ-5648) AMQP: Update JMS Outbound transformer to add the mapping compliant destination type markers

Timothy Bish created AMQ-5648: - Summary: AMQP: Update JMS Outbound transformer to add the mapping compliant destination type markers Key: AMQ-5648 URL: https://issues.apache.org/jira/browse/AMQ-5648

[jira] [Commented] (AMQ-5643) javax.jms.JMSSecurityException: User is not authorized to write to: queue:// with NIO Transport

[ https://issues.apache.org/jira/browse/AMQ-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350400#comment-14350400 ] Timothy Bish commented on AMQ-5643: --- I'd guess it's a configuration problem

[jira] [Resolved] (AMQ-5563) activemq-camel - Wrong default value in javadoc

[ https://issues.apache.org/jira/browse/AMQ-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5563. --- Resolution: Fixed Fix Version/s: 5.12.0 I added the changes to the Javadocs to reflect the

[jira] [Resolved] (AMQ-5560) AMQP: use type descriptors to inspect AMQP filter types rather than the map keys

[ https://issues.apache.org/jira/browse/AMQ-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5560. --- Resolution: Fixed Added additional checking for the Symbolic IDs as well. > AMQP: use type descript

[jira] [Reopened] (AMQ-5560) AMQP: use type descriptors to inspect AMQP filter types rather than the map keys

[ https://issues.apache.org/jira/browse/AMQ-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened AMQ-5560: --- Need to add support for Symbolic descriptor values alongside numeric. > AMQP: use type descriptors

[jira] [Resolved] (AMQ-5560) AMQP: use type descriptors to inspect AMQP filter types rather than the map keys

[ https://issues.apache.org/jira/browse/AMQ-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5560. --- Resolution: Fixed Fixed on master, searched the filters for a matching DescribedType with the correct

[jira] [Assigned] (AMQ-5560) AMQP: use type descriptors to inspect AMQP filter types rather than the map keys

[ https://issues.apache.org/jira/browse/AMQ-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQ-5560: - Assignee: Timothy Bish > AMQP: use type descriptors to inspect AMQP filter types rather than

[jira] [Commented] (AMQ-5578) preallocate journal files

[ https://issues.apache.org/jira/browse/AMQ-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348802#comment-14348802 ] Timothy Bish commented on AMQ-5578: --- I'm seeing the following logged quite often

[jira] [Commented] (AMQ-5641) Failed to add Connection ID

[ https://issues.apache.org/jira/browse/AMQ-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348768#comment-14348768 ] Timothy Bish commented on AMQ-5641: --- Please provide a test case that demonstrates

[jira] [Updated] (AMQ-5641) Failed to add Connection ID

[ https://issues.apache.org/jira/browse/AMQ-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5641: -- Fix Version/s: (was: 5.11.1) > Failed to add Connection

[jira] [Closed] (AMQ-5641) Failed to add Connection ID

[ https://issues.apache.org/jira/browse/AMQ-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5641. - Resolution: Not a Problem You already have a client connected using the ID: WCarClient9 this is expected

[jira] [Resolved] (AMQCPP-566) Potential spin in SecureRandomImpl if /dev/urandom does not exist

[ https://issues.apache.org/jira/browse/AMQCPP-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-566. - Resolution: Fixed Fixed on trunk and 3.8.x > Potential spin in SecureRandomImpl if /dev/uran

[jira] [Created] (AMQCPP-566) Potential spin in SecureRandomImpl if /dev/urandom does not exist

Timothy Bish created AMQCPP-566: --- Summary: Potential spin in SecureRandomImpl if /dev/urandom does not exist Key: AMQCPP-566 URL: https://issues.apache.org/jira/browse/AMQCPP-566 Project: ActiveMQ C

[jira] [Resolved] (AMQ-5470) AMQP - delayed authentication from SASL connect leads to race on client end.

[ https://issues.apache.org/jira/browse/AMQ-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5470. --- Resolution: Fixed Fixed on master, when possible the AMQP stack will attempt to authenticate at the

[jira] [Updated] (AMQ-5636) Upgrade the bundled DBCP component. The current one is very old and buggy.

[ https://issues.apache.org/jira/browse/AMQ-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5636: -- Fix Version/s: (was: 5.11.1) (was: 5.12.0) > Upgrade the bundled D

[jira] [Resolved] (AMQ-5592) AMQP: Pull in Proton JMS transformer code and refactor to enable both JMS mapping and support for AMQP clients

[ https://issues.apache.org/jira/browse/AMQ-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5592. --- Resolution: Fixed The Proton-J bits have been merged in and some refactoring has already been done

[jira] [Closed] (AMQ-5633) MapMessage.getBooleanProperty should probably throw if value not present

[ https://issues.apache.org/jira/browse/AMQ-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5633. - Resolution: Not a Problem This is working as the spec defines it to "Getting a property value for a

[jira] [Commented] (AMQ-5629) MapMessage.getChar does not handle if the backing map contains String or UTF8

[ https://issues.apache.org/jira/browse/AMQ-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346057#comment-14346057 ] Timothy Bish commented on AMQ-5629: --- You have to use getObject / setObject to manu

[jira] [Resolved] (AMQ-5629) MapMessage.getChar does not handle if the backing map contains String or UTF8

[ https://issues.apache.org/jira/browse/AMQ-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5629. --- Resolution: Not a Problem Assignee: Timothy Bish A String value can in fact not be read as a char

[jira] [Resolved] (AMQ-5628) MapMessage.getDouble uses Float when converting from String/UTF8

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

[jira] [Resolved] (AMQ-5632) MapMessage.getBytes crashes with NPE if no value present

[ https://issues.apache.org/jira/browse/AMQ-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5632. --- Resolution: Fixed Fix Version/s: 5.12.0 Assignee: Timothy Bish Added check for null and

[jira] [Resolved] (AMQ-5631) AMQP: Add support for delete of temporary destinations

[ https://issues.apache.org/jira/browse/AMQ-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5631. --- Resolution: Fixed Add support for the link that creates the temp destination to destroy it when closed

[jira] [Resolved] (AMQ-5593) AMQP: Implement support for Temporary Topics

[ https://issues.apache.org/jira/browse/AMQ-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5593. --- Resolution: Fixed Fixed this up on master. Added some tests and fixed some issues with error handling

[jira] [Created] (AMQ-5631) AMQP: Add support for delete of temporary destinations

Timothy Bish created AMQ-5631: - Summary: AMQP: Add support for delete of temporary destinations Key: AMQ-5631 URL: https://issues.apache.org/jira/browse/AMQ-5631 Project: ActiveMQ Issue Type

[jira] [Commented] (AMQ-5629) MapMessage.getChar does not handle if the backing map contains String or UTF8

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

[jira] [Resolved] (AMQ-5622) STOMP clients can only delete durable subscriptions when clientId equals subscriptionName

[ https://issues.apache.org/jira/browse/AMQ-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5622. --- Resolution: Fixed Fix Version/s: 5.12.0 Assignee: Timothy Bish Fix this and a couple

[jira] [Commented] (AMQ-5622) STOMP clients can only delete durable subscriptions when clientId equals subscriptionName

[ https://issues.apache.org/jira/browse/AMQ-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343369#comment-14343369 ] Timothy Bish commented on AMQ-5622: --- I'll take a look at it, I would expect it t

[jira] [Commented] (AMQ-5622) STOMP clients can only delete durable subscriptions when clientId equals subscriptionName

[ https://issues.apache.org/jira/browse/AMQ-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343223#comment-14343223 ] Timothy Bish commented on AMQ-5622: --- Are you using STOMP client in 1.1+ mode or a S

[jira] [Updated] (AMQ-5593) AMQP: Implement support for Temporary Topics

[ https://issues.apache.org/jira/browse/AMQ-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5593: -- Attachment: AMQ5593.patch First crack at this. Needs additional testing and review. > AMQP: Implem

[jira] [Commented] (AMQ-5606) AMQP: Update the AMQP 1.0 JMS client from QPid to v0.32 when released.

[ https://issues.apache.org/jira/browse/AMQ-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340676#comment-14340676 ] Timothy Bish commented on AMQ-5606: --- Master is now using the SNAPSHOTE 0.32 versio

[jira] [Commented] (AMQ-5560) AMQP: use type descriptors to inspect AMQP filter types rather than the map keys

[ https://issues.apache.org/jira/browse/AMQ-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340414#comment-14340414 ] Timothy Bish commented on AMQ-5560: --- Moved this to a subtask of AMQ-5591 since the

[jira] [Updated] (AMQ-5559) dont list filters which are not actually being applied in AMQP attach responses

[ https://issues.apache.org/jira/browse/AMQ-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5559: -- Issue Type: Sub-task (was: Bug) Parent: AMQ-5591 > dont list filters which are not actua

[jira] [Commented] (AMQ-5559) AMQP: dont list filters which are not actually being applied in AMQP attach responses

[ https://issues.apache.org/jira/browse/AMQ-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340412#comment-14340412 ] Timothy Bish commented on AMQ-5559: --- Made this a subtask of AMQ-5591 as it relate

[jira] [Updated] (AMQ-5560) use type descriptors to inspect AMQP filter types rather than the map keys

[ https://issues.apache.org/jira/browse/AMQ-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5560: -- Issue Type: Sub-task (was: Bug) Parent: AMQ-5591 > use type descriptors to inspect AMQP fil

[jira] [Updated] (AMQ-5560) AMQP: use type descriptors to inspect AMQP filter types rather than the map keys

[ https://issues.apache.org/jira/browse/AMQ-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5560: -- Summary: AMQP: use type descriptors to inspect AMQP filter types rather than the map keys (was: use type

[jira] [Updated] (AMQ-5559) AMQP: dont list filters which are not actually being applied in AMQP attach responses

[ https://issues.apache.org/jira/browse/AMQ-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5559: -- Summary: AMQP: dont list filters which are not actually being applied in AMQP attach responses (was

[jira] [Resolved] (AMQ-5597) AMQP: clean up durable subscription unsubscribe handling to simplify and resolve issues

[ https://issues.apache.org/jira/browse/AMQ-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5597. --- Resolution: Fixed Assignee: Timothy Bish AMQP receivers can now close with detach = true to leave

[jira] [Resolved] (AMQ-5617) AMQP: Remove direct usage of types from the legacy QPid JMS 1.0 client from the tests

[ https://issues.apache.org/jira/browse/AMQ-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5617. --- Resolution: Fixed refactored the existing tests to use a common context class to create connection

[jira] [Created] (AMQ-5621) Unit tests cleanup

Timothy Bish created AMQ-5621: - Summary: Unit tests cleanup Key: AMQ-5621 URL: https://issues.apache.org/jira/browse/AMQ-5621 Project: ActiveMQ Issue Type: Improvement Reporter

Re: enabling svngit2jira integration?

On 02/26/2015 12:30 PM, Robbie Gemmell wrote: Hi all, I was wondering what people thought about asking for the svngit2jira integration[1] being turned on for the ActiveMQ repo/JIRA? I find it very useful to know what work if any has ben done against a JIRA so far, and it can make tracking things

[jira] [Commented] (AMQ-3917) ActiveMQ should support multiple durable subscriptions per Stomp client

[ https://issues.apache.org/jira/browse/AMQ-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338680#comment-14338680 ] Timothy Bish commented on AMQ-3917: --- Added a note about that to the docs. > A

[jira] [Updated] (AMQ-5616) Declare variables as ConcurrentMap not ConcurrentHashMap to avoid issues after compiling on Java 8

[ https://issues.apache.org/jira/browse/AMQ-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5616: -- Attachment: AMQ5616.patch Initial pass at this task, need to validate and test full suite. > Decl

[jira] [Created] (AMQ-5617) AMQP: Remove direct usage of types from the legacy QPid JMS 1.0 client from the tests

Timothy Bish created AMQ-5617: - Summary: AMQP: Remove direct usage of types from the legacy QPid JMS 1.0 client from the tests Key: AMQ-5617 URL: https://issues.apache.org/jira/browse/AMQ-5617 Project

[jira] [Created] (AMQ-5616) Declare variables as ConcurrentMap not ConcurrentHashMap to avoid issues after compiling on Java 8

Timothy Bish created AMQ-5616: - Summary: Declare variables as ConcurrentMap not ConcurrentHashMap to avoid issues after compiling on Java 8 Key: AMQ-5616 URL: https://issues.apache.org/jira/browse/AMQ-5616

[jira] [Resolved] (AMQ-5615) AMQP: Connection open pump to socket twice in the error case when only once is needed.

[ https://issues.apache.org/jira/browse/AMQ-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5615. --- Resolution: Fixed Fixed on master. > AMQP: Connection open pump to socket twice in the error c

[jira] [Created] (AMQ-5615) AMQP: Connection open pump to socket twice in the error case when only once is needed.

Timothy Bish created AMQ-5615: - Summary: AMQP: Connection open pump to socket twice in the error case when only once is needed. Key: AMQ-5615 URL: https://issues.apache.org/jira/browse/AMQ-5615 Project

[jira] [Updated] (AMQ-5470) AMQP - delayed authentication from SASL connect leads to race on client end.

[ https://issues.apache.org/jira/browse/AMQ-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5470: -- Issue Type: Sub-task (was: Bug) Parent: AMQ-5591 > AMQP - delayed authentication from S

[jira] [Resolved] (AMQNET-498) Reduce log level of no consumer log in Connection to debug

[ https://issues.apache.org/jira/browse/AMQNET-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-498. - Resolution: Fixed Fixed on trunk and 1.6.x > Reduce log level of no consumer log in Connect

[jira] [Created] (AMQNET-498) Reduce log level of no consumer log in Connection to debug

Timothy Bish created AMQNET-498: --- Summary: Reduce log level of no consumer log in Connection to debug Key: AMQNET-498 URL: https://issues.apache.org/jira/browse/AMQNET-498 Project: ActiveMQ .Net

[jira] [Updated] (AMQ-5597) AMQP: clean up durable subscription unsubscribe handling to simplify and resolve issues

[ https://issues.apache.org/jira/browse/AMQ-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-5597: -- Attachment: AMQ-5597.patch Initial cut at implementing this bit, requires 0.32-SNAPSHOT of the AMQP 1.0

[jira] [Commented] (AMQ-5606) AMQP: Update the AMQP 1.0 JMS client from QPid to v0.32 when released.

[ https://issues.apache.org/jira/browse/AMQ-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333564#comment-14333564 ] Timothy Bish commented on AMQ-5606: --- Test using a snapshot and logged QPID-6404 to c

[jira] [Commented] (AMQ-5598) MQTT+NIO+SSL: Concurrent connections lead to 100% CPU usage

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

[jira] [Closed] (AMQCPP-565) Stop consumming messages after lost comunication (ActiveMQ C++ CLIENT 3.8.2)

[ https://issues.apache.org/jira/browse/AMQCPP-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQCPP-565. --- Resolution: Not a Problem When no consumers are active on a Topic messages are discarded so a Topic

[jira] [Resolved] (AMQ-5607) MQTT Tests can be sped up with some minimal changes

[ https://issues.apache.org/jira/browse/AMQ-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5607. --- Resolution: Fixed Made some improvement that shave off four to five minutes from the total run time

[jira] [Created] (AMQ-5607) MQTT Tests can be sped up with some minimal changes

Timothy Bish created AMQ-5607: - Summary: MQTT Tests can be sped up with some minimal changes Key: AMQ-5607 URL: https://issues.apache.org/jira/browse/AMQ-5607 Project: ActiveMQ Issue Type

[jira] [Created] (AMQ-5606) AMQP: Update the AMQP 1.0 JMS client from QPid to v0.32 when released.

Timothy Bish created AMQ-5606: - Summary: AMQP: Update the AMQP 1.0 JMS client from QPid to v0.32 when released. Key: AMQ-5606 URL: https://issues.apache.org/jira/browse/AMQ-5606 Project: ActiveMQ

[ANNOUNCE] ActiveMQ-CPP Version 3.8.4 Released

Hi Everyone, Its official, AcitveMQ-CPP v3.8.3 has now been released. This release contains a fixes for some issues found since the 3.8.3 release that improve overall client stability. The Wiki page for the release is here: The l

[jira] [Resolved] (AMQ-5604) AMQP: Clean up unit test start / stop code, excessive thread creation casuse slowdowns.

[ https://issues.apache.org/jira/browse/AMQ-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5604. --- Resolution: Fixed Fixed on master > AMQP: Clean up unit test start / stop code, excessive thr

[jira] [Created] (AMQ-5604) AMQP: Clean up unit test start / stop code, excessive thread creation casuse slowdowns.

Timothy Bish created AMQ-5604: - Summary: AMQP: Clean up unit test start / stop code, excessive thread creation casuse slowdowns. Key: AMQ-5604 URL: https://issues.apache.org/jira/browse/AMQ-5604 Project

[jira] [Created] (AMQ-5602) AMQP: Create simple Proton based client to be used in testing

Timothy Bish created AMQ-5602: - Summary: AMQP: Create simple Proton based client to be used in testing Key: AMQ-5602 URL: https://issues.apache.org/jira/browse/AMQ-5602 Project: ActiveMQ Issue

[RESULT][VOTE] Release ActiveMQ-CPP v3.8.4

Results of the ActiveMQ-CPP v3.8.4 vote: Vote passes with 5 binding +1 votes. The following binding votes were received: Claus Ibsen Timothy Bish Hiram Chirino Christian Posta Gary Tully I'll start pushing out the release bundles and update the Wiki. -- Tim Bish Sr Software Engineer | R

[jira] [Resolved] (AMQ-5596) Remove the deprecated JMS streams code

[ https://issues.apache.org/jira/browse/AMQ-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5596. --- Resolution: Fixed Removed the deprecated code from master. > Remove the deprecated JMS streams c

[jira] [Commented] (AMQ-5596) Remove the deprecated JMS streams code

[ https://issues.apache.org/jira/browse/AMQ-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326418#comment-14326418 ] Timothy Bish commented on AMQ-5596: --- Issue where the code was deprecated. > Rem

[jira] [Created] (AMQ-5596) Remove the deprecated JMS streams code

Timothy Bish created AMQ-5596: - Summary: Remove the deprecated JMS streams code Key: AMQ-5596 URL: https://issues.apache.org/jira/browse/AMQ-5596 Project: ActiveMQ Issue Type: Task

[jira] [Resolved] (AMQ-5595) Cleanup tests in activemq-jms-pool to fix some failures seen in Jenkins

[ https://issues.apache.org/jira/browse/AMQ-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5595. --- Resolution: Fixed fixed on master. > Cleanup tests in activemq-jms-pool to fix some failures seen

[jira] [Created] (AMQ-5595) Cleanup tests in activemq-jms-pool to fix some failures seen in Jenkins

Timothy Bish created AMQ-5595: - Summary: Cleanup tests in activemq-jms-pool to fix some failures seen in Jenkins Key: AMQ-5595 URL: https://issues.apache.org/jira/browse/AMQ-5595 Project: ActiveMQ

[jira] [Created] (AMQ-5593) AMQP: Implement support for Temporary Topics

Timothy Bish created AMQ-5593: - Summary: AMQP: Implement support for Temporary Topics Key: AMQ-5593 URL: https://issues.apache.org/jira/browse/AMQ-5593 Project: ActiveMQ Issue Type: Sub-task

[jira] [Created] (AMQ-5592) AMQP: Pull in Proton JMS transformer code and refactor to enable both JMS mapping and support for AMQP clients

Timothy Bish created AMQ-5592: - Summary: AMQP: Pull in Proton JMS transformer code and refactor to enable both JMS mapping and support for AMQP clients Key: AMQ-5592 URL: https://issues.apache.org/jira/browse/AMQ

[jira] [Created] (AMQ-5591) AMQP Implement the JMS Mapping spec as it evolves.

Timothy Bish created AMQ-5591: - Summary: AMQP Implement the JMS Mapping spec as it evolves. Key: AMQ-5591 URL: https://issues.apache.org/jira/browse/AMQ-5591 Project: ActiveMQ Issue Type

[jira] [Commented] (AMQ-5588) Failover transport should not hang on startup if it cannot connect & Failover transport timeout options overrides reconnection strategy

[ https://issues.apache.org/jira/browse/AMQ-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324329#comment-14324329 ] Timothy Bish commented on AMQ-5588: --- There was not fix applied for AMQ-2114 because

[jira] [Closed] (AMQ-5582) Queues stop sending to consumers after a threshold

[ https://issues.apache.org/jira/browse/AMQ-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-5582. - Resolution: Not a Problem This is working as currently designed. > Queues stop sending to consum

[jira] [Commented] (AMQ-5443) SSL client does not validate server certificate common name

[ https://issues.apache.org/jira/browse/AMQ-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324275#comment-14324275 ] Timothy Bish commented on AMQ-5443: --- Now that we require JDK v1.7 a simpler fix migh

[jira] [Resolved] (AMQ-5590) Reduce the time to run STOMP tests where possible.

[ https://issues.apache.org/jira/browse/AMQ-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5590. --- Resolution: Fixed Trimmed about 2 minutes off the tests, added JUnit timeouts etc. > Reduce the t

[jira] [Created] (AMQ-5590) Reduce the time to run STOMP tests where possible.

Timothy Bish created AMQ-5590: - Summary: Reduce the time to run STOMP tests where possible. Key: AMQ-5590 URL: https://issues.apache.org/jira/browse/AMQ-5590 Project: ActiveMQ Issue Type

[jira] [Resolved] (AMQ-5589) AMQP Module tests run much longer than necessary.

[ https://issues.apache.org/jira/browse/AMQ-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-5589. --- Resolution: Fixed Cleaned up and fix some issues, reduces overall time by about 2 minutes. > A

<    1   2   3   4   5   6   7   8   9   10   >