[jira] [Commented] (CAMEL-16811) Cannot consume messages from sjms2 endpoint with deliveryMode set

["Shannon Gallagher (Jira)" <ji...@apache.org>]

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

Shannon Gallagher commented on CAMEL-16811:
-------------------------------------------

Upon further investigation, I did find that I can consume a message from an sjms2 endpoint with deliveryMode specified, if I also set timeToLive.

I'm not sure if this is by designed in the camel component or JMS 2.0, but I did not see any documentation indicating that I needed to set timeToLive in conjunction with deliveryMode.

I suppose this may be a non-issue if that is by designed, but it might be helpful to include in the docs if that is the case :)  

> Cannot consume messages from sjms2 endpoint with deliveryMode set
> -----------------------------------------------------------------
>
>                 Key: CAMEL-16811
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16811
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-sjms
>    Affects Versions: 3.8.0
>            Reporter: Shannon Gallagher
>            Priority: Minor
>
> (Note: The component in question should be camel-sjms2, but that was not an option in the component list.)
> Messages cannot be consumed from an sjms2 endpoint with a delivery mode query parameter specified.
> To reproduce this issue, I was using InOnlyQueueProducerTest in both the camel-sjms and camel-sjms2 components. In both tests, I changed the first producer endpoint URI to the following (where component is sjms and sjms2, respectively):
> {code:java}
> .to("[sjms,sjms2]:queue:" + TEST_DESTINATION_NAME + "?deliveryMode=1");
> {code}
> The sjms test continues to succeed, but the sjms2 test fails due to the consumer not receiving the message before timing out.
>  
> I could not determine a root cause, but as a workaround, I did discover that manually setting the JMSDeliveryMode header in the route or in the send call did work as expected. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)