You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Thomas Diesler (JIRA)" <ji...@apache.org> on 2015/04/28 10:22:05 UTC
[jira] [Updated] (CAMEL-8711) JMS Session not exposed to Camel
route
[ https://issues.apache.org/jira/browse/CAMEL-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler updated CAMEL-8711:
----------------------------------
Description:
On a JMS message consumer route, we support
{code}
jms:...&acknowledgementModeName=CLIENT_ACKNOWLEDGE
{code}
The pattern is that a client may chose to process a batch of msgs before it acks. If batch processing succeeds the client calls Message.acknowledge(). If it fails, the client may choose to recover the msgs in the batch with Session.recover()
The Session is however not exposed to the client, which makes it impossible to call Session.recover(). CLIENT_ACKNOWLEDGE has IMHO currently limited use because of this.
CrossRef: https://jira.spring.io/browse/SPR-12961
was:
On a JMS message consumer route, we support
{code}
jms:...&acknowledgementModeName=CLIENT_ACKNOWLEDGE
{code}
The pattern is that a client may chose to process a batch of msgs before it acks. If batch processing succeeds the client calls Message.acknowledge(). If it fails, the client may choose to recover the msgs in the batch with Session.recover()
The Session is however not exposed to the client, which makes it impossible to call Session.recover(). CLIENT_ACKNOWLEDGE has IMHO currently limited use because of this.
> JMS Session not exposed to Camel route
> --------------------------------------
>
> Key: CAMEL-8711
> URL: https://issues.apache.org/jira/browse/CAMEL-8711
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 2.15.1
> Reporter: Thomas Diesler
>
> On a JMS message consumer route, we support
> {code}
> jms:...&acknowledgementModeName=CLIENT_ACKNOWLEDGE
> {code}
> The pattern is that a client may chose to process a batch of msgs before it acks. If batch processing succeeds the client calls Message.acknowledge(). If it fails, the client may choose to recover the msgs in the batch with Session.recover()
> The Session is however not exposed to the client, which makes it impossible to call Session.recover(). CLIENT_ACKNOWLEDGE has IMHO currently limited use because of this.
> CrossRef: https://jira.spring.io/browse/SPR-12961
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)