[
https://issues.apache.org/jira/browse/ARTEMIS-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107108#comment-16107108
]
Gary Tully commented on ARTEMIS-1310:
-
this feature requires PROTON-1525 b/c SASL GSSAPI requires
[
https://issues.apache.org/jira/browse/ARTEMIS-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107100#comment-16107100
]
Gary Tully commented on ARTEMIS-1310:
-
ARTEMIS-1264 provides for kerberos single sign on over an
Gary Tully created ARTEMIS-1310:
---
Summary: Provide GSSAPI (kerberos) SASL mechanism for AMQP
Key: ARTEMIS-1310
URL: https://issues.apache.org/jira/browse/ARTEMIS-1310
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/AMQ-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6778.
-
Resolution: Fixed
> Advisories are dropped till broker is fully started in error
>
Gary Tully created AMQ-6778:
---
Summary: Advisories are dropped till broker is fully started in
error
Key: AMQ-6778
URL: https://issues.apache.org/jira/browse/AMQ-6778
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6771.
-
Resolution: Fixed
> Improve performance of KahaDB recovery check checkForCorruptJournalFiles=true
>
[
https://issues.apache.org/jira/browse/AMQ-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089937#comment-16089937
]
Gary Tully commented on AMQ-6772:
-
it won't work at all via the runtimeConfigurationPlugin, you will need a
[
https://issues.apache.org/jira/browse/AMQ-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089842#comment-16089842
]
Gary Tully commented on AMQ-6771:
-
[~cshannon] I don't have great numbers from my local testing b/c I am on
[
https://issues.apache.org/jira/browse/AMQ-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089692#comment-16089692
]
Gary Tully commented on AMQ-4693:
-
[~nannou9] thanks for the reply :-)
> Add kerberos [SASL]
[
https://issues.apache.org/jira/browse/AMQ-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089683#comment-16089683
]
Gary Tully commented on AMQ-6772:
-
use a wildcard policy to enable prioritySupport for all queues and
[
https://issues.apache.org/jira/browse/AMQ-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089592#comment-16089592
]
Gary Tully commented on AMQ-6772:
-
the priority support is not a good candidate for runtime modification
Gary Tully created AMQ-6771:
---
Summary: Improve performance of KahaDB recovery check
checkForCorruptJournalFiles=true
Key: AMQ-6771
URL: https://issues.apache.org/jira/browse/AMQ-6771
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/ARTEMIS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-1264:
Description:
Allow a client authenticated with a kerberos credential to authenticate to the
[
https://issues.apache.org/jira/browse/AMQ-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085525#comment-16085525
]
Gary Tully commented on AMQ-4693:
-
[~nannou9] I was inspired by ur PR to implement same in artemis -
[
https://issues.apache.org/jira/browse/ARTEMIS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-1264:
Comment: was deleted
(was: next steps:
- -ensure mapping from kerberos principal to broker
[
https://issues.apache.org/jira/browse/ARTEMIS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-1264:
Description:
Allow a client authenticated with a kerberos credential to authenticate to the
[
https://issues.apache.org/jira/browse/ARTEMIS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074589#comment-16074589
]
Gary Tully edited comment on ARTEMIS-1264 at 7/13/17 10:22 AM:
---
next
[
https://issues.apache.org/jira/browse/AMQ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6764.
-
Resolution: Fixed
> Add ended statement to Audit log for JMX ops
>
[
https://issues.apache.org/jira/browse/AMQ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6764:
Description:
AMQ-3100 introduced an audit log. It is boolean enabled or disabled.
This enhancement allows
[
https://issues.apache.org/jira/browse/AMQ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6764:
Description:
AMQ-3100 introduced an audit log. It is boolean enabled or disabled.
This enhancement allows
[
https://issues.apache.org/jira/browse/ARTEMIS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074589#comment-16074589
]
Gary Tully edited comment on ARTEMIS-1264 at 7/6/17 4:05 PM:
-
next steps:
-
[
https://issues.apache.org/jira/browse/ARTEMIS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074589#comment-16074589
]
Gary Tully edited comment on ARTEMIS-1264 at 7/5/17 12:38 PM:
--
next steps:
[
https://issues.apache.org/jira/browse/ARTEMIS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074589#comment-16074589
]
Gary Tully commented on ARTEMIS-1264:
-
next steps:
- ensure jms client config is trivial
-
Gary Tully created ARTEMIS-1264:
---
Summary: Client authentication via Kerberos TLS Cipher Suites (RFC
2712)
Key: ARTEMIS-1264
URL: https://issues.apache.org/jira/browse/ARTEMIS-1264
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050747#comment-16050747
]
Gary Tully commented on AMQ-6625:
-
The DefaultIOExceptionHandler implements a resume call on kahadb that
[
https://issues.apache.org/jira/browse/AMQ-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907515#comment-15907515
]
Gary Tully edited comment on AMQ-6625 at 6/15/17 4:38 PM:
--
Prior to the
[
https://issues.apache.org/jira/browse/AMQ-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6625.
-
Resolution: Fixed
> IOException in kahaDB needs to pause pending IOExceptionHandler intervention
>
[
https://issues.apache.org/jira/browse/AMQ-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-6625:
-
The KahaDbIOExceptionHandler clashes with the use of the
LeaseLockerIOExceptionHandler - need to push the
[
https://issues.apache.org/jira/browse/AMQ-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6703.
-
Resolution: Fixed
> JMX purge needs to clear the message audit
> --
Gary Tully created AMQ-6703:
---
Summary: JMX purge needs to clear the message audit
Key: AMQ-6703
URL: https://issues.apache.org/jira/browse/AMQ-6703
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049094#comment-16049094
]
Gary Tully commented on AMQ-6701:
-
there is noting odd in there. it could be gc: see
[
https://issues.apache.org/jira/browse/AMQ-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6702.
-
Resolution: Fixed
The dead letter strategy has an message audit that is enabled by default. This
prevents
Gary Tully created AMQ-6702:
---
Summary: Allow dead letter strategy audit configuration
Key: AMQ-6702
URL: https://issues.apache.org/jira/browse/AMQ-6702
Project: ActiveMQ
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/AMQ-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047758#comment-16047758
]
Gary Tully commented on AMQ-6701:
-
post a series of thread dumps during the high cpu period, that will tell
[
https://issues.apache.org/jira/browse/AMQ-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16040724#comment-16040724
]
Gary Tully commented on AMQ-6683:
-
Any chance you can replicate the usage pattern in some test code or maybe
[
https://issues.apache.org/jira/browse/AMQ-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034856#comment-16034856
]
Gary Tully commented on AMQ-6695:
-
I agree - the mirror should get a copy - and I think it should differ by
[
https://issues.apache.org/jira/browse/AMQ-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034562#comment-16034562
]
Gary Tully commented on AMQ-6695:
-
guess the copy option could be deprecated in the same way as in
[
https://issues.apache.org/jira/browse/AMQ-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034558#comment-16034558
]
Gary Tully commented on AMQ-6695:
-
btw: this copy not needed has been addressed in
[
https://issues.apache.org/jira/browse/AMQ-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6696.
-
Resolution: Fixed
> Memory Usage for composite destination increasing when concurrentSend is used
>
Gary Tully created AMQ-6696:
---
Summary: Memory Usage for composite destination increasing when
concurrentSend is used
Key: AMQ-6696
URL: https://issues.apache.org/jira/browse/AMQ-6696
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6696:
Description:
After message has been forwarded to the underlying queues MemoryUsageByteCount
is increasing
[
https://issues.apache.org/jira/browse/AMQ-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034386#comment-16034386
]
Gary Tully commented on AMQ-6695:
-
thanks for the patch.
Changes like this can be tricky (as in it will
[
https://issues.apache.org/jira/browse/AMQ-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6693.
-
Resolution: Fixed
> SQLException when concurrently moving messages to DLQ
>
Gary Tully created AMQ-6693:
---
Summary: SQLException when concurrently moving messages to DLQ
Key: AMQ-6693
URL: https://issues.apache.org/jira/browse/AMQ-6693
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6691.
-
Resolution: Fixed
Assignee: Gary Tully
Test that validates persistence of the dlq flag via the
Gary Tully created AMQ-6691:
---
Summary: JMX - allow DLQ flag to be modified
Key: AMQ-6691
URL: https://issues.apache.org/jira/browse/AMQ-6691
Project: ActiveMQ
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/AMQ-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6690.
-
Resolution: Fixed
I considered throwing an exception but I think it is safer to retain the
existing
Gary Tully created AMQ-6690:
---
Summary: Protect against JMX move/copy operations onto self
Key: AMQ-6690
URL: https://issues.apache.org/jira/browse/AMQ-6690
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6688.
-
Resolution: Fixed
> org.apache.activemq.broker.region.Queue.doMessageSend() future not completing
>
[
https://issues.apache.org/jira/browse/AMQ-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6687.
-
Resolution: Fixed
> destination memory usage incorrect after flow control (PFC) sendTimeout and
> rollback
[
https://issues.apache.org/jira/browse/AMQ-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024737#comment-16024737
]
Gary Tully commented on AMQ-6687:
-
With transactions or concurrentStoreAndDispatch - memory is accounted for
[
https://issues.apache.org/jira/browse/AMQ-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024609#comment-16024609
]
Gary Tully commented on AMQ-4467:
-
With transactions or concurrentStoreAndDispatch - memory is accounted for
[
https://issues.apache.org/jira/browse/AMQ-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024568#comment-16024568
]
Gary Tully commented on AMQ-6687:
-
AMQ-4467 needed a revisit b/c that change prevented pfc from kicking in
Gary Tully created AMQ-6687:
---
Summary: destination memory usage incorrect after flow control
(PFC) sendTimeout and rollback
Key: AMQ-6687
URL: https://issues.apache.org/jira/browse/AMQ-6687
Project:
[
https://issues.apache.org/jira/browse/AMQ-6684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6684.
-
Resolution: Fixed
Assignee: Gary Tully
resolved via exclusions in the pom.
> org.json is cat-x -
[
https://issues.apache.org/jira/browse/AMQ-6684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6684:
Description:
org.json is cat-x and cannot be included as a compile dependency going forward.
Gary Tully created AMQ-6684:
---
Summary: org.json is cat-x - needs to be removed
Key: AMQ-6684
URL: https://issues.apache.org/jira/browse/AMQ-6684
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6678.
-
Resolution: Fixed
fix and test added.
> Move/Retry (destructive) Queue JMX operations need synchronization
Gary Tully created AMQ-6678:
---
Summary: Move/Retry (destructive) Queue JMX operations need
synchronization
Key: AMQ-6678
URL: https://issues.apache.org/jira/browse/AMQ-6678
Project: ActiveMQ
Issue
[
https://issues.apache.org/jira/browse/AMQ-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002772#comment-16002772
]
Gary Tully edited comment on AMQ-6671 at 5/9/17 2:28 PM:
-
[~anujkhandelwal90] it may
[
https://issues.apache.org/jira/browse/AMQ-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002772#comment-16002772
]
Gary Tully commented on AMQ-6671:
-
[~anujkhandelwal90] it may be that the cleanup task needs to run a few
[
https://issues.apache.org/jira/browse/AMQ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6670.
-
Resolution: Fixed
> KahaDB - Inconsistent error handling on corrupt journal reads
>
Gary Tully created AMQ-6670:
---
Summary: KahaDB - Inconsistent error handling on corrupt journal
reads
Key: AMQ-6670
URL: https://issues.apache.org/jira/browse/AMQ-6670
Project: ActiveMQ
Issue
[
https://issues.apache.org/jira/browse/AMQ-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6068:
Fix Version/s: 5.15.0
> RAR - cannot reset clientId on pooled managed connection
>
[
https://issues.apache.org/jira/browse/AMQ-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996446#comment-15996446
]
Gary Tully commented on AMQ-6068:
-
thanks for the feedback. It may make sense to have this full cleanup
[
https://issues.apache.org/jira/browse/AMQ-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15994642#comment-15994642
]
Gary Tully commented on AMQ-6667:
-
increasing the audit capacity; policyEntry maxProducersToAudit=200
Gary Tully created AMQ-6667:
---
Summary: Many instances of "duplicate message ... from cursor"
redirecting to dlq
Key: AMQ-6667
URL: https://issues.apache.org/jira/browse/AMQ-6667
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6665.
-
Resolution: Fixed
issue was nio+ssl transport not extending SslTtransport but since AMQ-6339 the
relevant
Gary Tully created AMQ-6665:
---
Summary: certificate-based authentication on network bridge fails
for nio+ssl protocol
Key: AMQ-6665
URL: https://issues.apache.org/jira/browse/AMQ-6665
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963599#comment-15963599
]
Gary Tully commented on AMQ-6654:
-
this may be resolved via AMQ-6652
> Durable subscriber pendingQueueSize
Gary Tully created AMQ-6652:
---
Summary: KahaDB checkpoint index page flush skips metadata page
Key: AMQ-6652
URL: https://issues.apache.org/jira/browse/AMQ-6652
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6646.
-
Resolution: Fixed
> default blob strategy error reporting should include url
>
Gary Tully created AMQ-6646:
---
Summary: default blob strategy error reporting should include url
Key: AMQ-6646
URL: https://issues.apache.org/jira/browse/AMQ-6646
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955269#comment-15955269
]
Gary Tully commented on AMQ-5558:
-
refinement
[
https://issues.apache.org/jira/browse/AMQ-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6645.
-
Resolution: Fixed
Gary Tully created AMQ-6645:
---
Summary: activemq:browse command does not display Header -
OriginalDestination
Key: AMQ-6645
URL: https://issues.apache.org/jira/browse/AMQ-6645
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955123#comment-15955123
]
Gary Tully commented on AMQ-6494:
-
reverted
[
https://issues.apache.org/jira/browse/AMQ-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6644.
-
Resolution: Fixed
> Incorrect logging from KahaDB cleanup task when enableAckCompaction=true
>
Gary Tully created AMQ-6644:
---
Summary: Incorrect logging from KahaDB cleanup task when
enableAckCompaction=true
Key: AMQ-6644
URL: https://issues.apache.org/jira/browse/AMQ-6644
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6643.
-
Resolution: Fixed
> Shared virtual topic wildcard consumers receive spurious and duplicate
> messages
>
[
https://issues.apache.org/jira/browse/AMQ-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954873#comment-15954873
]
Gary Tully commented on AMQ-6643:
-
The restrictions introduced in
Gary Tully created AMQ-6643:
---
Summary: Shared virtual topic wildcard consumers receive spurious
and duplicate messages
Key: AMQ-6643
URL: https://issues.apache.org/jira/browse/AMQ-6643
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1594#comment-1594
]
Gary Tully commented on AMQ-6640:
-
network connector options suppressDuplicate[Queue|Topic]Subscriptions
[
https://issues.apache.org/jira/browse/AMQ-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6640.
-
Resolution: Fixed
network connector internal vm transports are a all sync with the exception of
the duplex
[
https://issues.apache.org/jira/browse/AMQ-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-6640:
-
it is still not exactly right - need to rationalise the use of sync and async
vm transports on either end of
[
https://issues.apache.org/jira/browse/AMQ-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6640.
-
Resolution: Fixed
> network of brokers, duplex connector, network consumers not registered on
>
[
https://issues.apache.org/jira/browse/AMQ-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945214#comment-15945214
]
Gary Tully commented on AMQ-6640:
-
AMQ-4328 fix needed to be confined to the async side, the duplex
Gary Tully created AMQ-6640:
---
Summary: network of brokers, duplex connector, network consumers
not registered on destination - hung bridge
Key: AMQ-6640
URL: https://issues.apache.org/jira/browse/AMQ-6640
[
https://issues.apache.org/jira/browse/AMQ-6628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6628.
-
Resolution: Fixed
Fix Version/s: 5.15.0
update applied, thanks for the contribution.
> [doc] Add
[
https://issues.apache.org/jira/browse/AMQ-6628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6628:
---
Assignee: Gary Tully
> [doc] Add details on message groups dispatch delay
>
[
https://issues.apache.org/jira/browse/AMQ-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6625.
-
Resolution: Fixed
Prior to the handIOException up-call the journal and index pause. The appender
write
[
https://issues.apache.org/jira/browse/AMQ-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907486#comment-15907486
]
Gary Tully commented on AMQ-6625:
-
If the broker needs to stay up, for sync traffic AMQ-6606 helps ensure
[
https://issues.apache.org/jira/browse/AMQ-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907474#comment-15907474
]
Gary Tully commented on AMQ-6625:
-
AMQ-3725 feature is better suited to the jdbc store which is internally
Gary Tully created AMQ-6625:
---
Summary: IOException in kahaDB needs to pause pending
IOExceptionHandler intervention
Key: AMQ-6625
URL: https://issues.apache.org/jira/browse/AMQ-6625
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6606.
-
Resolution: Fixed
the fix is refined to just sync batches such that index updates from async
writes do not
[
https://issues.apache.org/jira/browse/AMQ-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897168#comment-15897168
]
Gary Tully edited comment on AMQ-6606 at 3/7/17 12:32 PM:
--
This needs more work..
[
https://issues.apache.org/jira/browse/AMQ-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-6606:
-
This needs more work.. readjustment of offset needs to percolate into all
queued writes... some more thought
[
https://issues.apache.org/jira/browse/AMQ-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894591#comment-15894591
]
Gary Tully commented on AMQ-6377:
-
[~cshannon] noticed the use of String for
[
https://issues.apache.org/jira/browse/AMQ-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3233.
-
Resolution: Fixed
Fix Version/s: (was: NEEDS_REVIEW)
5.15.0
strange that this
[
https://issues.apache.org/jira/browse/AMQ-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-3233:
---
Assignee: Gary Tully
> warnOnProducerFlowControl is never reset to 'true' after the first INFO
>
1001 - 1100 of 1472 matches
Mail list logo
