[
https://issues.apache.org/jira/browse/AMQ-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468478#comment-16468478
]
Tim Bain commented on AMQ-5730:
---
The same behavior was described by another user on the mailing list:
[
https://issues.apache.org/jira/browse/AMQ-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464578#comment-16464578
]
Tim Bain commented on AMQ-6938:
---
[~gtully] So I guess the other question is whether the capability implied in
[
https://issues.apache.org/jira/browse/AMQ-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464577#comment-16464577
]
Tim Bain commented on AMQ-6938:
---
[~gtully] If that's what that flag actually means in the code, then I think
[
https://issues.apache.org/jira/browse/AMQ-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-6938:
--
Description:
It was reported on the user mailing list
[
https://issues.apache.org/jira/browse/AMQ-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-6938:
--
Description:
It was reported on the user mailing list
[
https://issues.apache.org/jira/browse/AMQ-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455735#comment-16455735
]
Tim Bain commented on AMQ-6951:
---
Since
[
https://issues.apache.org/jira/browse/AMQ-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-6938:
--
Description:
It was reported on the user mailing list
[
https://issues.apache.org/jira/browse/AMQ-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-6938:
--
Description:
It was reported on the user mailing list
[
https://issues.apache.org/jira/browse/AMQ-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413351#comment-16413351
]
Tim Bain commented on AMQ-6938:
---
This appears to be part of the error described in AMQ-6929, but I've pulled
Tim Bain created AMQ-6938:
-
Summary: KahaDB's ignoreMissingJournalFiles argument doesn't
actually ignore missing journal files
Key: AMQ-6938
URL: https://issues.apache.org/jira/browse/AMQ-6938
Project:
[
https://issues.apache.org/jira/browse/AMQ-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409018#comment-16409018
]
Tim Bain commented on AMQ-6931:
---
[~gtully] The fix for AMQ-6815 doesn't handle the zero-length payload problem
[
https://issues.apache.org/jira/browse/AMQ-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-6931:
--
Description:
As reported on the users mailing list
[
https://issues.apache.org/jira/browse/AMQ-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397981#comment-16397981
]
Tim Bain commented on AMQ-3901:
---
This issue appears to be the same symptoms as AMQ-6902.
> ActiveMq hangs
[
https://issues.apache.org/jira/browse/AMQ-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307132#comment-16307132
]
Tim Bain commented on AMQ-6823:
---
Do we believe that this was introduced in 5.14.5 as indicated by the Affects
Tim Bain created AMQ-6864:
-
Summary: Add appropriate Java 9 JVM arguments to allow reflective
access to sun.* classes
Key: AMQ-6864
URL: https://issues.apache.org/jira/browse/AMQ-6864
Project: ActiveMQ
Tim Bain created AMQ-6773:
-
Summary: Calling external code while holding a lock sometimes
results in deadlock
Key: AMQ-6773
URL: https://issues.apache.org/jira/browse/AMQ-6773
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972064#comment-15972064
]
Tim Bain commented on AMQ-6470:
---
Although I fully approve of cleaning out old code, including this in an
[
https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730947#comment-15730947
]
Tim Bain commented on AMQ-6441:
---
The one downside to Gary's implementation is that if you use this option,
[
https://issues.apache.org/jira/browse/AMQ-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610533#comment-15610533
]
Tim Bain edited comment on AMQ-3978 at 10/27/16 3:35 AM:
-
AMQ-6203 reduces the
[
https://issues.apache.org/jira/browse/AMQ-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610533#comment-15610533
]
Tim Bain commented on AMQ-3978:
---
I believe that AMQ-6203 reduces the severity of the problem by allowing the
[
https://issues.apache.org/jira/browse/AMQ-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15547690#comment-15547690
]
Tim Bain commented on AMQ-6453:
---
Original user mailing list thread with considerably more detail:
[
https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532690#comment-15532690
]
Tim Bain commented on AMQ-6441:
---
I recommend rejecting this pull request, and reworking the change to include
[
https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532687#comment-15532687
]
Tim Bain commented on AMQ-6441:
---
This approach addresses the immediate problem, with an 8 EB volume. It will
[
https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526064#comment-15526064
]
Tim Bain commented on AMQ-6441:
---
Let's start with reopening the bug. No one will contribute code for a bug
[
https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526017#comment-15526017
]
Tim Bain commented on AMQ-6441:
---
I don't agree that there's nothing we can do, and I think this bug should be
[
https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525992#comment-15525992
]
Tim Bain commented on AMQ-6441:
---
An OpenJDK bug was opened about this issue:
[
https://issues.apache.org/jira/browse/AMQ-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489570#comment-15489570
]
Tim Bain commented on AMQ-5995:
---
You're right, there shouldn't be any reference to KahaDB specifically in that
[
https://issues.apache.org/jira/browse/AMQ-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-6099:
--
Description:
The current persistence store implementation only allows a single OpenWire
version to be read from
[
https://issues.apache.org/jira/browse/AMQ-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486323#comment-15486323
]
Tim Bain commented on AMQ-5995:
---
After proposing the above, I submitted AMQ-6099 to request the ability for a
[
https://issues.apache.org/jira/browse/AMQ-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235057#comment-15235057
]
Tim Bain commented on AMQ-6239:
---
This algorithm isn't thread-safe in the face of concurrent removals, so if we
[
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101802#comment-15101802
]
Tim Bain commented on AMQ-6052:
---
Can we back-port this issue to any future patch releases we do (5.13.1 at a
[
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101813#comment-15101813
]
Tim Bain commented on AMQ-6052:
---
Also note that a workaround is to set the logging level to ERROR for
[
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101971#comment-15101971
]
Tim Bain commented on AMQ-6052:
---
Great, thanks.
> Network of brokers on duplex mode reports
[
https://issues.apache.org/jira/browse/AMQ-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-6099:
--
Description:
The current KahaDB implementation only allows a single OpenWire version to be
read from the store.
[
https://issues.apache.org/jira/browse/AMQ-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067515#comment-15067515
]
Tim Bain commented on AMQ-6099:
---
Also, I'm not convinced you'd ever have more than 2 versions at once; you'd
[
https://issues.apache.org/jira/browse/AMQ-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067558#comment-15067558
]
Tim Bain commented on AMQ-6099:
---
I was imagining that you'd simply try your best guess (the version that will
[
https://issues.apache.org/jira/browse/AMQ-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067554#comment-15067554
]
Tim Bain commented on AMQ-6099:
---
I reread AMQ-5995 and realized I hadn't caught that it was written in
Tim Bain created AMQ-6103:
-
Summary: Provide command-line utility to migrate KahaDB files to a
new OpenWire version
Key: AMQ-6103
URL: https://issues.apache.org/jira/browse/AMQ-6103
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067523#comment-15067523
]
Tim Bain commented on AMQ-6103:
---
Split out from AMQ-6099 into a stand-alone issue.
> Provide command-line
[
https://issues.apache.org/jira/browse/AMQ-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067513#comment-15067513
]
Tim Bain commented on AMQ-6099:
---
[~cshannon] Are you sure that KahaDB will automatically detect the older
Tim Bain created AMQ-6099:
-
Summary: Allow broker to read any OpenWire version from KahaDB
Key: AMQ-6099
URL: https://issues.apache.org/jira/browse/AMQ-6099
Project: ActiveMQ
Issue Type: New Feature
Tim Bain created AMQ-6098:
-
Summary: Allow clients to NACK a message in INDIVIDUAL_ACKNOWLEDGE
mode
Key: AMQ-6098
URL: https://issues.apache.org/jira/browse/AMQ-6098
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064352#comment-15064352
]
Tim Bain commented on AMQ-5545:
---
This is not a bug. Electing to use message groups is an explicit choice to
[
https://issues.apache.org/jira/browse/AMQ-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742286#comment-14742286
]
Tim Bain commented on AMQ-3978:
---
If you don't use mKahaDB, you might get better performance from using very
[
https://issues.apache.org/jira/browse/AMQ-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-5161:
--
Comment: was deleted
(was: According to Jeremie Brebec on the users mailing list
Tim Bain created AMQ-5905:
-
Summary: Allow KahaDB to perform compaction of sparsely-used data
files
Key: AMQ-5905
URL: https://issues.apache.org/jira/browse/AMQ-5905
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644363#comment-14644363
]
Tim Bain commented on AMQ-5161:
---
According to Jeremie Brebec on the users mailing list
[
https://issues.apache.org/jira/browse/AMQ-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-3978:
--
Component/s: KahaDB
Allow KahaDB to compact journal files to remove messages that are no longer
needed
[
https://issues.apache.org/jira/browse/AMQ-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-3978:
--
Description:
KahaDB uses a write-only journaling approach that ensures that a journal file
will be deleted only
[
https://issues.apache.org/jira/browse/AMQ-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-5905:
--
Component/s: Message Store
Allow KahaDB to perform compaction of sparsely-used data files
[
https://issues.apache.org/jira/browse/AMQ-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Bain updated AMQ-5905:
--
Description:
As currently implemented, KahaDB can only reduce data file usage by deleting an
entire data file.
[
https://issues.apache.org/jira/browse/AMQ-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1469#comment-1469
]
Tim Bain commented on AMQ-4093:
---
Recommend closing as a duplicate of AMQ-3978.
Auto
[
https://issues.apache.org/jira/browse/AMQ-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644450#comment-14644450
]
Tim Bain commented on AMQ-5905:
---
Embarrassingly, I'm the author of two of those three but
[
https://issues.apache.org/jira/browse/AMQ-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14581393#comment-14581393
]
Tim Bain commented on AMQ-5825:
---
TreeSet will only work if you do what I suggest about keeping
Tim Bain created AMQ-5824:
-
Summary: Improve performance of
ManagedRegionBroker.removeConsumer()
Key: AMQ-5824
URL: https://issues.apache.org/jira/browse/AMQ-5824
Project: ActiveMQ
Issue Type: Bug
Tim Bain created AMQ-5825:
-
Summary: Improve performance of Queue.addToConsumerList()
Key: AMQ-5825
URL: https://issues.apache.org/jira/browse/AMQ-5825
Project: ActiveMQ
Issue Type: Bug
56 matches
Mail list logo
