[
https://issues.apache.org/jira/browse/ARTEMIS-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116764#comment-16116764
]
ASF GitHub Bot commented on ARTEMIS-1308:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1428
@clebertsuconic thanks, ill run that.
re the individual acks on that test, simple moved the close method before
checking state in the test, as on close state is actual, before that with block
on ack it is just eventual. have pushed this change.
> Client Acknowledge not performant
> ---------------------------------
>
> Key: ARTEMIS-1308
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1308
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Michael Andre Pearce
> Assignee: Michael Andre Pearce
> Priority: Critical
> Fix For: 2.3.0
>
>
> Artemis recommendation in docs is to use CLIENT_ACKNOWLEDGE instead of
> AUTO_ACKNOWLEDGE, on perf testing it seems this is not the case.
> On checking code it seems the reason for this is because ActiveMQMessage
> acknowledge actually calls session.commit, causing a full session commit all
> the time.
> On checking Core API, calling message.acknowledge it seems to behave as
> expected, as such believe this to be an issue in JMS api wrapper, that it
> should just be delegating to the ClientMessage.acknowledge method and this is
> the cause of the perf issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
