[
https://issues.apache.org/jira/browse/CAMEL-26506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-26506 started by Claus Ibsen.
-------------------------------------------
> camel-jms / camel-sjms - transferException reply together with a rollback,
> and the sjms consumer keeps a StreamMessage raw
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26506
> URL: https://issues.apache.org/jira/browse/CAMEL-26506
> Project: Camel
> Issue Type: Bug
> Components: camel-jms, camel-sjms
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> Two finds from CAMEL-26152 (PR #28925), not fixed there.
> # With transferException=true the consumer looks up the failure with
> getException(RuntimeCamelException.class), which walks the causes. It can
> then send the exception as the reply and also roll back the transacted
> session, so the reply is sent and the request is redelivered. camel-jms and
> camel-sjms both do this.
> # The camel-sjms consumer gives the raw jakarta.jms.StreamMessage as the
> body, where camel-jms maps it to an InputStream. So a round trip of a stream
> body over sjms does not give the bytes back.
> Needs a closer look before fixing.
> _Claude Code on behalf of Claus Ibsen (davsclaus)_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
