GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/395
ARTEMIS-404 fixing space issues on scripts
https://issues.apache.org/jira/browse/ARTEMIS-404
You can merge this pull request into a Git repository by running:
$ git pull https:
Ok, that's an issue then :)
@Lionel: Can you open a JIRA?
On Thu, Feb 18, 2016 at 2:36 PM, Timothy Bish wrote:
> On 02/18/2016 02:24 PM, Hiram Chirino wrote:
>> I thought that ACKs were supposed to be transactional per the spec.
> That was my understanding as well, here's the relevant text from
On 02/18/2016 02:24 PM, Hiram Chirino wrote:
> I thought that ACKs were supposed to be transactional per the spec.
That was my understanding as well, here's the relevant text from the spec.
"|ACK| is used to acknowledge consumption of a message from a
subscription using |client| or |client-individ
I thought that ACKs were supposed to be transactional per the spec.
On Thursday, February 18, 2016, Clebert Suconic
wrote:
> TBH I don't remember what Hiram (et all) wrote on the spec. It will be
> a bug depending on what's said at the spec.
>
> On Thu, Feb 18, 2016 at 9:43 AM, Lionel Cons > wr
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/392
---
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 featu
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/393
---
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 featu
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/394
---
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 featu
I am modelling my systems such that there is only one session per
connection per thread, but there are a lot of consumers per session (
hundreds ) which in-turn consume messages from hundreds of different
destinations.
The message listener associated with each consumer is very light weight and
doe
TBH I don't remember what Hiram (et all) wrote on the spec. It will be
a bug depending on what's said at the spec.
On Thu, Feb 18, 2016 at 9:43 AM, Lionel Cons wrote:
> The Artemis 1.2.0 doc contains:
>
> | Message acknowledgements are not transactional. The ACK frame can not be
> part
> | of
The Artemis 1.2.0 doc contains:
| Message acknowledgements are not transactional. The ACK frame can not be part
| of a transaction (it will be ignored if its transaction header is set).
Is this a design decision (meaning that this behaviour will not change) or is
this considered as a bug (that
GitHub user dudaerich opened a pull request:
https://github.com/apache/activemq-artemis/pull/394
ARTEMIS-403 - [Artemis Testsuite] AlmostLargeAsynchronousFailoverTestâ¦
â¦#testTransactional fails
You can merge this pull request into a Git repository by running:
$ git pull htt
could you raise a Jira please?
On 18/02/16 12:50, Lionel Cons wrote:
Using Jolokia, it is very easy to list all the attributes exposed by Artemis:
$ jmx4perl http://localhost:8161/jolokia/ list
'org.apache.activemq.artemis:brokerName="0.0.0.0",module=JMS,name="DLQ",serviceType=Queue,type=Brok
Using Jolokia, it is very easy to list all the attributes exposed by Artemis:
$ jmx4perl http://localhost:8161/jolokia/ list
'org.apache.activemq.artemis:brokerName="0.0.0.0",module=JMS,name="DLQ",serviceType=Queue,type=Broker'
org.apache.activemq.artemis:brokerName="0.0.0.0",module=JMS,name="DLQ
13 matches
Mail list logo
