[
https://issues.apache.org/jira/browse/ARTEMIS-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned ARTEMIS-2632:
---
Assignee: (was: Jean-Baptiste Onofré)
> CLONE - Prevent JMX registry rebind
>
[
https://issues.apache.org/jira/browse/ARTEMIS-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully moved AMQ-7422 to ARTEMIS-2632:
--
Component/s: (was: JMX)
JMX
Fix
Gary Tully created AMQ-7422:
---
Summary: CLONE - Prevent JMX registry rebind
Key: AMQ-7422
URL: https://issues.apache.org/jira/browse/AMQ-7422
Project: ActiveMQ
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/AMQ-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039994#comment-17039994
]
Gary Tully commented on AMQ-7291:
-
[~jbonofre], I think the properties on a message are different, normally
[
https://issues.apache.org/jira/browse/AMQ-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998949#comment-16998949
]
Gary Tully edited comment on AMQ-7368 at 12/18/19 8:51 AM:
---
there was a generic
[
https://issues.apache.org/jira/browse/AMQ-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998949#comment-16998949
]
Gary Tully commented on AMQ-7368:
-
there was a generic limitQuery statement added in
[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984514#comment-16984514
]
Gary Tully commented on AMQ-6831:
-
[~cshannon] I don't think that PR is related to the problem b/c that
[
https://issues.apache.org/jira/browse/AMQ-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982692#comment-16982692
]
Gary Tully commented on AMQ-7245:
-
I _think_ the root cause of this client side issue is a broker side
[
https://issues.apache.org/jira/browse/AMQ-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7353.
-
Resolution: Fixed
> Rare NPE during marshal, killing async dispatch task and potentially leaving
>
[
https://issues.apache.org/jira/browse/AMQ-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7353:
Summary: Rare NPE during marshal, killing async dispatch task and
potentially leaving un-marshal cache
[
https://issues.apache.org/jira/browse/AMQ-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982664#comment-16982664
]
Gary Tully edited comment on AMQ-7353 at 11/26/19 5:01 PM:
---
I added the causes
[
https://issues.apache.org/jira/browse/AMQ-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982664#comment-16982664
]
Gary Tully commented on AMQ-7353:
-
I added the causes relation here to
Gary Tully created AMQ-7353:
---
Summary: Rare NPE during marshall killing async dispatch task
Key: AMQ-7353
URL: https://issues.apache.org/jira/browse/AMQ-7353
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ARTEMIS-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16966778#comment-16966778
]
Gary Tully commented on ARTEMIS-2532:
-
for completeness, in 5.x I added the xaErrorCode to the
[
https://issues.apache.org/jira/browse/AMQ-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16947548#comment-16947548
]
Gary Tully commented on AMQ-7316:
-
that sounds like constantPendingMessageLimitStrategy is in play for
[
https://issues.apache.org/jira/browse/AMQ-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7311.
-
Resolution: Fixed
> KahaDB XA topic recovered pending ack tracking is store wide, needs to be per
>
Gary Tully created AMQ-7311:
---
Summary: KahaDB XA topic recovered pending ack tracking is store
wide, needs to be per subscription key
Key: AMQ-7311
URL: https://issues.apache.org/jira/browse/AMQ-7311
[
https://issues.apache.org/jira/browse/AMQ-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7308.
-
Resolution: Fixed
recovery processing will recreate the message store, otherwise the expectation
is that
[
https://issues.apache.org/jira/browse/AMQ-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7308:
Description: With a fast producer on a virtual topic, a jmx op to remove a
consumer queue will succeed but
Gary Tully created AMQ-7308:
---
Summary: Virtual Topic concurrent send with JMX consumer queue
deletion can lead to kahaDb leak
Key: AMQ-7308
URL: https://issues.apache.org/jira/browse/AMQ-7308
Project:
[
https://issues.apache.org/jira/browse/AMQ-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931515#comment-16931515
]
Gary Tully commented on AMQ-6391:
-
I can't say for certain, ideally if there is some wrapper in the mix
[
https://issues.apache.org/jira/browse/AMQ-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-4495:
Comment: was deleted
(was: [~cshannon]
{quote}
I've seen out of memory problems occasionally even though
[
https://issues.apache.org/jira/browse/AMQ-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928387#comment-16928387
]
Gary Tully commented on AMQ-6391:
-
disabling transaction tracking should do it, that state is only relevant
[
https://issues.apache.org/jira/browse/AMQ-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7302.
-
Resolution: Fixed
> JMX operation removeMessage(messageID) is not completing and leading to high
> CPU
Gary Tully created AMQ-7302:
---
Summary: JMX operation removeMessage(messageID) is not completing
and leading to high CPU usage
Key: AMQ-7302
URL: https://issues.apache.org/jira/browse/AMQ-7302
Project:
[
https://issues.apache.org/jira/browse/AMQ-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922572#comment-16922572
]
Gary Tully commented on AMQ-7185:
-
[~davidhilton68] I think [~jbonofre] is on the job based on the 5.15.10
[
https://issues.apache.org/jira/browse/AMQ-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7298.
-
Resolution: Fixed
The key observation was that local rollback delayed redelivery (with the
default 1s
[
https://issues.apache.org/jira/browse/AMQ-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922390#comment-16922390
]
Gary Tully edited comment on AMQ-7298 at 9/4/19 11:16 AM:
--
The root cause of
[
https://issues.apache.org/jira/browse/AMQ-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922390#comment-16922390
]
Gary Tully commented on AMQ-7298:
-
The root cause was duplicate redelivery from rollback delayed redelivery
[
https://issues.apache.org/jira/browse/AMQ-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7270.
-
Resolution: Fixed
> Queue's copyMatchingMessages effects maxPageSize in error
>
[
https://issues.apache.org/jira/browse/AMQ-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7270:
Summary: Queue's copyMatchingMessages effects maxPageSize in error (was:
Queue's copyMatchingMessages
Gary Tully created AMQ-7270:
---
Summary: Queue's copyMatchingMessages effects setMaxPageSize in
error
Key: AMQ-7270
URL: https://issues.apache.org/jira/browse/AMQ-7270
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/ARTEMIS-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-2433:
Labels: AMQP LDAP SASL (was: )
> Support LDAP role mapping of SASL EXTERNAL credentials
>
Gary Tully created ARTEMIS-2433:
---
Summary: Support LDAP role mapping of SASL EXTERNAL credentials
Key: ARTEMIS-2433
URL: https://issues.apache.org/jira/browse/ARTEMIS-2433
Project: ActiveMQ Artemis
[
https://issues.apache.org/jira/browse/AMQ-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888012#comment-16888012
]
Gary Tully commented on AMQ-7245:
-
It looks like an issue with the cache, that is per connection, I wonder
[
https://issues.apache.org/jira/browse/AMQ-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7234.
-
Resolution: Fixed
> Topic flow control with messages in a transaction can loop forever waiting
> for
[
https://issues.apache.org/jira/browse/AMQ-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869633#comment-16869633
]
Gary Tully commented on AMQ-7234:
-
Not sure why MemoryUsage must override the wait, wait(timeout) wait high
Gary Tully created AMQ-7234:
---
Summary: Topic flow control with messages in a transaction can
loop forever waiting for usage
Key: AMQ-7234
URL: https://issues.apache.org/jira/browse/AMQ-7234
Project:
[
https://issues.apache.org/jira/browse/AMQ-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7233.
-
Resolution: Fixed
> PooledConnectionFactory connection close does not delete temp dests if there
> is an
Gary Tully created AMQ-7233:
---
Summary: PooledConnectionFactory connection close does not delete
temp dests if there is an active consumer
Key: AMQ-7233
URL: https://issues.apache.org/jira/browse/AMQ-7233
[
https://issues.apache.org/jira/browse/AMQ-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866581#comment-16866581
]
Gary Tully commented on AMQ-7232:
-
The outlier may be the topic enqueue count, dequeue count is only
[
https://issues.apache.org/jira/browse/AMQ-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866534#comment-16866534
]
Gary Tully commented on AMQ-7232:
-
[~lionel.cons] I see your point, but there is no magic here. There are
[
https://issues.apache.org/jira/browse/ARTEMIS-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved ARTEMIS-2378.
-
Resolution: Fixed
> openwire redelivery counter for message increasing, if consumer is closed
[
https://issues.apache.org/jira/browse/AMQ-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863870#comment-16863870
]
Gary Tully edited comment on AMQ-7227 at 6/14/19 9:12 AM:
--
note: it is possible to
[
https://issues.apache.org/jira/browse/AMQ-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863870#comment-16863870
]
Gary Tully commented on AMQ-7227:
-
note: t is possible to workaround if the scheduleDB.free is copied to a
[
https://issues.apache.org/jira/browse/AMQ-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7227.
-
Resolution: Fixed
> Legacy store load failed: java.io.FileNotFoundException scheduleDB.free
>
Gary Tully created AMQ-7227:
---
Summary: Legacy store load failed: java.io.FileNotFoundException
scheduleDB.free
Key: AMQ-7227
URL: https://issues.apache.org/jira/browse/AMQ-7227
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/ARTEMIS-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-2378:
Description:
If a consumer closes without receiving any messages the redelivery count of
Gary Tully created ARTEMIS-2378:
---
Summary: openwire redelivery counter for message increasing, if
consumer is closed without consuming any message
Key: ARTEMIS-2378
URL:
[
https://issues.apache.org/jira/browse/AMQ-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860955#comment-16860955
]
Gary Tully commented on AMQ-7225:
-
[~cshannon] thanks. I noticed the same thing. there was another window
[
https://issues.apache.org/jira/browse/AMQ-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7225:
Affects Version/s: 5.15.0
> [mKahadb] over eager cleanup processing during recovery
>
[
https://issues.apache.org/jira/browse/AMQ-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7225.
-
Resolution: Fixed
Fix Version/s: 5.16.0
> [mKahadb] over eager cleanup processing during recovery
>
[
https://issues.apache.org/jira/browse/AMQ-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-7225:
---
Assignee: Gary Tully
> [mKahadb] over eager cleanup processing during recovery
>
Gary Tully created AMQ-7225:
---
Summary: [mKahadb] over eager cleanup processing during recovery
Key: AMQ-7225
URL: https://issues.apache.org/jira/browse/AMQ-7225
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7219.
-
Resolution: Fixed
Assignee: Gary Tully
Fix Version/s: 5.16.0
looks good.
it does beg the
[
https://issues.apache.org/jira/browse/AMQ-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7209:
Summary: [STOMP] SecurityException stack trace should not be in error
frames (was: [STOMP]
[
https://issues.apache.org/jira/browse/AMQ-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7209.
-
Resolution: Fixed
> [STOMP] SecurityException stack trace should no be in error frames
>
[
https://issues.apache.org/jira/browse/AMQ-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7209:
Summary: [STOMP] SecurityException stack trace should no be in error frames
(was: [STOMP] SecurityError
Gary Tully created AMQ-7209:
---
Summary: [STOMP] SecurityError stack trace should no be in error
frames
Key: AMQ-7209
URL: https://issues.apache.org/jira/browse/AMQ-7209
Project: ActiveMQ
Issue
[
https://issues.apache.org/jira/browse/AMQ-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841246#comment-16841246
]
Gary Tully commented on AMQ-5960:
-
[~jreock] I was investigating a similar issue just now, it looks like
[
https://issues.apache.org/jira/browse/AMQ-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7193.
-
Resolution: Fixed
> duplex network connector with pending forwards - intermittent NPE on startup
>
Gary Tully created AMQ-7193:
---
Summary: duplex network connector with pending forwards -
intermittent NPE on startup
Key: AMQ-7193
URL: https://issues.apache.org/jira/browse/AMQ-7193
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/ARTEMIS-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820923#comment-16820923
]
Gary Tully commented on ARTEMIS-2308:
-
my 2 cent;
I think it would be sufficient to have artemis
[
https://issues.apache.org/jira/browse/AMQ-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7185.
-
Resolution: Fixed
> XA durable sub prepared acks don't block redelivery
>
Gary Tully created AMQ-7185:
---
Summary: XA durable sub prepared acks don't block redelivery
Key: AMQ-7185
URL: https://issues.apache.org/jira/browse/AMQ-7185
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16813437#comment-16813437
]
Gary Tully commented on AMQ-7177:
-
This is one of those undefined JMS areas. See:
[
https://issues.apache.org/jira/browse/AMQ-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7167.
-
Resolution: Fixed
> IP address is missing from TransportConnector error message
>
Gary Tully created AMQ-7167:
---
Summary: IP address is missing from TransportConnector error
message
Key: AMQ-7167
URL: https://issues.apache.org/jira/browse/AMQ-7167
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7165.
-
Resolution: Fixed
> failover transport and rebalanceClusterClients=true should fall back to
> original
[
https://issues.apache.org/jira/browse/AMQ-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789569#comment-16789569
]
Gary Tully commented on AMQ-7165:
-
merging the updated and url list helps with AMQ-4505 also
> failover
[
https://issues.apache.org/jira/browse/AMQ-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789514#comment-16789514
]
Gary Tully commented on AMQ-7165:
-
part of the fix for AMQ-3685 seems to be the root cause. The upshot is
Gary Tully created AMQ-7165:
---
Summary: failover transport and rebalanceClusterClients=true
should fall back to original broker list if no broker on updated cluster
information is available
Key: AMQ-7165
URL:
[
https://issues.apache.org/jira/browse/AMQ-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785612#comment-16785612
]
Gary Tully commented on AMQ-7159:
-
+1 to more stats.
> Adding a new attribute on
[
https://issues.apache.org/jira/browse/AMQ-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5790.
-
Resolution: Fixed
Assignee: Gary Tully
Fix Version/s: 5.16.0
The RAR start/stop contract
[
https://issues.apache.org/jira/browse/AMQ-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777862#comment-16777862
]
Gary Tully commented on AMQ-5790:
-
AMQ-4486 needs to be reworked to resolve this, rather than using a new
[
https://issues.apache.org/jira/browse/AMQ-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776886#comment-16776886
]
Gary Tully commented on AMQ-7154:
-
[~cshannon] this is interesting, is this a preexisting inversion problem
[
https://issues.apache.org/jira/browse/AMQ-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761618#comment-16761618
]
Gary Tully commented on AMQ-7147:
-
It looks like the issue is: stopStartConnectors="true", this does not
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760809#comment-16760809
]
Gary Tully commented on AMQ-7080:
-
I am only offering thoughts, and thoughts are relatively cheap! I think
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760646#comment-16760646
]
Gary Tully commented on AMQ-7080:
-
I don't think it needs a feature flag.
The thought that keeps coming
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756325#comment-16756325
]
Gary Tully commented on AMQ-7080:
-
ahh, sorry [~alanprot] - apologies, I was on the wrong track - I
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756209#comment-16756209
]
Gary Tully commented on AMQ-7080:
-
{quote}If I understood you correctly you are saying that instead of
[
https://issues.apache.org/jira/browse/AMQ-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756022#comment-16756022
]
Gary Tully commented on AMQ-7080:
-
this is interesting. the async recovery will be expensive for sure, it
[
https://issues.apache.org/jira/browse/AMQ-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7125.
-
Resolution: Fixed
Fix Version/s: 5.16.0
[~avi5k...@gmail.com] I committed a variation of the pr
[
https://issues.apache.org/jira/browse/AMQ-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-7125:
---
Assignee: Gary Tully
> AMQ broker does not send the error frame back to the websocket client when an
[
https://issues.apache.org/jira/browse/AMQ-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740297#comment-16740297
]
Gary Tully commented on AMQ-7132:
-
this looks like a great improvement [~alanprot], avoiding a full index
[
https://issues.apache.org/jira/browse/AMQ-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740285#comment-16740285
]
Gary Tully edited comment on AMQ-7129 at 1/11/19 11:02 AM:
---
[~cshannon] I never
[
https://issues.apache.org/jira/browse/AMQ-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740285#comment-16740285
]
Gary Tully commented on AMQ-7129:
-
[~cshannon] I never got a handle on the need for individual ack on a
[
https://issues.apache.org/jira/browse/AMQ-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703070#comment-16703070
]
Gary Tully commented on AMQ-7115:
-
TLS session resume avoiding an rtt allows application data to piggyback
[
https://issues.apache.org/jira/browse/AMQ-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7115.
-
Resolution: Fixed
> Deadlock between MQTTInactivityMonitor and BrokerService Threads
>
[
https://issues.apache.org/jira/browse/AMQ-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701953#comment-16701953
]
Gary Tully commented on AMQ-7115:
-
The serviceRead with the start lock held can only occur if it wins the
[
https://issues.apache.org/jira/browse/AMQ-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7115:
Environment:
(was: {code}
{code})
> Deadlock between MQTTInactivityMonitor and BrokerService Threads
>
Gary Tully created AMQ-7115:
---
Summary: Deadlock between MQTTInactivityMonitor and BrokerService
Threads
Key: AMQ-7115
URL: https://issues.apache.org/jira/browse/AMQ-7115
Project: ActiveMQ
Issue
[
https://issues.apache.org/jira/browse/AMQ-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7106.
-
Resolution: Fixed
The same fix pattern could be applied to the stop/stopping choreography however
that
[
https://issues.apache.org/jira/browse/AMQ-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7106:
Description:
If start blocks, the inactivity monitor can kick in. The intent is that it can
see the
Gary Tully created AMQ-7106:
---
Summary: TransportConnection pendingStop support during start is
broken
Key: AMQ-7106
URL: https://issues.apache.org/jira/browse/AMQ-7106
Project: ActiveMQ
Issue
[
https://issues.apache.org/jira/browse/AMQ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7102.
-
Resolution: Fixed
> managementContext suppressMBean filters registration but still tracks objects
> as
Gary Tully created AMQ-7102:
---
Summary: managementContext suppressMBean filters registration but
still tracks objects as registered in error
Key: AMQ-7102
URL: https://issues.apache.org/jira/browse/AMQ-7102
[
https://issues.apache.org/jira/browse/AMQ-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686573#comment-16686573
]
Gary Tully commented on AMQ-7096:
-
Please provide a standalone test case that asserts that the bug is in
[
https://issues.apache.org/jira/browse/AMQ-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7009.
-
Resolution: Fixed
Assignee: Gary Tully
Fix Version/s: 5.16.0
Thanks for the test case and
[
https://issues.apache.org/jira/browse/AMQ-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully closed AMQ-6903.
---
Resolution: Not A Bug
The answer is in the error message from the log, you got to start there before
opening
601 - 700 of 1463 matches
Mail list logo
