[
https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230472#comment-15230472
]
Gary Tully commented on AMQ-6142:
-
[~cshannon] I think rolling back the sync is best, then thinking of
[
https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230280#comment-15230280
]
Gary Tully commented on AMQ-6142:
-
there is some more context in
[
https://issues.apache.org/jira/browse/AMQ-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6151.
-
Resolution: Fixed
Fix Version/s: (was: 5.13.1)
> Redelivered messages bypass priority ordering
>
[
https://issues.apache.org/jira/browse/AMQ-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-6151:
-
Within a priority, dispatch order after prefetch needs to be retained.
Having a single merged list breaks this.
[
https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6142:
Attachment: amq-6142.diff
amq-6142.diff - file attach. Show the problem with message.copy that seems to
be
[
https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228135#comment-15228135
]
Gary Tully commented on AMQ-6142:
-
[~cshannon] sorry for the late input. I was peeking at this change and
[
https://issues.apache.org/jira/browse/AMQ-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221792#comment-15221792
]
Gary Tully commented on AMQ-6133:
-
[~cshannon]
I like that, isPersistJMSRedelivered is likely selectively
[
https://issues.apache.org/jira/browse/AMQ-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221713#comment-15221713
]
Gary Tully commented on AMQ-6133:
-
hmm. I think concurrentStoreAndDispatchQueues is not compatible with
Gary Tully created AMQ-6215:
---
Summary: priority message dispatch can be affected by jms browser
or expiry processing paging messages in error
Key: AMQ-6215
URL: https://issues.apache.org/jira/browse/AMQ-6215
[
https://issues.apache.org/jira/browse/AMQ-6208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6208.
-
Resolution: Fixed
> The connector's jmx attribute UpdateClusterClients is not correct
>
[
https://issues.apache.org/jira/browse/AMQ-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6206.
-
Resolution: Fixed
> properties in stomp non persistent messages are not reflected in the message
> size
[
https://issues.apache.org/jira/browse/AMQ-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6206:
Summary: properties in stomp non persistent messages are not reflected in
the message size used for usage
[
https://issues.apache.org/jira/browse/AMQ-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6199.
-
Resolution: Fixed
> cursorMemoryHighWaterMark configuration not applied to topic subscription
>
[
https://issues.apache.org/jira/browse/AMQ-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6199:
Summary: cursorMemoryHighWaterMark configuration not applied to topic
subscription (was:
Gary Tully created AMQ-6199:
---
Summary: ursorMemoryHighWaterMark configuration not applied to
topic subscription
Key: AMQ-6199
URL: https://issues.apache.org/jira/browse/AMQ-6199
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185105#comment-15185105
]
Gary Tully commented on AMQ-5785:
-
it looks like the onUsageChanged of the filecursor needs to remove
[
https://issues.apache.org/jira/browse/AMQ-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4495.
-
Resolution: Fixed
On review - i have retained the status quo. The performance implications of
going to the
[
https://issues.apache.org/jira/browse/AMQ-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183267#comment-15183267
]
Gary Tully commented on AMQ-4495:
-
I have not found a straight forward way to deal with performance issue so
[
https://issues.apache.org/jira/browse/AMQ-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15182900#comment-15182900
]
Gary Tully commented on AMQ-6194:
-
[~cshannon] thanks for the heads up!
The intent is to match
[
https://issues.apache.org/jira/browse/AMQ-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175454#comment-15175454
]
Gary Tully commented on AMQ-5773:
-
I think this is resolved by
[
https://issues.apache.org/jira/browse/AMQ-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173781#comment-15173781
]
Gary Tully commented on AMQ-4495:
-
The second use case here is starvation, simplest when there is a shared
[
https://issues.apache.org/jira/browse/AMQ-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15173767#comment-15173767
]
Gary Tully commented on AMQ-4495:
-
[~cshannon] yes to both.
It was oom that brought me back, then i saw the
[
https://issues.apache.org/jira/browse/AMQ-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-4495:
-
Assignee: Gary Tully (was: Dejan Bosanac)
Regression: Regression
There is a problem with this
[
https://issues.apache.org/jira/browse/AMQ-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6171.
-
Resolution: Fixed
> legal colon in broker name breaks vm transport
>
Gary Tully created AMQ-6171:
---
Summary: legal colon in broker name breaks vm transport
Key: AMQ-6171
URL: https://issues.apache.org/jira/browse/AMQ-6171
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-6148:
-
looks like we could pull back the fix from artemis for this. I don't see any
reason why we cannot cache the
Gary Tully created AMQ-6164:
---
Summary: queue sendLock prevents concurrent journal updates
Key: AMQ-6164
URL: https://issues.apache.org/jira/browse/AMQ-6164
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6164.
-
Resolution: Fixed
multiple producers on a single destination can now get the benefit of write
batching to
[
https://issues.apache.org/jira/browse/AMQ-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137116#comment-15137116
]
Gary Tully commented on AMQ-6153:
-
this may be a case where using a 0 or -1 value works. Both are illegal
[
https://issues.apache.org/jira/browse/AMQ-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6151.
-
Resolution: Fixed
newly paged in and pending messages are merged prior to dispatch when
prioritizedMessage
[
https://issues.apache.org/jira/browse/AMQ-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117148#comment-15117148
]
Gary Tully commented on AMQ-6134:
-
fyi https://issues.apache.org/jira/browse/AMQ-6084 in 5.13.1 may also be
Gary Tully created AMQ-6137:
---
Summary: Special escape characters in LIKE selectors do not work
as expected
Key: AMQ-6137
URL: https://issues.apache.org/jira/browse/AMQ-6137
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6137.
-
Resolution: Fixed
additional tests for using _ and % as escape characters in like expressions. A
little
[
https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112621#comment-15112621
]
Gary Tully commented on ARTEMIS-355:
for reference - the original activemq use case -
Gary Tully created ARTEMIS-356:
--
Summary: Special escape characters in LIKE selectors do not work
as expected
Key: ARTEMIS-356
URL: https://issues.apache.org/jira/browse/ARTEMIS-356
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110438#comment-15110438
]
Gary Tully commented on AMQ-6134:
-
please attach your xml config.
the broker should exit. the
[
https://issues.apache.org/jira/browse/AMQ-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15108652#comment-15108652
]
Gary Tully commented on AMQ-6133:
-
It should add the message if it cannot be found. It is expected that the
Gary Tully created AMQ-6128:
---
Summary: browsing priority queue can return messages in different
order than they will be consumed
Key: AMQ-6128
URL: https://issues.apache.org/jira/browse/AMQ-6128
Project:
Gary Tully created AMQ-6124:
---
Summary: failover backup transports options do not update the
brokerInfo stale org.apache.activemq.ActiveMQConnection#getBrokerName
Key: AMQ-6124
URL:
[
https://issues.apache.org/jira/browse/AMQ-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6124:
---
Assignee: Gary Tully
> failover backup transports do not update the brokerInfo leaving stale
>
[
https://issues.apache.org/jira/browse/AMQ-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6124:
Summary: failover backup transports options do not update the brokerInfo
leaving stale
[
https://issues.apache.org/jira/browse/AMQ-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6124:
Summary: failover backup transports do not update the brokerInfo leaving
stale
[
https://issues.apache.org/jira/browse/AMQ-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6124.
-
Resolution: Fixed
> failover backup transports do not update the brokerInfo leaving stale
>
[
https://issues.apache.org/jira/browse/AMQ-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6089:
---
Assignee: Gary Tully
> org.apache.activemq.TransactionContext.recover(int flag) should return null
>
[
https://issues.apache.org/jira/browse/AMQ-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085471#comment-15085471
]
Gary Tully commented on AMQ-6089:
-
I agree, I had a read of
[
https://issues.apache.org/jira/browse/AMQ-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6089.
-
Resolution: Fixed
Fix Version/s: 5.14.0
thanks for the test. I merged in the looping code from your
[
https://issues.apache.org/jira/browse/AMQ-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085501#comment-15085501
]
Gary Tully commented on AMQ-6089:
-
peeking at the patch, not sure there is any value in the round trip to
[
https://issues.apache.org/jira/browse/AMQ-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6094.
-
Resolution: Fixed
Fix Version/s: 5.14.0
Regression: Regression
[~cshannon] thanks for the
[
https://issues.apache.org/jira/browse/AMQ-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6094:
---
Assignee: Gary Tully
> Memory Leak with abnormal disconnecting consumers
>
[
https://issues.apache.org/jira/browse/AMQ-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057916#comment-15057916
]
Gary Tully commented on AMQ-6089:
-
the transaction context does not maintain any state at the moment. I can
[
https://issues.apache.org/jira/browse/AMQ-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056268#comment-15056268
]
Gary Tully commented on AMQ-6086:
-
having some sort of stack of started components is needed here. Pushing
[
https://issues.apache.org/jira/browse/AMQ-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6086:
---
Assignee: Gary Tully
> Broker stop and start are not at all thread safe - we can do better
>
Gary Tully created AMQ-6086:
---
Summary: Broker stop and start are not at all thread safe - we can
do better
Key: AMQ-6086
URL: https://issues.apache.org/jira/browse/AMQ-6086
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6005:
---
Assignee: Gary Tully
> Slave broker startup corrupts shared PList storage
>
[
https://issues.apache.org/jira/browse/AMQ-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6005.
-
Resolution: Fixed
Fix Version/s: 5.14.0
clearing out temp store is deferred till temp store start
[
https://issues.apache.org/jira/browse/AMQ-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6083.
-
Resolution: Fixed
> Broker starts on corrupted kahadb despite checkForCorruptJournalFiles="true"
> and
Gary Tully created AMQ-6083:
---
Summary: Broker starts on corrupted kahadb despite
checkForCorruptJournalFiles="true" and ignoreMissingJournalfiles="false"
Key: AMQ-6083
URL:
Gary Tully created AMQ-6084:
---
Summary: Have an option to error out if a limit is exceeded
Key: AMQ-6084
URL: https://issues.apache.org/jira/browse/AMQ-6084
Project: ActiveMQ
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/AMQ-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15048803#comment-15048803
]
Gary Tully commented on AMQ-6084:
-
thanks for the feedback. The jvm heap limits are also adjusted -
[
https://issues.apache.org/jira/browse/AMQ-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5454.
-
Resolution: Fixed
Assignee: Gary Tully
Fix Version/s: (was: NEEDS_REVIEW)
[
https://issues.apache.org/jira/browse/AMQ-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046762#comment-15046762
]
Gary Tully commented on AMQ-5454:
-
do you have a stack trace with a npe from the log or a test case?
As part
[
https://issues.apache.org/jira/browse/AMQ-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046777#comment-15046777
]
Gary Tully commented on AMQ-5486:
-
that looks like a sensible enhancement. my only comment would be the
[
https://issues.apache.org/jira/browse/AMQ-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6071.
-
Resolution: Fixed
Fix Version/s: 5.14.0
thanks for the patch :-)
> Log info about corrupted journal
[
https://issues.apache.org/jira/browse/AMQ-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6071:
---
Assignee: Gary Tully
> Log info about corrupted journal records at WARN level
>
Gary Tully created AMQ-6070:
---
Summary: originalDestination property of advisory messages set to
message id in error
Key: AMQ-6070
URL: https://issues.apache.org/jira/browse/AMQ-6070
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6070.
-
Resolution: Fixed
> originalDestination property of advisory messages set to message id in error
>
[
https://issues.apache.org/jira/browse/AMQ-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6070:
Priority: Minor (was: Major)
> originalDestination property of advisory messages set to message id in error
[
https://issues.apache.org/jira/browse/AMQ-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6068.
-
Resolution: Fixed
> RAR - cannot reset clientId on pooled managed connection
>
Gary Tully created AMQ-6068:
---
Summary: RAR - cannot reset clientId on pooled managed connection
Key: AMQ-6068
URL: https://issues.apache.org/jira/browse/AMQ-6068
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15032054#comment-15032054
]
Gary Tully commented on AMQ-6067:
-
ideally we would be able to have a store cursor that would walk the
[
https://issues.apache.org/jira/browse/AMQ-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15032071#comment-15032071
]
Gary Tully commented on AMQ-6067:
-
the follow up to https://issues.apache.org/jira/browse/AMQ-3362
[
https://issues.apache.org/jira/browse/AMQ-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15029848#comment-15029848
]
Gary Tully commented on AMQ-2191:
-
rework of this issue to make interruption of an inprogress request an
Gary Tully created AMQ-6065:
---
Summary: Allow selective use of broker systemExitOnShutdown from
DefaultIOExceptionHandler
Key: AMQ-6065
URL: https://issues.apache.org/jira/browse/AMQ-6065
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6065.
-
Resolution: Fixed
> Allow selective use of broker systemExitOnShutdown from
> DefaultIOExceptionHandler
>
[
https://issues.apache.org/jira/browse/AMQ-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2191.
-
Resolution: Fixed
Fix Version/s: (was: 5.4.0)
(was: 5.3.1)
[
https://issues.apache.org/jira/browse/AMQ-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15029856#comment-15029856
]
Gary Tully commented on AMQ-3547:
-
As part of the reqworked fix for
[
https://issues.apache.org/jira/browse/AMQ-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-3547:
Fix Version/s: 5.13.0
> Calling Connection.close() on interrupted thread generates
> InterruptedIOException
[
https://issues.apache.org/jira/browse/AMQ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15029905#comment-15029905
]
Gary Tully commented on AMQ-5461:
-
trace level logging for :
[
https://issues.apache.org/jira/browse/AMQ-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026617#comment-15026617
]
Gary Tully commented on AMQ-6061:
-
plugins is an element that must be set via a property using a single bean
[
https://issues.apache.org/jira/browse/AMQ-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022037#comment-15022037
]
Gary Tully commented on AMQ-6014:
-
[~cshannon] thanks for the heads up. that test was in a browser tab on
[
https://issues.apache.org/jira/browse/AMQ-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15013420#comment-15013420
]
Gary Tully commented on AMQ-6053:
-
I suspect this is a resolved by
[
https://issues.apache.org/jira/browse/AMQ-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15011279#comment-15011279
]
Gary Tully commented on AMQ-6050:
-
[~cshannon] that looks perfect to me :-)
> Recreated durable after
[
https://issues.apache.org/jira/browse/AMQ-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-2191:
-
Assignee: Gary Tully (was: Rob Davies)
I have come across a similar issue, different TM but that is
[
https://issues.apache.org/jira/browse/AMQ-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-4645:
Summary: The lease-database-locker does not work properly if slave broker
system clock is behind Database
[
https://issues.apache.org/jira/browse/AMQ-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6033.
-
Resolution: Fixed
> mkahaDB,shared-file-locker - broker not shutting down when it loses the lock
>
[
https://issues.apache.org/jira/browse/AMQ-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969255#comment-14969255
]
Gary Tully commented on AMQ-4361:
-
[~shendley] thanks, sorted that IllegalMonitorStateException
> Deadlock
Gary Tully created AMQ-6014:
---
Summary: Offline Durable Topic Subscription exceeds memory limits
Key: AMQ-6014
URL: https://issues.apache.org/jira/browse/AMQ-6014
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6014.
-
Resolution: Fixed
ref count was off, causing an ack on one sub to decrement usage shared across
other
[
https://issues.apache.org/jira/browse/AMQ-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5933.
-
Resolution: Fixed
all done.
> NullPointerException in SelectorAwareVirtualTopicInterceptor
>
[
https://issues.apache.org/jira/browse/AMQ-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944885#comment-14944885
]
Gary Tully commented on AMQ-6000:
-
To sort this, I think there should be a call to wakeup() in
[
https://issues.apache.org/jira/browse/AMQ-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5994.
-
Resolution: Fixed
Fix Version/s: 5.13.0
[~cshannon] thanks for the test!
> Broker can't recover
[
https://issues.apache.org/jira/browse/AMQ-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-5994:
---
Assignee: Gary Tully
> Broker can't recover Durable Subscription on index deletion
>
[
https://issues.apache.org/jira/browse/AMQ-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939991#comment-14939991
]
Gary Tully commented on AMQ-5994:
-
[~cshannon] thanks for the heads up. That does look like a problem. I
[
https://issues.apache.org/jira/browse/AMQ-5854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14936683#comment-14936683
]
Gary Tully commented on AMQ-5854:
-
good to know. thank for the verification
> Duplicate messages when
[
https://issues.apache.org/jira/browse/AMQ-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14936704#comment-14936704
]
Gary Tully commented on AMQ-5961:
-
I think the pull request looks fine and I see your point about liveness.
[
https://issues.apache.org/jira/browse/AMQ-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933473#comment-14933473
]
Gary Tully commented on AMQ-5961:
-
peeking at the thread dump the root cause is: {code}at
[
https://issues.apache.org/jira/browse/AMQ-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933473#comment-14933473
]
Gary Tully edited comment on AMQ-5961 at 9/28/15 3:51 PM:
--
peeking at the thread
Gary Tully created AMQ-5984:
---
Summary: Unsafe use of access-order LinkedHashMap via
ActiveMQMessageAuditNoSync - can lead to loop and hang
Key: AMQ-5984
URL: https://issues.apache.org/jira/browse/AMQ-5984
[
https://issues.apache.org/jira/browse/AMQ-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-5984:
Component/s: KahaDB
> Unsafe use of access-order LinkedHashMap via ActiveMQMessageAuditNoSync -
> can lead
[
https://issues.apache.org/jira/browse/AMQ-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5984.
-
Resolution: Fixed
ensure serial access to the message audit in kahaDB
> Unsafe use of access-order
1301 - 1400 of 1472 matches
Mail list logo
