[ https://issues.apache.org/jira/browse/KARAF-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2919:
----------------------------------------
Fix Version/s: (was: 2.3.8)
2.3.9
> karaf jms:* commands works in non-transacted mode
> -------------------------------------------------
>
> Key: KARAF-2919
> URL: https://issues.apache.org/jira/browse/KARAF-2919
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
> Affects Versions: 3.0.1
> Environment: Karaf 3.0.1 on Windows 7 Professional
> Reporter: Alexandre Gallice
> Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.3, 2.4.1, 2.3.9
>
>
> It seems that karaf jms:* commands are not locally transactional as suggested by the
following piece of code in org.apache.karaf.jms.internal.JmsConnector at line 97:
> return session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
> In my opinion, it could be interesting to create transacted session that the client explicitely
commit. For instance:
> return session = connection.createSession(true, Session.CLIENT_ACKNOWLEDGE);
> This would secure the move a lot.
> Moreover, we could explicitely commit messages one by one so that problematic messages
could be insulated in the DLQ.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|