You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've had issues with connection leaks using the default routing-jms activemq connection management (not actually sure what the defaults are; whether connection pooling is used at all, or whether the pool size is just incredibly high: the defaults allow over 1000 connections to grow when using e.g. dynamic endpoints). The following is a translation of the documentation's example connection pooling spring configuration ((http://camel.apache.org/activemq.html) to the grails spring dsl, consider using this as the default spring configuration shipped with the routing-jms plugin:
We've had issues with connection leaks using the default routing-jms
activemq connection management (not actually sure what the defaults are;
whether connection pooling is used at all, or whether the pool size is just
incredibly high: the defaults allow over 1000 connections to grow when
using e.g. dynamic endpoints). The following is a translation of the
documentation's example connection pooling spring configuration ( http://camel.apache.org/activemq.html), consider using this as the
default spring configuration shipped with the routing-jms plugin:
We've had issues with connection leaks using the default routing-jms activemq connection management (not actually sure what the defaults are; whether connection pooling is used at all, or whether the pool size is just incredibly high: the defaults allow over 1000 connections to grow when using e.g. dynamic endpoints). The following is a translation of the documentation's example connection pooling spring configuration ((http://camel.apache.org/activemq.html) to the grails spring dsl, consider using this as the default spring configuration shipped with the routing-jms plugin:
The text was updated successfully, but these errors were encountered: