[jira] [Resolved] (AMQ-6603) Excessive number of consumers when used with PooledConnectionFactory and Failover transport

[ https://issues.apache.org/jira/browse/AMQ-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6603. - Resolution: Fixed Fix Version/s: 5.15.0 Thanks for the follow up [~tabish121] :-) > Excessive

[jira] [Commented] (AMQ-6603) Excessive number of consumers when used with PooledConnectionFactory and Failover transport

[ https://issues.apache.org/jira/browse/AMQ-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888349#comment-15888349 ] Gary Tully commented on AMQ-6603: - I think there is something in this. The consumer creation failing with an

[jira] [Assigned] (AMQ-6603) Excessive number of consumers when used with PooledConnectionFactory and Failover transport

[ https://issues.apache.org/jira/browse/AMQ-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-6603: --- Assignee: Gary Tully > Excessive number of consumers when used with PooledConnectionFactory and >

[jira] [Commented] (AMQ-6414) The nio+ssl transports can block and hang on connection in certain situations

[ https://issues.apache.org/jira/browse/AMQ-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887825#comment-15887825 ] Gary Tully commented on AMQ-6414: - [~cshannon] I think it is ok as it is now, so long as we don't get a

[jira] [Commented] (AMQ-6414) The nio+ssl transports can block and hang on connection in certain situations

[ https://issues.apache.org/jira/browse/AMQ-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15886106#comment-15886106 ] Gary Tully commented on AMQ-6414: - I was digging into this fix from another angle, hence the additional

[jira] [Commented] (AMQ-6494) Exceptions and timeouts during shutdown of connectors

[ https://issues.apache.org/jira/browse/AMQ-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878266#comment-15878266 ] Gary Tully commented on AMQ-6494: - There are a few tests in the activemq.all set that fail (65+ runs) with

[jira] [Resolved] (AMQ-6606) Journal partial write can result in batch corruption on restart

[ https://issues.apache.org/jira/browse/AMQ-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6606. - Resolution: Fixed > Journal partial write can result in batch corruption on restart >

[jira] [Created] (AMQ-6606) Journal partial write can result in batch corruption on restart

Gary Tully created AMQ-6606: --- Summary: Journal partial write can result in batch corruption on restart Key: AMQ-6606 URL: https://issues.apache.org/jira/browse/AMQ-6606 Project: ActiveMQ Issue

[jira] [Commented] (AMQ-5867) Refresh SSL context through a custom SslContext implementation

[ https://issues.apache.org/jira/browse/AMQ-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867664#comment-15867664 ] Gary Tully commented on AMQ-5867: - [~thodimi] that seems sensible however it may be better to have the

[jira] [Commented] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

[ https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15861541#comment-15861541 ] Gary Tully commented on AMQ-6587: - note: the root cause could result in a wildcard sub missing a newly

[jira] [Resolved] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

[ https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6587. - Resolution: Fixed [~cshannon] note the additional fix for a second variant of this problem > Failed to

[jira] [Comment Edited] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

[ https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856023#comment-15856023 ] Gary Tully edited comment on AMQ-6587 at 2/7/17 1:56 PM: - This warn/error can also

[jira] [Comment Edited] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

[ https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856023#comment-15856023 ] Gary Tully edited comment on AMQ-6587 at 2/7/17 1:56 PM: - This warn/error can also

[jira] [Reopened] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

[ https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reopened AMQ-6587: - This warn can also appear when a wildcard sub arrived during the gc process > Failed to remove inactive

[jira] [Resolved] (AMQ-6432) Improve 'Failed to load next journal location: null' warning output

[ https://issues.apache.org/jira/browse/AMQ-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6432. - Resolution: Fixed Fix Version/s: 5.15.0 issue was not related to syncs but doing a scan for acks

[jira] [Updated] (AMQ-6432) Improve 'Failed to load next journal location: null' warning output

[ https://issues.apache.org/jira/browse/AMQ-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-6432: Issue Type: Bug (was: Improvement) > Improve 'Failed to load next journal location: null' warning output >

[jira] [Assigned] (AMQ-6432) Improve 'Failed to load next journal location: null' warning output

[ https://issues.apache.org/jira/browse/AMQ-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-6432: --- Assignee: Gary Tully > Improve 'Failed to load next journal location: null' warning output >

[jira] [Commented] (AMQ-6590) KahaDB index loses track of free pages on unclean shutdown

[ https://issues.apache.org/jira/browse/AMQ-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850004#comment-15850004 ] Gary Tully commented on AMQ-6590: - [~cshannon] sure. that fix does look correct and is a great catch. >

[jira] [Commented] (AMQ-6432) Improve 'Failed to load next journal location: null' warning output

[ https://issues.apache.org/jira/browse/AMQ-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849854#comment-15849854 ] Gary Tully commented on AMQ-6432: - if the trigger is a purge, it may be that the acks are not synced, and

[jira] [Resolved] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

[ https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6587. - Resolution: Fixed Fix Version/s: 5.15.0 > Failed to remove inactive destination Topic: Destination

[jira] [Updated] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

[ https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-6587: Affects Version/s: 5.14.0 > Failed to remove inactive destination Topic: Destination still has an active >

[jira] [Commented] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

[ https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848249#comment-15848249 ] Gary Tully commented on AMQ-6587: - The fix for AMQ-6188 which resets lastActiveTime on publish/send helps

[jira] [Commented] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

[ https://issues.apache.org/jira/browse/AMQ-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848247#comment-15848247 ] Gary Tully commented on AMQ-6587: - There is some locking in RegionBroker using

[jira] [Created] (AMQ-6587) Failed to remove inactive destination Topic: Destination still has an active subscription

Gary Tully created AMQ-6587: --- Summary: Failed to remove inactive destination Topic: Destination still has an active subscription Key: AMQ-6587 URL: https://issues.apache.org/jira/browse/AMQ-6587 Project:

[jira] (AMQ-6585) Upgrade to Camel 2.18.x

Title: Message Title Gary Tully commented on AMQ-6585

[jira] [Resolved] (AMQ-6571) HttpClientTransport refuses to accept cookies using `Expires' header

[ https://issues.apache.org/jira/browse/AMQ-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6571. - Resolution: Fixed Fix Version/s: 5.15.0 patch applied with thanks. > HttpClientTransport refuses to

[jira] [Commented] (AMQ-1940) Negative queue size (reproducible)

[ https://issues.apache.org/jira/browse/AMQ-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831728#comment-15831728 ] Gary Tully commented on AMQ-1940: - I don't think perf is a problem with the purge operation. an all out

[jira] [Comment Edited] (AMQ-6571) HttpClientTransport refuses to accept cookies using `Expires' header

[ https://issues.apache.org/jira/browse/AMQ-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831669#comment-15831669 ] Gary Tully edited comment on AMQ-6571 at 1/20/17 12:44 PM: --- Thanks for the patch.

[jira] [Commented] (AMQ-6571) HttpClientTransport refuses to accept cookies using `Expires' header

[ https://issues.apache.org/jira/browse/AMQ-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831669#comment-15831669 ] Gary Tully commented on AMQ-6571: - Thanks for the patch. I wonder if there us a use case where this option

[jira] [Commented] (AMQ-6568) Consumers stop consuming

[ https://issues.apache.org/jira/browse/AMQ-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828185#comment-15828185 ] Gary Tully commented on AMQ-6568: - [~andreasgies] hope all is well :-) One thought is to check the memory

[jira] [Commented] (AMQ-6545) Deadlock can occur during journal file rotation

[ https://issues.apache.org/jira/browse/AMQ-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827933#comment-15827933 ] Gary Tully commented on AMQ-6545: - nice catch [~cshannon] :-) > Deadlock can occur during journal file

[jira] [Resolved] (AMQ-6567) Broker failure when deleting files in gc can cause missing journal errors on restart

[ https://issues.apache.org/jira/browse/AMQ-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6567. - Resolution: Fixed > Broker failure when deleting files in gc can cause missing journal errors on > restart

[jira] [Resolved] (AMQ-6548) Commit messages on exception

[ https://issues.apache.org/jira/browse/AMQ-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6548. - Resolution: Fixed Fix Version/s: 5.15.0 it makes sense to force rollbackOnly on delivery failure due

[jira] [Assigned] (AMQ-6548) Commit messages on exception

[ https://issues.apache.org/jira/browse/AMQ-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-6548: --- Assignee: Gary Tully > Commit messages on exception > > >

[jira] [Created] (AMQ-6567) Broker failure when deleting files in gc can cause missing journal errors on restart

Gary Tully created AMQ-6567: --- Summary: Broker failure when deleting files in gc can cause missing journal errors on restart Key: AMQ-6567 URL: https://issues.apache.org/jira/browse/AMQ-6567 Project:

[jira] [Commented] (AMQ-6548) Commit messages on exception

[ https://issues.apache.org/jira/browse/AMQ-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823890#comment-15823890 ] Gary Tully commented on AMQ-6548: - would it be possible to build a test case or unit test that will

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

[ https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821635#comment-15821635 ] Gary Tully edited comment on AMQ-5249 at 1/13/17 11:13 AM: --- For the durable topic

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

[ https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821635#comment-15821635 ] Gary Tully edited comment on AMQ-5249 at 1/13/17 11:12 AM: --- For the durable topic

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

[ https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821635#comment-15821635 ] Gary Tully commented on AMQ-5249: - For the durable topic sub case the scenario is captures in

[jira] [Resolved] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

[ https://issues.apache.org/jira/browse/AMQ-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6562. - Resolution: Fixed > WARN TopicStorePrefetch cursor got duplicate from store >

[jira] [Comment Edited] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

[ https://issues.apache.org/jira/browse/AMQ-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821598#comment-15821598 ] Gary Tully edited comment on AMQ-6562 at 1/13/17 10:51 AM: --- The WARN is expected

[jira] [Comment Edited] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

[ https://issues.apache.org/jira/browse/AMQ-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821598#comment-15821598 ] Gary Tully edited comment on AMQ-6562 at 1/13/17 10:50 AM: --- The WARN is expected

[jira] [Commented] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

[ https://issues.apache.org/jira/browse/AMQ-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821598#comment-15821598 ] Gary Tully commented on AMQ-6562: - The WARN is expected when the cache is exhausted and page in begins at

[jira] [Created] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

Gary Tully created AMQ-6562: --- Summary: WARN TopicStorePrefetch cursor got duplicate from store Key: AMQ-6562 URL: https://issues.apache.org/jira/browse/AMQ-6562 Project: ActiveMQ Issue Type: Bug

[jira] [Comment Edited] (AMQ-6424) Duplicate dead letter queues

[ https://issues.apache.org/jira/browse/AMQ-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820885#comment-15820885 ] Gary Tully edited comment on AMQ-6424 at 1/12/17 12:27 PM: --- as a possible

[jira] [Commented] (AMQ-6424) Duplicate dead letter queues

[ https://issues.apache.org/jira/browse/AMQ-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820885#comment-15820885 ] Gary Tully commented on AMQ-6424: - as a possible workaround you could provide a "discarding" dead letter

[jira] [Commented] (AMQ-4467) Memory usage percent can be exceeded much if PFC is disabled

[ https://issues.apache.org/jira/browse/AMQ-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814953#comment-15814953 ] Gary Tully commented on AMQ-4467: - Thanks for the feedback @Christopher L], It can stop dispatch which is a

[jira] [Resolved] (AMQ-4467) Memory usage percent can be exceeded much if PFC is disabled

[ https://issues.apache.org/jira/browse/AMQ-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-4467. - Resolution: Fixed Fix Version/s: (was: 5.9.0) 5.15.0 shared limit check now

[jira] [Reopened] (AMQ-4467) Memory usage percent can be exceeded much if PFC is disabled

[ https://issues.apache.org/jira/browse/AMQ-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reopened AMQ-4467: - Assignee: Gary Tully (was: Dejan Bosanac) The fix applies the cursor high water mark value to the shared

[jira] [Resolved] (AMQ-6547) mKahaDB: support storeUsage per filtered instance

[ https://issues.apache.org/jira/browse/AMQ-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6547. - Resolution: Fixed Additional usage attribute:{code}

[jira] [Created] (AMQ-6547) mKahaDB: support storeUsage per filtered instance

Gary Tully created AMQ-6547: --- Summary: mKahaDB: support storeUsage per filtered instance Key: AMQ-6547 URL: https://issues.apache.org/jira/browse/AMQ-6547 Project: ActiveMQ Issue Type: Improvement

[jira] [Commented] (AMQ-6539) Duplex message across cluster not work on ActiveMQ 5.14.2

[ https://issues.apache.org/jira/browse/AMQ-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748107#comment-15748107 ] Gary Tully commented on AMQ-6539: - you should use masteSlave in place of static failover, see:

[jira] [Commented] (AMQ-6534) QueueBrowser can view messages being processed by consumers which are not yet acknowledged

[ https://issues.apache.org/jira/browse/AMQ-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15744852#comment-15744852 ] Gary Tully commented on AMQ-6534: - [~yogu13] it is not assigned to anyone so please do. Contributions are

[jira] [Commented] (AMQ-6534) QueueBrowser can view messages being processed by consumers which are not yet acknowledged

[ https://issues.apache.org/jira/browse/AMQ-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741664#comment-15741664 ] Gary Tully commented on AMQ-6534: - https://issues.apache.org/jira/browse/AMQ-5274 may have the fix that

[jira] [Commented] (AMQ-6534) QueueBrowser can view messages being processed by consumers which are not yet acknowledged

[ https://issues.apache.org/jira/browse/AMQ-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741661#comment-15741661 ] Gary Tully commented on AMQ-6534: - there is a related fix: https://issues.apache.org/jira/browse/AMQ-5274

[jira] [Resolved] (AMQ-6441) Incorrect File System Size Reported with Amazon Elastic File System (EFS)

[ https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6441. - Resolution: Fixed Fix Version/s: 5.15.0 I added a PercentUsage section at the end of[1] that covers

[jira] [Commented] (AMQ-6441) Incorrect File System Size Reported with Amazon Elastic File System (EFS)

[ https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729456#comment-15729456 ] Gary Tully commented on AMQ-6441: - with the above changes a negative value from the filesystem will error

[jira] [Commented] (AMQ-6441) Incorrect File System Size Reported with Amazon Elastic File System (EFS)

[ https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728934#comment-15728934 ] Gary Tully commented on AMQ-6441: - I had a peek at this and think maybe this can be recast as allowing the

[jira] [Resolved] (AMQ-6526) Exception occurred processing: -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded

[ https://issues.apache.org/jira/browse/AMQ-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6526. - Resolution: Fixed Fix Version/s: 5.15.0 > Exception occurred processing: -> >

[jira] [Resolved] (AMQ-6515) Install of activemq-blueprint fails as javax.inject is missing

[ https://issues.apache.org/jira/browse/AMQ-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6515. - Resolution: Fixed the analysis via bnd pulls in the import from the dependent jar references unless there

[jira] [Comment Edited] (AMQ-6515) Install of activemq-blueprint fails as javax.inject is missing

[ https://issues.apache.org/jira/browse/AMQ-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15725165#comment-15725165 ] Gary Tully edited comment on AMQ-6515 at 12/6/16 11:25 AM: --- with guava 18,

[jira] [Reopened] (AMQ-6515) Install of activemq-blueprint fails as javax.inject is missing

[ https://issues.apache.org/jira/browse/AMQ-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reopened AMQ-6515: - Assignee: Gary Tully with guava 18, activemq-osig gets another spurious import in error. A workaround to

[jira] [Commented] (AMQ-6515) Install of activemq-blueprint fails as javax.inject is missing

[ https://issues.apache.org/jira/browse/AMQ-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715053#comment-15715053 ] Gary Tully commented on AMQ-6515: - the root cause of this issue was a leaked export-package of inject from

[jira] [Commented] (AMQ-6452) Geronimo transaction manager dependency version should be upgraded

[ https://issues.apache.org/jira/browse/AMQ-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15708405#comment-15708405 ] Gary Tully commented on AMQ-6452: - I just noticed that this version pulls in j2ee-connector_1.6_spec and our

[jira] [Resolved] (AMQ-6522) KahaDB - checkForCorruptJournalFiles has hard coded 32k batch size limit in error

[ https://issues.apache.org/jira/browse/AMQ-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6522. - Resolution: Fixed > KahaDB - checkForCorruptJournalFiles has hard coded 32k batch size limit in > error >

[jira] [Comment Edited] (AMQ-6522) KahaDB - checkForCorruptJournalFiles has hard coded 32k batch size limit in error

[ https://issues.apache.org/jira/browse/AMQ-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705032#comment-15705032 ] Gary Tully edited comment on AMQ-6522 at 11/29/16 11:35 AM: symptom with a

[jira] [Commented] (AMQ-6522) KahaDB - checkForCorruptJournalFiles has hard coded 32k batch size limit in error

[ https://issues.apache.org/jira/browse/AMQ-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705032#comment-15705032 ] Gary Tully commented on AMQ-6522: - symptom with a message > 32k in size{code} 14:23:16,374 | ERROR |

[jira] [Created] (AMQ-6522) KahaDB - checkForCorruptJournalFiles has hard coded 32k batch size limit in error

Gary Tully created AMQ-6522: --- Summary: KahaDB - checkForCorruptJournalFiles has hard coded 32k batch size limit in error Key: AMQ-6522 URL: https://issues.apache.org/jira/browse/AMQ-6522 Project: ActiveMQ

[jira] [Resolved] (AMQ-6520) support indexDirectory attribute via mKahaDB

[ https://issues.apache.org/jira/browse/AMQ-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6520. - Resolution: Fixed > support indexDirectory attribute via mKahaDB >

[jira] [Created] (AMQ-6520) support indexDirectory attribute via mKahaDB

Gary Tully created AMQ-6520: --- Summary: support indexDirectory attribute via mKahaDB Key: AMQ-6520 URL: https://issues.apache.org/jira/browse/AMQ-6520 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (AMQ-6519) [doc] re-work section "Pooled Consumers and Prefetch" on prefetch documentation

[ https://issues.apache.org/jira/browse/AMQ-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696198#comment-15696198 ] Gary Tully commented on AMQ-6519: - good update. Cast your eyes over

[jira] [Resolved] (AMQ-6518) Statistics plugin shows wrong value for average message size

[ https://issues.apache.org/jira/browse/AMQ-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6518. - Resolution: Fixed thanks for the report and fix identification. > Statistics plugin shows wrong value for

[jira] [Assigned] (AMQ-6518) Statistics plugin shows wrong value for average message size

[ https://issues.apache.org/jira/browse/AMQ-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-6518: --- Assignee: Gary Tully > Statistics plugin shows wrong value for average message size >

[jira] [Resolved] (AMQ-6517) Make redelivery policy preDispatch check optional

[ https://issues.apache.org/jira/browse/AMQ-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6517. - Resolution: Fixed > Make redelivery policy preDispatch check optional >

[jira] [Created] (AMQ-6517) Make redelivery policy preDispatch check optional

Gary Tully created AMQ-6517: --- Summary: Make redelivery policy preDispatch check optional Key: AMQ-6517 URL: https://issues.apache.org/jira/browse/AMQ-6517 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (AMQ-6509) localHostName is anounced instead of the host IP

[ https://issues.apache.org/jira/browse/AMQ-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689900#comment-15689900 ] Gary Tully commented on AMQ-6509: - see: https://issues.apache.org/jira/browse/AMQ-4024 The fix for that

[jira] [Commented] (AMQ-3166) client calls to createProducer() and send() successful even though BrokerFilter methods throw exceptions

[ https://issues.apache.org/jira/browse/AMQ-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687138#comment-15687138 ] Gary Tully commented on AMQ-3166: - [~jahlborn] thanks for the suggestion. I swapped the boolean for a

[jira] [Commented] (AMQ-6514) Property placeholders do not work in blueprint activemq config

[ https://issues.apache.org/jira/browse/AMQ-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15686340#comment-15686340 ] Gary Tully commented on AMQ-6514: - it would be smashing to have an additional test in activemq-karaf-itest

[jira] [Updated] (AMQ-4944) Implement reliable forwarding in broker networks

[ https://issues.apache.org/jira/browse/AMQ-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-4944: Fix Version/s: (was: 5.15.0) > Implement reliable forwarding in broker networks >

[jira] [Commented] (AMQ-6477) ReduceMemoryFootprint should apply to non-persistent messages and subscriptions

[ https://issues.apache.org/jira/browse/AMQ-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602237#comment-15602237 ] Gary Tully commented on AMQ-6477: - [~cshannon] looks good one thought: I guess it also means that on

[jira] [Commented] (AMQ-6395) JMX 'DLQ' flag is not true for dead letter queues

[ https://issues.apache.org/jira/browse/AMQ-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15581680#comment-15581680 ] Gary Tully commented on AMQ-6395: - [~lichtin] that flag is set on first usage of a destination as a dlq;

[jira] [Resolved] (AMQ-6463) NPE on scheduler send via blocked waiting for space task

[ https://issues.apache.org/jira/browse/AMQ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6463. - Resolution: Fixed fix and test. Added connection that will warn on error responses to the send. this

[jira] [Created] (AMQ-6463) NPE on scheduler send via blocked waiting for space

Gary Tully created AMQ-6463: --- Summary: NPE on scheduler send via blocked waiting for space Key: AMQ-6463 URL: https://issues.apache.org/jira/browse/AMQ-6463 Project: ActiveMQ Issue Type: Bug

[jira] [Updated] (AMQ-6463) NPE on scheduler send via blocked waiting for space task

[ https://issues.apache.org/jira/browse/AMQ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-6463: Summary: NPE on scheduler send via blocked waiting for space task (was: NPE on scheduler send via blocked

[jira] [Commented] (AMQ-6454) Message is redelivered after succesfull acknowledge()

[ https://issues.apache.org/jira/browse/AMQ-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1409#comment-1409 ] Gary Tully commented on AMQ-6454: - yes, that would be in the intent. When the broker url is: host:port?jms

[jira] [Created] (AMQ-6459) JMX broker view attribute tempPercentUsage does not decrease

Gary Tully created AMQ-6459: --- Summary: JMX broker view attribute tempPercentUsage does not decrease Key: AMQ-6459 URL: https://issues.apache.org/jira/browse/AMQ-6459 Project: ActiveMQ Issue

[jira] [Commented] (AMQ-6454) Message is redelivered after succesfull acknowledge()

[ https://issues.apache.org/jira/browse/AMQ-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554594#comment-15554594 ] Gary Tully commented on AMQ-6454: - What would be a good name for the connection factory config option that

[jira] [Commented] (AMQ-6456) Exclusive consumer may stop consuming in broker network

[ https://issues.apache.org/jira/browse/AMQ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552050#comment-15552050 ] Gary Tully commented on AMQ-6456: - yes. and by stop working - messages will get isolated on a broker because

[jira] [Commented] (AMQ-6456) Exclusive consumer may stop consuming in broker network

[ https://issues.apache.org/jira/browse/AMQ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551986#comment-15551986 ] Gary Tully commented on AMQ-6456: - if by fundamentally you mean "in a network of brokers" then yes. >

[jira] [Commented] (AMQ-6454) Message is redelivered after succesfull acknowledge()

[ https://issues.apache.org/jira/browse/AMQ-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551708#comment-15551708 ] Gary Tully commented on AMQ-6454: - This essentially comes down to being able to do the following: {code}

[jira] [Commented] (AMQ-6456) Exclusive consumer may stop consuming in broker network

[ https://issues.apache.org/jira/browse/AMQ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551469#comment-15551469 ] Gary Tully commented on AMQ-6456: - the exclusive *choice* is local to a broker. If there are two brokers

[jira] [Commented] (AMQ-6454) Message is redelivered after succesfull acknowledge()

[ https://issues.apache.org/jira/browse/AMQ-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549300#comment-15549300 ] Gary Tully commented on AMQ-6454: - actually the fix may be a simple as deferring the close in this case, the

[jira] [Commented] (AMQ-6456) Exclusive consumer may stop consuming in broker network

[ https://issues.apache.org/jira/browse/AMQ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549109#comment-15549109 ] Gary Tully commented on AMQ-6456: - This is a little difficult to reason about because the "choice" of a

[jira] [Commented] (AMQ-6456) Exclusive consumer may stop consuming in broker network

[ https://issues.apache.org/jira/browse/AMQ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549026#comment-15549026 ] Gary Tully commented on AMQ-6456: - there are some unit tests that may help build a junit test case (they

[jira] [Commented] (AMQ-6454) Message is redelivered after succesfull acknowledge()

[ https://issues.apache.org/jira/browse/AMQ-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15548264#comment-15548264 ] Gary Tully commented on AMQ-6454: - What you describe does look like the correct behaviour w.r.t the java

[jira] [Updated] (AMQ-6446) New org.slf4j.Logger instance created for every new connection but never cleared when transport listener is configured for trace=true

[ https://issues.apache.org/jira/browse/AMQ-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-6446: Description: Configuring the broker for transport

[jira] [Resolved] (AMQ-6446) New org.slf4j.Logger instance created for every new connection but never cleared when transport listener is configured for trace=true

[ https://issues.apache.org/jira/browse/AMQ-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6446. - Resolution: Fixed > New org.slf4j.Logger instance created for every new connection but never > cleared

[jira] [Created] (AMQ-6446) New org.slf4j.Logger instance created for every new connection but never cleared when transport listener is configured for trace=true

Gary Tully created AMQ-6446: --- Summary: New org.slf4j.Logger instance created for every new connection but never cleared when transport listener is configured for trace=true Key: AMQ-6446 URL:

[jira] [Resolved] (AMQ-6184) Improve nio transport scalability

[ https://issues.apache.org/jira/browse/AMQ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6184. - Resolution: Fixed Fix Version/s: (was: 5.14.0) 5.15.0 We need the best of

[jira] [Reopened] (AMQ-6184) Improve nio transport scalability

[ https://issues.apache.org/jira/browse/AMQ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reopened AMQ-6184: - Assignee: Gary Tully (was: Dejan Bosanac) The change from SynchronousQueue to BlockingQueue(1k) impacts

<    7   8   9   10   11   12   13   14   15   >