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 2011/07/07 16:23:18 UTC
[jira] [Updated] (CXF-3618) Extremely bad performance in JMS
transport when the MessageListenerContainer is used
[ https://issues.apache.org/jira/browse/CXF-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-3618:
-----------------------------
Fix Version/s: 2.3.6
> Extremely bad performance in JMS transport when the MessageListenerContainer is used
> ------------------------------------------------------------------------------------
>
> Key: CXF-3618
> URL: https://issues.apache.org/jira/browse/CXF-3618
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.4.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.3.6, 2.4.2
>
>
> When configuring the JMS transport for a fixed queue and using the async api the MessageListenerContainer is used.
> Normally this should increase the performance compared to jmsTemplate. When doing performance tests I found that the performance is extremely bad though.
> (Few messages per second). When I profiled where time is spent I found that the ListenerContainer is shut down all the time and restarted on next call.
> I removed the shutdown calls when no async messages are outstanding as the listeners may be kept open without any problems. Now the performance is fine again ( about 1500 request/reply calls per second).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira