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
In a simple route like the one below, I observe that the jms-amqp-10-sink is opening, using, and closing a new connection for each exchange that is generated.
public class Hello extends RouteBuilder
{
@Override
public void configure() throws Exception {
from("timer:java?period=1000")
.setBody()
.simple ("Hello, World")
.log ("${body}")
.to ("kamelet:jms-amqp-10-sink?remoteURI=amqp://localhost:61616&destinationName=foo");
}
}
It would be nice if connection could be pooled in some way. It would be even nicer if the pooling parameters could be made configurable.
Tested on version 4.4.0 of Camel-JBang.
The text was updated successfully, but these errors were encountered:
In a simple route like the one below, I observe that the
jms-amqp-10-sink
is opening, using, and closing a new connection for each exchange that is generated.It would be nice if connection could be pooled in some way. It would be even nicer if the pooling parameters could be made configurable.
Tested on version 4.4.0 of Camel-JBang.
The text was updated successfully, but these errors were encountered: