New servicemix-jms endpoint out of the box uses listenerType="default" without any caching which drastically degrades performance.

The new servicemix-jms endpoint 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 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.