[
https://issues.apache.org/jira/browse/AMQ-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16684081#comment-16684081
]
Gary Tully commented on AMQ-7091:
-
[~tabish121] thanks. [~jgenender] Probably no need for any config option
[
https://issues.apache.org/jira/browse/AMQ-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683923#comment-16683923
]
Gary Tully commented on AMQ-7091:
-
[~tabish121] Hi tim, you added the messageReferences cache way back in
[
https://issues.apache.org/jira/browse/AMQ-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16679675#comment-16679675
]
Gary Tully commented on AMQ-7094:
-
new log:
{code}
2018-11-07 17:50:42,118 [on(2)-127.0.0.1] - INFO audit
[
https://issues.apache.org/jira/browse/AMQ-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16679675#comment-16679675
]
Gary Tully edited comment on AMQ-7094 at 11/8/18 12:18 PM:
---
new log:
{code}
Gary Tully created AMQ-7094:
---
Summary: AuditLog should show the target of the operation and not
just arguments
Key: AMQ-7094
URL: https://issues.apache.org/jira/browse/AMQ-7094
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7094.
-
Resolution: Fixed
> AuditLog should show the target of the operation and not just arguments
>
[
https://issues.apache.org/jira/browse/AMQ-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678790#comment-16678790
]
Gary Tully commented on AMQ-7091:
-
[~alanprot] you have to ask the computer to see if there is any negative
[
https://issues.apache.org/jira/browse/AMQ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678090#comment-16678090
]
Gary Tully commented on AMQ-7082:
-
[~alanprot] I added an additional condition the the end of your new test
[
https://issues.apache.org/jira/browse/AMQ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-7082:
-
peeking at the latest additions to the fix.
> KahaDB index, recover free pages in parallel with start
>
[
https://issues.apache.org/jira/browse/AMQ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7082.
-
Resolution: Fixed
Fix is good, thanks [~alanprot]
> KahaDB index, recover free pages in parallel with
[
https://issues.apache.org/jira/browse/AMQ-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676855#comment-16676855
]
Gary Tully commented on AMQ-7091:
-
that info does not need to be persisted, it is duplicate info. I would
[
https://issues.apache.org/jira/browse/AMQ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676576#comment-16676576
]
Gary Tully commented on AMQ-7082:
-
The window is small, however with something like message expiry, and all
[
https://issues.apache.org/jira/browse/AMQ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-7082:
-
[~alanprot] pointed out an issue that can cause the concurrent free page
recovery to walk on newly allocated
[
https://issues.apache.org/jira/browse/AMQ-7085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676375#comment-16676375
]
Gary Tully commented on AMQ-7085:
-
[~sits] even for a small change, it is best to include a test case to
[
https://issues.apache.org/jira/browse/AMQ-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7088.
-
Resolution: Fixed
> mqtt deadlock on creation/removal of destinations (virtual topic)
>
Gary Tully created AMQ-7088:
---
Summary: mqtt deadlock on creation/removal of destinations
(virtual topic)
Key: AMQ-7088
URL: https://issues.apache.org/jira/browse/AMQ-7088
Project: ActiveMQ
Issue
[
https://issues.apache.org/jira/browse/AMQ-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7086.
-
Resolution: Fixed
new kahaDB boolean attribute:
cleanupOnStop - default to true as before.
When
[
https://issues.apache.org/jira/browse/AMQ-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7086:
Summary: KahaDB - optionally perform expensive gc run on shutdown (was:
KahaDB - don't perform expensive gc
[
https://issues.apache.org/jira/browse/AMQ-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663646#comment-16663646
]
Gary Tully commented on AMQ-7086:
-
The checkpoint=0 use case is from: AMQ-3646
disabling gc on shutdown
[
https://issues.apache.org/jira/browse/AMQ-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7086:
Description:
when looking at the speed of broker.stop with kahadb and the scheduler store.
There is a full
[
https://issues.apache.org/jira/browse/AMQ-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7086:
Description:
when looking at the speed of broker.stop with kahadb and the scheduler store.
There is a full
Gary Tully created AMQ-7086:
---
Summary: KahaDB - don't perform expensive gc run on shutdown
Key: AMQ-7086
URL: https://issues.apache.org/jira/browse/AMQ-7086
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662345#comment-16662345
]
Gary Tully commented on AMQ-6690:
-
[~nopius]
that is not good, for some context; there were related
[
https://issues.apache.org/jira/browse/AMQ-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7084.
-
Resolution: Fixed
> Kahadb pagefile, allocated and unused pages from read only transactions are
> leaked
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660787#comment-16660787
]
Gary Tully commented on AMQ-7080:
-
[~alanprot] I opened https://issues.apache.org/jira/browse/AMQ-7084 to
Gary Tully created AMQ-7084:
---
Summary: Kahadb pagefile, allocated and unused pages from read
only transactions are leaked
Key: AMQ-7084
URL: https://issues.apache.org/jira/browse/AMQ-7084
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659158#comment-16659158
]
Gary Tully commented on AMQ-7080:
-
[~alanprot] peek at [^AMQ-7080-freeList-update.diff]
that will sort
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7080:
Attachment: AMQ-7080-freeList-update.diff
> Keep track of free pages - Update db.free file during
[
https://issues.apache.org/jira/browse/AMQ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659033#comment-16659033
]
Gary Tully commented on AMQ-7082:
-
[~cshannon] yep, good catch thanks. it is the lazySet semantic I was
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658770#comment-16658770
]
Gary Tully commented on AMQ-7080:
-
{quote}When we call tx.allocate the pages are not included in the
[
https://issues.apache.org/jira/browse/AMQ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656986#comment-16656986
]
Gary Tully commented on AMQ-7082:
-
I did not want to block normal work with sync on what the recovery
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656919#comment-16656919
]
Gary Tully commented on AMQ-7080:
-
with https://issues.apache.org/jira/browse/AMQ-7082 the need for any
[
https://issues.apache.org/jira/browse/AMQ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7082.
-
Resolution: Fixed
The recovery is now back in the start phase, if it completes we are good.
Otherwise we
[
https://issues.apache.org/jira/browse/AMQ-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully closed AMQ-7081.
---
> After AMQ-7079 abortSlowAckConsumerStrategy aborts connection by default
>
[
https://issues.apache.org/jira/browse/AMQ-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7081.
-
Resolution: Not A Bug
> After AMQ-7079 abortSlowAckConsumerStrategy aborts connection by default
>
Gary Tully created AMQ-7082:
---
Summary: KahaDB index, recover free pages in parallel with start
Key: AMQ-7082
URL: https://issues.apache.org/jira/browse/AMQ-7082
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656669#comment-16656669
]
Gary Tully edited comment on AMQ-7081 at 10/19/18 11:17 AM:
see the attached
[
https://issues.apache.org/jira/browse/AMQ-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656669#comment-16656669
]
Gary Tully commented on AMQ-7081:
-
see the attached test case, leave it running for 30 seconds and note the
[
https://issues.apache.org/jira/browse/AMQ-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7081:
Attachment: AMQ7081Test.java
> After AMQ-7079 abortSlowAckConsumerStrategy aborts connection by default
>
[
https://issues.apache.org/jira/browse/AMQ-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656663#comment-16656663
]
Gary Tully commented on AMQ-7081:
-
This looks ok, maxSlowDuration defaults to 30 seconds, if it is slow for
[
https://issues.apache.org/jira/browse/AMQ-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-7081:
---
Assignee: Gary Tully
> After AMQ-7079 abortSlowAckConsumerStrategy aborts connection by default
>
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656627#comment-16656627
]
Gary Tully commented on AMQ-7080:
-
It is more to verify the read. A partial write will be ok in this case,
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16655866#comment-16655866
]
Gary Tully commented on AMQ-7080:
-
the freelist format is not so lenient.
the writes can be already
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16655819#comment-16655819
]
Gary Tully commented on AMQ-7080:
-
you may be able to do this without any change to the stored metadata
[
https://issues.apache.org/jira/browse/AMQ-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7079.
-
Resolution: Fixed
Assignee: Gary Tully
Fix Version/s: 5.16.0
> Using
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7067.
-
Resolution: Fixed
I think this is now sorted, the ack compaction will still work and not get in
the way.
[
https://issues.apache.org/jira/browse/AMQ-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653873#comment-16653873
]
Gary Tully commented on AMQ-6590:
-
[~cshannon] sure, the recovery penalty needs to be taken at some stage.
[
https://issues.apache.org/jira/browse/AMQ-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653398#comment-16653398
]
Gary Tully edited comment on AMQ-6590 at 10/17/18 11:40 AM:
[~cshannon] I have
[
https://issues.apache.org/jira/browse/AMQ-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653398#comment-16653398
]
Gary Tully commented on AMQ-6590:
-
[~cshannon] I have move this fix to the shutdown phase b/c the recovery
[
https://issues.apache.org/jira/browse/AMQ-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653357#comment-16653357
]
Gary Tully commented on AMQ-6590:
-
The checkpoint won't help, it will not be possible to work with a stale
[
https://issues.apache.org/jira/browse/AMQ-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653349#comment-16653349
]
Gary Tully commented on AMQ-6590:
-
It turns out that this change, while good, means that we take a hit on
[
https://issues.apache.org/jira/browse/AMQ-6421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6421.
-
Resolution: Fixed
Assignee: Gary Tully
Fix Version/s: 5.16.0
>
[
https://issues.apache.org/jira/browse/AMQ-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7077.
-
Resolution: Fixed
[~simmel] with the abort slow ack policy and
_maxTimeSinceLastAck_ you can now control
[
https://issues.apache.org/jira/browse/AMQ-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651788#comment-16651788
]
Gary Tully commented on AMQ-7077:
-
If the abortSlowAck policy is responsible for setting the flag, it can
Gary Tully created AMQ-7077:
---
Summary: Queue subscriber view slowConsumer flag set in error
Key: AMQ-7077
URL: https://issues.apache.org/jira/browse/AMQ-7077
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16647928#comment-16647928
]
Gary Tully commented on AMQ-7067:
-
I pushed an update, that goes some of the way, at least there is one
[
https://issues.apache.org/jira/browse/AMQ-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646958#comment-16646958
]
Gary Tully edited comment on AMQ-7070 at 10/12/18 8:18 AM:
---
my bet is that there
[
https://issues.apache.org/jira/browse/AMQ-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646958#comment-16646958
]
Gary Tully commented on AMQ-7070:
-
my bet is that there is little crossover between tests for priority and
[
https://issues.apache.org/jira/browse/AMQ-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646627#comment-16646627
]
Gary Tully edited comment on AMQ-7070 at 10/11/18 4:56 PM:
---
Hi Gary! Thanks
[
https://issues.apache.org/jira/browse/AMQ-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646627#comment-16646627
]
Gary Tully edited comment on AMQ-7070 at 10/11/18 4:55 PM:
---
Hi Gary! Thanks
[
https://issues.apache.org/jira/browse/ARTEMIS-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646638#comment-16646638
]
Gary Tully commented on ARTEMIS-2103:
-
[~pawelj] thanks for the confirmation :) - it is great to
[
https://issues.apache.org/jira/browse/AMQ-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646215#comment-16646215
]
Gary Tully commented on AMQ-7070:
-
[~alanprot] purging the cache seems the only way, it could be selective,
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643245#comment-16643245
]
Gary Tully commented on AMQ-7067:
-
[~cshannon] We just need the lock for protection, no tx, b/c the index
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-7067:
---
Assignee: Gary Tully
> KahaDB Recovery can experience a dangling transaction when prepare and commit
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643158#comment-16643158
]
Gary Tully edited comment on AMQ-7067 at 10/9/18 11:40 AM:
---
[~cshannon] yes, good
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643158#comment-16643158
]
Gary Tully commented on AMQ-7067:
-
[~cshannon] yes, good catch. I should be under that lock for all of the
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7067:
Description:
KahaDB Recovery can experience a dangling transaction when prepare and commit
occur on
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643123#comment-16643123
]
Gary Tully commented on AMQ-7067:
-
[~jgoodyear] I have pushed your changes and some additional test tidy up
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642151#comment-16642151
]
Gary Tully edited comment on AMQ-7067 at 10/8/18 5:07 PM:
--
I see that losing a
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642151#comment-16642151
]
Gary Tully commented on AMQ-7067:
-
I see that losing a prepare record after an outcome is still
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642107#comment-16642107
]
Gary Tully edited comment on AMQ-7067 at 10/8/18 4:37 PM:
--
In the xa case, I don't
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642107#comment-16642107
]
Gary Tully edited comment on AMQ-7067 at 10/8/18 4:36 PM:
--
In the xa case, I don't
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642107#comment-16642107
]
Gary Tully commented on AMQ-7067:
-
In the xa case, I don't think the prepare record location is tracked, so
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7067:
Summary: KahaDB Recovery can experience a dangling transaction when prepare
and commit occur on different
[
https://issues.apache.org/jira/browse/AMQ-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641757#comment-16641757
]
Gary Tully commented on AMQ-7067:
-
[~jgoodyear] I think the patch is on the right track but I think it
Gary Tully created ARTEMIS-2110:
---
Summary: JDBC LeaseLocker repeated renew or renew after aquire can
fail in error
Key: ARTEMIS-2110
URL: https://issues.apache.org/jira/browse/ARTEMIS-2110
Project:
[
https://issues.apache.org/jira/browse/ARTEMIS-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636893#comment-16636893
]
Gary Tully commented on ARTEMIS-2103:
-
The mapping to queue name needs to take the full openwire
[
https://issues.apache.org/jira/browse/ARTEMIS-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned ARTEMIS-2103:
---
Assignee: Gary Tully
> VirtualTopic doesn't work correctly with multiple consumers
>
[
https://issues.apache.org/jira/browse/ARTEMIS-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635574#comment-16635574
]
Gary Tully commented on ARTEMIS-2103:
-
Why does the second consumer need the same name?
you
[
https://issues.apache.org/jira/browse/AMQ-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7062.
-
Resolution: Fixed
> RedeliverPlugin can loop on duplicate detection sending to dlq
>
Gary Tully created AMQ-7062:
---
Summary: RedeliverPlugin can loop on duplicate detection sending
to dlq
Key: AMQ-7062
URL: https://issues.apache.org/jira/browse/AMQ-7062
Project: ActiveMQ
Issue
[
https://issues.apache.org/jira/browse/AMQ-7057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7057.
-
Resolution: Fixed
> Suppress (optionally) warn logging of EOF or Reset exceptions when remote
> socket
[
https://issues.apache.org/jira/browse/AMQ-7057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16622087#comment-16622087
]
Gary Tully commented on AMQ-7057:
-
I am defaulting to true to retain the stomp behaviour of not reporting,
Gary Tully created AMQ-7057:
---
Summary: Suppress (optionally) warn logging of EOF or Reset
exceptions when remote socket is closed
Key: AMQ-7057
URL: https://issues.apache.org/jira/browse/AMQ-7057
Project:
[
https://issues.apache.org/jira/browse/AMQ-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7055.
-
Resolution: Fixed
Assignee: Gary Tully
Fix Version/s: 5.16.0
[~alanprot] thanks for the
[
https://issues.apache.org/jira/browse/AMQ-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7056.
-
Resolution: Fixed
Assignee: Gary Tully
Fix Version/s: 5.16.0
> Fix AMQ3625Test and
[
https://issues.apache.org/jira/browse/AMQ-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620375#comment-16620375
]
Gary Tully commented on AMQ-7028:
-
I pulled the mkahadb fix.
on the xa scenario, AMQ-6707 has ~8 commits,
[
https://issues.apache.org/jira/browse/AMQ-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7052.
-
Resolution: Fixed
Fix Version/s: (was: 5.x)
5.16.0
[~alanprot] Thanks for
[
https://issues.apache.org/jira/browse/AMQ-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-7052:
---
Assignee: Gary Tully
> Fix tests related to purgeRecoveredXATransactions property on the KahaDB
>
[
https://issues.apache.org/jira/browse/AMQ-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16608875#comment-16608875
]
Gary Tully commented on AMQ-7028:
-
The first thing to figure is if the tests work ok on their own. Some
[
https://issues.apache.org/jira/browse/AMQ-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593766#comment-16593766
]
Gary Tully commented on AMQ-7041:
-
Maybe check what are the default performance options. the store expects
[
https://issues.apache.org/jira/browse/AMQ-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590433#comment-16590433
]
Gary Tully commented on AMQ-7041:
-
I have seen this happen and it seems it is the gluster
[
https://issues.apache.org/jira/browse/AMQ-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7037.
-
Resolution: Fixed
{code:java}
{code}
> Add sslContext attribute to networkConnector to override
Gary Tully created AMQ-7037:
---
Summary: Add sslContext attribute to networkConnector to override
broker sslContext
Key: AMQ-7037
URL: https://issues.apache.org/jira/browse/AMQ-7037
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5917.
-
Resolution: Fixed
Fix Version/s: 5.16.0
[
https://issues.apache.org/jira/browse/AMQ-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-5917:
Comment: was deleted
(was: more generally - we want to be able to specify the sslContext per
[
https://issues.apache.org/jira/browse/AMQ-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-5917:
---
Assignee: Gary Tully
> networkConnectorStartAsync="true" results in "WARN | Could not connect to
>
[
https://issues.apache.org/jira/browse/AMQ-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583937#comment-16583937
]
Gary Tully edited comment on AMQ-3003 at 8/17/18 1:24 PM:
--
note: the audit should
[
https://issues.apache.org/jira/browse/AMQ-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583937#comment-16583937
]
Gary Tully commented on AMQ-3003:
-
The audit should be disabled; *enableAudit=false* when
[
https://issues.apache.org/jira/browse/AMQ-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7035.
-
Resolution: Fixed
> Memory usage incorrectly increases when selectors are used in JMX operations
>
701 - 800 of 1463 matches
Mail list logo
