Gary Tully created AMQ-7035:
---
Summary: Memory usage incorrectly increases when selectors are
used in JMX operations
Key: AMQ-7035
URL: https://issues.apache.org/jira/browse/AMQ-7035
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16572866#comment-16572866
]
Gary Tully commented on AMQ-7028:
-
I think the policy entry doOptimzeMessageStorage will cover
[
https://issues.apache.org/jira/browse/AMQ-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566985#comment-16566985
]
Gary Tully edited comment on AMQ-7028 at 8/2/18 3:56 PM:
-
[~cshannon] I don't know.
[
https://issues.apache.org/jira/browse/AMQ-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566985#comment-16566985
]
Gary Tully commented on AMQ-7028:
-
I don't know. It is a sensible change though, waiting for the cursor to
[
https://issues.apache.org/jira/browse/AMQ-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7030.
-
Resolution: Fixed
> unhandled CancellationException in cursor duplicate detection logic
>
[
https://issues.apache.org/jira/browse/AMQ-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7030:
Description:
With concurrentStoreAndDispatchQueues true, a CancellationException can bubble
up to pageIn in
Gary Tully created AMQ-7030:
---
Summary: unhandled CancellationException in cursor duplicate
detection logic
Key: AMQ-7030
URL: https://issues.apache.org/jira/browse/AMQ-7030
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561903#comment-16561903
]
Gary Tully commented on AMQ-2659:
-
[~cshannon] thanks for the heads up, apologies. yes - the config for
[
https://issues.apache.org/jira/browse/AMQ-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559757#comment-16559757
]
Gary Tully commented on AMQ-7015:
-
unlike ignoreMissingJournalfiles/checkForCorruptJournalFiles leaving
[
https://issues.apache.org/jira/browse/AMQ-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7010.
-
Resolution: Won't Fix
updated the documentation for the ignoreNoSpaceErrors attribute with:
>From 5.15.0
[
https://issues.apache.org/jira/browse/AMQ-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559646#comment-16559646
]
Gary Tully commented on AMQ-7010:
-
I agree. It is best to stop. The latest update to this feature
[
https://issues.apache.org/jira/browse/AMQ-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6967.
-
Resolution: Fixed
complete.
> Periodic expiry with no consumers fails to page in messages if cache has
>
[
https://issues.apache.org/jira/browse/AMQ-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559472#comment-16559472
]
Gary Tully commented on AMQ-7015:
-
my issue is that you are using xml config to do an admin task that would
[
https://issues.apache.org/jira/browse/AMQ-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558405#comment-16558405
]
Gary Tully commented on AMQ-7015:
-
Having a mbean.rollbackAll operation leaves the broker still capable to
[
https://issues.apache.org/jira/browse/AMQ-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558171#comment-16558171
]
Gary Tully commented on AMQ-7015:
-
[~jgenender] there may be cross wires here, my suggestion was to have an
[
https://issues.apache.org/jira/browse/AMQ-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7021.
-
Resolution: Fixed
A virtual topic send intensive test is ~40% better with the changes b/c
matching on the
Gary Tully created AMQ-7021:
---
Summary: DestinationMap access inside Abstract Region readwrite
lock does not need sync
Key: AMQ-7021
URL: https://issues.apache.org/jira/browse/AMQ-7021
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-6954:
Fix Version/s: 5.15.5
5.16.0
> Queue page on web console displays URL parameter without
[
https://issues.apache.org/jira/browse/AMQ-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1630#comment-1630
]
Gary Tully commented on AMQ-6954:
-
resolved with:
[
https://issues.apache.org/jira/browse/AMQ-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6954.
-
Resolution: Fixed
> Queue page on web console displays URL parameter without proper encoding
>
[
https://issues.apache.org/jira/browse/AMQ-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16552539#comment-16552539
]
Gary Tully commented on AMQ-7015:
-
this feature breaks the xa contract, recovery is part of xa, the TM will
[
https://issues.apache.org/jira/browse/AMQ-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7007:
Summary: Limit the jetty endpoint to localhost by default (web
console/jolokia) (was: Limit the default
[
https://issues.apache.org/jira/browse/AMQ-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7007.
-
Resolution: Fixed
The doc already references localhost
http://activemq.apache.org/web-console.html
>
Gary Tully created AMQ-7007:
---
Summary: Limit the default jetty endpoint to localhost by default
(web console/jolokia)
Key: AMQ-7007
URL: https://issues.apache.org/jira/browse/AMQ-7007
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16527363#comment-16527363
]
Gary Tully edited comment on AMQ- at 6/29/18 9:45 AM:
--
The sendTimeout is
[
https://issues.apache.org/jira/browse/AMQ-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16527363#comment-16527363
]
Gary Tully commented on AMQ-:
-
The sendTimeout is confined to message send commands.
these transaction
[
https://issues.apache.org/jira/browse/AMQ-7002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525203#comment-16525203
]
Gary Tully commented on AMQ-7002:
-
I don't see any issue with the change in the format of the job id
[
https://issues.apache.org/jira/browse/AMQ-7002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7002.
-
Resolution: Fixed
Assignee: Gary Tully
Fix Version/s: (was: 5.x)
[
https://issues.apache.org/jira/browse/AMQ-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524993#comment-16524993
]
Gary Tully edited comment on AMQ-6575 at 6/27/18 1:02 PM:
--
[~meth] I was in that
[
https://issues.apache.org/jira/browse/AMQ-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524993#comment-16524993
]
Gary Tully edited comment on AMQ-6575 at 6/27/18 12:46 PM:
---
[~meth] I was in that
[
https://issues.apache.org/jira/browse/AMQ-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524993#comment-16524993
]
Gary Tully edited comment on AMQ-6575 at 6/27/18 12:46 PM:
---
[~meth] I was in that
[
https://issues.apache.org/jira/browse/AMQ-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524993#comment-16524993
]
Gary Tully commented on AMQ-6575:
-
[~meth] I was in that area of the code today and came to the same
[
https://issues.apache.org/jira/browse/AMQ-7001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7001.
-
Resolution: Fixed
> Contention on message properties with amqp jms transfromer and kahadb
>
[
https://issues.apache.org/jira/browse/AMQ-7002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523801#comment-16523801
]
Gary Tully commented on AMQ-7002:
-
running the scheduled package: org.apache.activemq.broker.scheduler -
[
https://issues.apache.org/jira/browse/AMQ-7001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-7001:
Description:
Openwire to AMQP
Send can fail with ConcurrentModificationException. Stack trace:
{code:java}
Gary Tully created AMQ-7001:
---
Summary: Contention on message properties with amqp jms
transfromer and kahadb concurrentStoreAndDispatch
Key: AMQ-7001
URL: https://issues.apache.org/jira/browse/AMQ-7001
[
https://issues.apache.org/jira/browse/AMQ-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-7000.
-
Resolution: Fixed
> RAR - occasional hang on graceful server shutdown
>
Gary Tully created AMQ-7000:
---
Summary: RAR - occasional hang on graceful server shutdown
Key: AMQ-7000
URL: https://issues.apache.org/jira/browse/AMQ-7000
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512176#comment-16512176
]
Gary Tully commented on AMQ-6986:
-
it is by design because the jdbc store does not have an index.
the
[
https://issues.apache.org/jira/browse/AMQ-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2659.
-
Resolution: Fixed
Fix Version/s: 5.16.0
To use a non transacted ack mode in XASessions, it now
[
https://issues.apache.org/jira/browse/AMQ-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-2659:
-
Revisiting this, I now think the change needs to be configurable.
I came across a use case with an XASession
[
https://issues.apache.org/jira/browse/AMQ-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497915#comment-16497915
]
Gary Tully commented on AMQ-5129:
-
it may still be no harm to introduce the scheduled executor even with a
[
https://issues.apache.org/jira/browse/AMQ-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6979.
-
Resolution: Fixed
> consumer message pull timeout being effected by long running scheduled tasks
>
[
https://issues.apache.org/jira/browse/AMQ-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496357#comment-16496357
]
Gary Tully commented on AMQ-6977:
-
maybe post your connection pool configuration; the exception says it is
[
https://issues.apache.org/jira/browse/AMQ-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496314#comment-16496314
]
Gary Tully commented on AMQ-5875:
-
w.r.t the test regression - it is most likely the fix from AMQ-6901 that
[
https://issues.apache.org/jira/browse/AMQ-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495124#comment-16495124
]
Gary Tully commented on AMQ-6979:
-
Linking in AMQ-5129 which has a patch for replacing the timerThread with
[
https://issues.apache.org/jira/browse/AMQ-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494954#comment-16494954
]
Gary Tully commented on AMQ-6979:
-
I had a quick peek at giving the existing TimerThread based scheduler a
Gary Tully created AMQ-6979:
---
Summary: consumer message pull timeout being effected by long
running scheduled tasks
Key: AMQ-6979
URL: https://issues.apache.org/jira/browse/AMQ-6979
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/ARTEMIS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487386#comment-16487386
]
Gary Tully commented on ARTEMIS-856:
I think they only help with loadbalancing, the first exclusive
[
https://issues.apache.org/jira/browse/ARTEMIS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-856:
---
Description:
Add support enhancing destination consumer features (ActiveMQ 5.x parity):
[
https://issues.apache.org/jira/browse/AMQ-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487104#comment-16487104
]
Gary Tully edited comment on AMQ-6972 at 5/23/18 11:30 AM:
---
I made that
[
https://issues.apache.org/jira/browse/AMQ-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487104#comment-16487104
]
Gary Tully commented on AMQ-6972:
-
I made that modification of the destination and setting of the original
Gary Tully created AMQ-6967:
---
Summary: Periodic expiry with no consumers fails to page in
messages if cache has flipped
Key: AMQ-6967
URL: https://issues.apache.org/jira/browse/AMQ-6967
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6707.
-
Resolution: Fixed
Fix Version/s: 5.16.0
I think this should be sorted on trunk now. The
[
https://issues.apache.org/jira/browse/AMQ-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6956.
-
Resolution: Information Provided
> java.net.SocketException: Connection closed by remote host thrown during
[
https://issues.apache.org/jira/browse/AMQ-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468933#comment-16468933
]
Gary Tully edited comment on AMQ-6956 at 5/9/18 3:43 PM:
-
I think that is just a
[
https://issues.apache.org/jira/browse/AMQ-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468933#comment-16468933
]
Gary Tully commented on AMQ-6956:
-
I think that is just a race between the client sending its shutdown
[
https://issues.apache.org/jira/browse/AMQ-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462261#comment-16462261
]
Gary Tully commented on AMQ-6707:
-
This is also relevant:
AMQ-6906 tidy up cleanup on jdbc error and
[
https://issues.apache.org/jira/browse/AMQ-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461059#comment-16461059
]
Gary Tully commented on AMQ-6938:
-
note: if journal files are manually removed, then the index needs to be
[
https://issues.apache.org/jira/browse/AMQ-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454205#comment-16454205
]
Gary Tully commented on AMQ-6707:
-
I think the issue is that the callbacks can be be invoked twice on
[
https://issues.apache.org/jira/browse/AMQ-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6929:
---
Assignee: Gary Tully
> ERROR | Failed to start Apache ActiveMQ ([localhost, null],
>
[
https://issues.apache.org/jira/browse/AMQ-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6929:
---
Assignee: (was: Gary Tully)
> ERROR | Failed to start Apache ActiveMQ ([localhost, null],
>
[
https://issues.apache.org/jira/browse/AMQ-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6707:
---
Assignee: Gary Tully
> JDBC XA: Could not remove prepared transaction state from message
>
[
https://issues.apache.org/jira/browse/AMQ-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411134#comment-16411134
]
Gary Tully commented on AMQ-6936:
-
That was resolved via:
[
https://issues.apache.org/jira/browse/ARTEMIS-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved ARTEMIS-1758.
-
Resolution: Fixed
> Support SASL EXTERNAL
> -
>
> Key:
[
https://issues.apache.org/jira/browse/ARTEMIS-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408346#comment-16408346
]
Gary Tully commented on ARTEMIS-1758:
-
note: the EXTERNAL mechanism does not do a jaas login to
[
https://issues.apache.org/jira/browse/ARTEMIS-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408346#comment-16408346
]
Gary Tully edited comment on ARTEMIS-1758 at 3/21/18 6:08 PM:
--
note: the
[
https://issues.apache.org/jira/browse/ARTEMIS-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408159#comment-16408159
]
Gary Tully commented on ARTEMIS-1758:
-
SASL EXTERNAL will only work with an empty response from the
[
https://issues.apache.org/jira/browse/ARTEMIS-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-1758:
Description:
Add support for SASL EXTERNAL
https://tools.ietf.org/html/rfc4422#appendix-A
Peer
Gary Tully created ARTEMIS-1758:
---
Summary: Support SASL EXTERNAL
Key: ARTEMIS-1758
URL: https://issues.apache.org/jira/browse/ARTEMIS-1758
Project: ActiveMQ Artemis
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/AMQ-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406183#comment-16406183
]
Gary Tully commented on AMQ-6931:
-
I think this is solved via:
[
https://issues.apache.org/jira/browse/AMQ-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396848#comment-16396848
]
Gary Tully commented on AMQ-6926:
-
there is a vm: create=false option that will cause the vm transport to
[
https://issues.apache.org/jira/browse/ARTEMIS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388063#comment-16388063
]
Gary Tully commented on ARTEMIS-1552:
-
[~jbertram] yes. just marked it resolved. thanks.
> SASL
[
https://issues.apache.org/jira/browse/ARTEMIS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved ARTEMIS-1552.
-
Resolution: Fixed
> SASL GSSAPI IBM JDK - clients get authentication refused first time they
>
[
https://issues.apache.org/jira/browse/AMQ-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4261.
-
Resolution: Fixed
Fix Version/s: 5.16.0
> Please change logging message from INFO to WARN or ERROR
[
https://issues.apache.org/jira/browse/AMQ-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383429#comment-16383429
]
Gary Tully edited comment on AMQ-4261 at 3/2/18 10:26 AM:
--
I am coming around to
[
https://issues.apache.org/jira/browse/AMQ-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-4261:
-
Assignee: Gary Tully
I am coming around to the view that this should be a WARN, b/c it typically
impacts
[
https://issues.apache.org/jira/browse/AMQ-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6907.
-
Resolution: Fixed
> Make conditionalNetworkBridgeFilterFactory selectorAware
>
Gary Tully created AMQ-6907:
---
Summary: Make conditionalNetworkBridgeFilterFactory selectorAware
Key: AMQ-6907
URL: https://issues.apache.org/jira/browse/AMQ-6907
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6906.
-
Resolution: Fixed
> XA JDBC rolled back recovered ack messages pending till restart when cache
> disabled
Gary Tully created AMQ-6906:
---
Summary: XA JDBC rolled back recovered ack messages pending till
restart when cache disabled
Key: AMQ-6906
URL: https://issues.apache.org/jira/browse/AMQ-6906
Project:
[
https://issues.apache.org/jira/browse/AMQ-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363813#comment-16363813
]
Gary Tully commented on AMQ-6899:
-
there is a test for this feature in karaf that may help reproduce or
[
https://issues.apache.org/jira/browse/ARTEMIS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved ARTEMIS-1030.
-
Resolution: Fixed
doco now up-to-date with the escapes.
> Support equivilent ActiveMQ 5.x
[
https://issues.apache.org/jira/browse/AMQ-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6891.
-
Resolution: Fixed
fixed up the non transacted path and reused the leak test, thanks.
> Duplicated message
[
https://issues.apache.org/jira/browse/ARTEMIS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343639#comment-16343639
]
Gary Tully commented on ARTEMIS-853:
5.x has: allConsumersExclusiveByDefault destination policy[1];
[
https://issues.apache.org/jira/browse/AMQ-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-6891:
-
the non transacted case has this issue also. Most often store IOErrors would
result in the broker stop.
[
https://issues.apache.org/jira/browse/AMQ-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6891.
-
Resolution: Fixed
Fix Version/s: 5.16.0
It think your fix is on the money and the completion should
[
https://issues.apache.org/jira/browse/AMQ-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340992#comment-16340992
]
Gary Tully commented on AMQ-6891:
-
[~rkraus] thanks for the great test and analysis. I think you have
[
https://issues.apache.org/jira/browse/AMQ-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-6891:
---
Assignee: Gary Tully
> Duplicated message in JMS transaction, when jdbc persistence fails (Memory
>
[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340904#comment-16340904
]
Gary Tully commented on ARTEMIS-550:
Thanks [~graben] for the code, I will follow up early next week.
[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339049#comment-16339049
]
Gary Tully commented on ARTEMIS-550:
peek again:
[
https://issues.apache.org/jira/browse/ARTEMIS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-1030:
Comment: was deleted
(was: it looks like a 5.x wildcard value cannot be encoded in an acceptor
[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339020#comment-16339020
]
Gary Tully commented on ARTEMIS-550:
[~graben] The only OpenWire client is the 5.x client. If you are
[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337658#comment-16337658
]
Gary Tully edited comment on ARTEMIS-550 at 1/24/18 2:33 PM:
-
[~graben] I
[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337658#comment-16337658
]
Gary Tully commented on ARTEMIS-550:
[~graben] I peeked some more - it is not ideal but url escaping
[
https://issues.apache.org/jira/browse/ARTEMIS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened ARTEMIS-1030:
-
it looks like a 5.x wildcard value cannot be encoded in an acceptor uri, one
problem is the ';'
[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337390#comment-16337390
]
Gary Tully commented on ARTEMIS-550:
[~graben] thanks for the fast feedback... darn I missed that,
[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335583#comment-16335583
]
Gary Tully commented on ARTEMIS-550:
[~graben] [~mattrpav] have a peek at the
[
https://issues.apache.org/jira/browse/ARTEMIS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved ARTEMIS-1241.
-
Resolution: Fixed
Fix Version/s: 2.5.0
> Auto create does not work for FQQN queues
>
[
https://issues.apache.org/jira/browse/ARTEMIS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved ARTEMIS-1030.
-
Resolution: Fixed
Fix Version/s: 2.5.0
note the related documentation additions for
801 - 900 of 1463 matches
Mail list logo
