You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Torsten Mielke (JIRA)" <ji...@apache.org> on 2009/04/06 14:46:35 UTC
[jira] Created: (SM-1841) New servicemix-jms endpoint out of the
box uses listenerType="default" without any caching which drastically
degrades performance.
New servicemix-jms endpoint out of the box uses listenerType="default" without any caching which drastically degrades performance.
----------------------------------------------------------------------------------------------------------------------------------
Key: SM-1841
URL: https://issues.apache.org/activemq/browse/SM-1841
Project: ServiceMix
Issue Type: Improvement
Components: servicemix-jms
Affects Versions: 3.3
Environment: new servicemix-jms endpoint
Reporter: Torsten Mielke
The [new servicemix-jms endpoint|http://servicemix.apache.org/servicemix-jms-new-endpoints.html] out of the box uses the default Spring JMS message listener and has no caching turned on. This really degrades out of the box performance. Compared to the [old servicemix-jms|http://servicemix.apache.org/servicemix-jms.html] endpoint the standard new endpoint is slower by a magnitude. Only with proper caching configured in the new JMS endpoint (cacheLevel="CACHE_CONSUMER") or by configuring for a different MessageListenerContainer (listenerType="server") will the performance be similar to the old JMS endpoint.
Perhaps we can improve the out of the box performance and configure some default caching? At least we should document the need for a proper configuration of the "default" listenerType better.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1841) New servicemix-jms endpoint out of the
box uses listenerType="default" without any caching which drastically
degrades performance.
Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Custine reassigned SM-1841:
---------------------------------
Assignee: Chris Custine
> New servicemix-jms endpoint out of the box uses listenerType="default" without any caching which drastically degrades performance.
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1841
> URL: https://issues.apache.org/activemq/browse/SM-1841
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-jms
> Affects Versions: 3.3
> Environment: new servicemix-jms endpoint
> Reporter: Torsten Mielke
> Assignee: Chris Custine
>
> The [new servicemix-jms endpoint|http://servicemix.apache.org/servicemix-jms-new-endpoints.html] out of the box uses the default Spring JMS message listener and has no caching turned on. This really degrades out of the box performance. Compared to the [old servicemix-jms|http://servicemix.apache.org/servicemix-jms.html] endpoint the standard new endpoint is slower by a magnitude. Only with proper caching configured in the new JMS endpoint (cacheLevel="CACHE_CONSUMER") or by configuring for a different MessageListenerContainer (listenerType="server") will the performance be similar to the old JMS endpoint.
> Perhaps we can improve the out of the box performance and configure some default caching? At least we should document the need for a proper configuration of the "default" listenerType better.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1841) New servicemix-jms endpoint out of the
box uses listenerType="default" without any caching which drastically
degrades performance.
Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51052#action_51052 ]
Chris Custine commented on SM-1841:
-----------------------------------
I also think we should default to cachelevel=3. I have has similar issues recently where users are using defaults and the performance was terrible and certain things like ActiveMQ failover urls don't work as expected. If anyone knows of a good reason not to change the default to cachelevel=3 let me know, otherwise I will change this soon.
> New servicemix-jms endpoint out of the box uses listenerType="default" without any caching which drastically degrades performance.
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1841
> URL: https://issues.apache.org/activemq/browse/SM-1841
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-jms
> Affects Versions: 3.3
> Environment: new servicemix-jms endpoint
> Reporter: Torsten Mielke
> Assignee: Chris Custine
>
> The [new servicemix-jms endpoint|http://servicemix.apache.org/servicemix-jms-new-endpoints.html] out of the box uses the default Spring JMS message listener and has no caching turned on. This really degrades out of the box performance. Compared to the [old servicemix-jms|http://servicemix.apache.org/servicemix-jms.html] endpoint the standard new endpoint is slower by a magnitude. Only with proper caching configured in the new JMS endpoint (cacheLevel="CACHE_CONSUMER") or by configuring for a different MessageListenerContainer (listenerType="server") will the performance be similar to the old JMS endpoint.
> Perhaps we can improve the out of the box performance and configure some default caching? At least we should document the need for a proper configuration of the "default" listenerType better.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1841) New servicemix-jms endpoint out of the
box uses listenerType="default" without any caching which drastically
degrades performance.
Posted by "Torsten Mielke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51048#action_51048 ]
Torsten Mielke commented on SM-1841:
------------------------------------
This has already caused [confusion|http://fusesource.com/forums/thread.jspa?threadID=760].
> New servicemix-jms endpoint out of the box uses listenerType="default" without any caching which drastically degrades performance.
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1841
> URL: https://issues.apache.org/activemq/browse/SM-1841
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-jms
> Affects Versions: 3.3
> Environment: new servicemix-jms endpoint
> Reporter: Torsten Mielke
>
> The [new servicemix-jms endpoint|http://servicemix.apache.org/servicemix-jms-new-endpoints.html] out of the box uses the default Spring JMS message listener and has no caching turned on. This really degrades out of the box performance. Compared to the [old servicemix-jms|http://servicemix.apache.org/servicemix-jms.html] endpoint the standard new endpoint is slower by a magnitude. Only with proper caching configured in the new JMS endpoint (cacheLevel="CACHE_CONSUMER") or by configuring for a different MessageListenerContainer (listenerType="server") will the performance be similar to the old JMS endpoint.
> Perhaps we can improve the out of the box performance and configure some default caching? At least we should document the need for a proper configuration of the "default" listenerType better.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.