GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/703
ARTEMIS-601 + logger fixes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-601
Alternatively you
sorry, I forgot to mention the version...
We are using 5.11.1. I diff between v10 and v11 and also 5.11.1 and 5.13.4
on the affected OpenWire code and they looked somewhat the same.
Thanks!
--
View this message in context:
What version are you using? There have been various bug fixes and
improvements with this in later releases, especially 5.12.0 which
introduced OpenWire v11. Since you are using OpenWire v10 I'm assuming you
have an older release so you should try upgrading.
On Fri, Aug 5, 2016 at 11:56 AM,
I am trying to drop any large messages by setting maxFrameSize=262144 and it
seems that it negotiated the setting.
2016-07-25T12:52:10.040-0700 CEF:1 | good |
wrap_mvn_com.good.activemq_osgi.activemq-gems_5.11.1 | 0.0.0 | DEBUG |
unknown | 3 | ID=147 THR=.137:61616@39196 CAT=WireFormatNegotiator
Results of the ActiveMQ 5.14.0 vote:
Vote passes with 4 +1 binding votes.
The following votes were received:
Binding:
+1 Dan Kulp
+1 Timothy Bish
+1 Christopher Shannon
+1 Claus Ibsen
Non Binding:
+1 Hassen Bennour
+1 John Ament
+1 Robbie Gemmell
I'll start pushing out the release bundles
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/690
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/701
I am not sure would really be that user friendly as you defined. it
could be confusing actually.
you already have permissions to createQueue, createDurableQueue and
Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/701
To track our offline conversations.
For sake of conversation I'm describing the equivilent "virtual topics"
feature as a "shared subscription".
We've established the use
