camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-8711) JMS Session not exposed to Camel route
Date Wed, 06 May 2015 10:40:00 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530318#comment-14530318
] 

Claus Ibsen commented on CAMEL-8711:
------------------------------------

You can now get the JMS session from the Camel JmsMessage.

{code}
Exchange exchange = ...
JmsMessage camelMsg = exchange.getIn(JmsMessage.class);
Session session = camelMsg.getJmsSession();
// and the JMS message as today
Message jmsMessage = camelMsg.getJmsMessage();
{code}


> JMS Session not exposed to Camel route
> --------------------------------------
>
>                 Key: CAMEL-8711
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8711
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 2.15.1
>            Reporter: Thomas Diesler
>            Assignee: Claus Ibsen
>             Fix For: 2.16.0
>
>
> 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)

Mime
View raw message