[
https://issues.apache.org/jira/browse/AMQ-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284105#comment-14284105
]
Eyad Ebrahim commented on AMQ-2079:
-----------------------------------
Thanks for the info. However, it's added for release 5.11.0, I think we can
assume that for 5.10.0 there is no way to manage your own session.
Anyway, sticking to the JMS specs doesn't seem like the worse idea. Probably
that's the direction we're going to go for.
Thanks again for your promptness.
> conflict between checking validity of createSession args and requirement to
> ignore them in managed environment
> --------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2079
> URL: https://issues.apache.org/jira/browse/AMQ-2079
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.3.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 5.3.0
>
>
> Since amq 4 someone added some parameter checking to
> ActiveMQConnection.createSession. This seems like a good idea until you get
> to the connector and read the ejb spec where it says in a managed environment
> these parameters should be ignored. I'm not sure how much they really can be
> ignored if an xa tx is not present. What I've done is to enhance the
> checking in ActiveMQConnection.createSession to be more thorough with better
> messages and to modify the ra ManagedConnectionProxy to modify one of the
> parameters if they are inconsistent (i.e. transacted == false, but ack mode
> == SESSION_TRANSACTED) (I change it to AUTO_ACKNOWLDEDGE). I haven't found
> this causing any problems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
