cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "EasternWahoo (JIRA)" <>
Subject [jira] [Commented] (CXF-6199) Allow scalability for slow services on jms
Date Mon, 19 Jan 2015 17:56:35 GMT


EasternWahoo commented on CXF-6199:

The fix works, and supports multiple JMS consumers.  Does that mean the deprecated JmsConfiguration
style should be used, as documented here  Here's
my config:
	<bean id="jmsConfighello" class="org.apache.cxf.transport.jms.JMSConfiguration"
	<jaxws:endpoint xmlns:tns=""
		id="helloJms" address="jms:queue:test.cxf.jmstransport.queue"
		implementor="..." publish="true"
		wsdlLocation="wsdl/hello.wsdl"	>
			<bean class="org.apache.cxf.feature.LoggingFeature" />					 
			<bean class="org.apache.cxf.transport.jms.JMSConfigFeature"

> Allow scalability for slow services on jms
> ------------------------------------------
>                 Key: CXF-6199
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: 3.0.3
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 3.1.0
> Currently the CXF transport does not scale well if the service implementation is slow.
> We need a facility to work with several threads.
> There are two options for this:
> 1. Allow to use more than one consumer
> 2. Use an executor in JMSDestination.onMessage
> Option 1 works well with PollingMessageListener but not with the event driven MessageListener.
It is also depending on the JMS provider how it scales with number of consumers.
> Option 2 works in all cases but does not allow to profit from more than one consumer
if the provider is slow with a single consumer.
> So probably we will need both variants.

This message was sent by Atlassian JIRA

View raw message