You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "javier (JIRA)" <ji...@apache.org> on 2010/02/25 20:38:28 UTC
[jira] Reopened: (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 ]
javier reopened CXF-2550:
-------------------------
hi Daniel,
now the exceptions are propagated and transactions works fine when we are using a transaction manager (JmsTransactionManager or JtaTransactionManager) for transactional wrapping of message but they aren't propagated if we use sessionTransacted = true and transactionManager = null (just local transactions of activemq)
> 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
> Assignee: Daniel Kulp
> Fix For: 2.1.9, 2.2.6
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.