[
https://issues.apache.org/jira/browse/CAMEL-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811375#comment-13811375
]
Scott England-Sullivan commented on CAMEL-6362:
-----------------------------------------------
Hi Babak,
No reason other than time right now. I was going to go through and catching up
in trunk and then planned to see what branches were available at that time. We
seem to release bug-fix branches quickly at times and I ended up missing a
couple of them. So I just focused on latest to get caught up.
I am also a little concerned with some of the backports breaking backwards
compatibility. My understanding was that minor release were allowing changes
in a components behavior where bug fix releases were just that, bug fix only.
This patch actually changes the session pooling behavior.
> camel-sjms - Consumers should always use dedicated Sessions
> -----------------------------------------------------------
>
> Key: CAMEL-6362
> URL: https://issues.apache.org/jira/browse/CAMEL-6362
> Project: Camel
> Issue Type: Improvement
> Components: camel-sjms
> Affects Versions: 2.11.0
> Reporter: Aaron Whiteside
> Assignee: Scott England-Sullivan
> Fix For: 2.13.0
>
>
> If you add more then one MessageListener to a Session then that session will
> use a single thread to notify each MessageListener in turn. Which defeats
> the purpose of using multiple MessageListeners, at least in my opinion.
> sessionCount in SjmsEndpoint should be ignored for Consumers, each Consumer
> (consumerCount) should instead use a dedicated Session, like what happens
> when transactions are enabled.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
