You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2017/03/22 18:08:42 UTC

[jira] [Resolved] (CXF-2550) transactions don't work in jaxws Endpoint with jms transport

     [ https://issues.apache.org/jira/browse/CXF-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-2550.
------------------------------
       Resolution: Cannot Reproduce
    Fix Version/s: Invalid

This is an ancient issue is an area of code that has been completely re-written.   If the new JMS transport still has an issue, please re-open with a new test case.

> transactions don't work in jaxws Endpoint  with jms transport
> -------------------------------------------------------------
>
>                 Key: CXF-2550
>                 URL: https://issues.apache.org/jira/browse/CXF-2550
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.2.4, 2.2.5
>            Reporter: javier
>             Fix For: Invalid
>
>         Attachments: jms_queue.zip
>
>
> i'm trying cxf with jms transport with transaction to process a message and it is dequeued  when the implementor object  throw an error .
> the message is inonly and the code is:
> 	EndpointImpl endpoint = new EndpointImpl(new ObjectImpl());
> 	endpoint.setAddress("jms://");
>         ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
>         JMSConfiguration jmsConfig = new JMSConfiguration();
>         jmsConfig.setConnectionFactory(connectionFactory);
>         jmsConfig.setTargetDestination("sso2");
> 	jmsConfig.setSessionTransacted(true);
> 	jmsConfig.setPubSubDomain(false);
> 	jmsConfig.setUseJms11(true);
> 	jmsConfig.setTransactionManager(new JmsTransactionManager(connectionFactory));
> 	JMSConfigFeature jmsConfigFeature = new JMSConfigFeature();
> 	jmsConfigFeature.setJmsConfig(jmsConfig);
> 	endpoint.getFeatures().add(jmsConfigFeature);
> 	endpoint.publish();
> seems that the exception never arrive to  AbstractMessageListenerContainer.doExecuteListener but it is catched inside



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)