Camel Producer uses a Spring-JMS JmsTemplate. The JmsTemplate doesn't keep a reference to JMS Connection or Session between calls to execute. It relies on the ConnectionFactory to manage that, hence the SingleConnectionFactory and CachingConnectionFactory.
-----Original Message----- From: RadoslavStoyanov [mailto:radoslav.stoya...@softwareag.com] Sent: Tuesday, December 06, 2011 5:54 AM To: users@camel.apache.org Subject: RE: Performance issue with Camel JMS publish/subscribe Hi Sven, This is code snippet of my publish functionality: Producer producer = producers.get(eventTypeID); if(producer == null) { String inChannel = resolveEventTypeToInChannel(eventTypeID); Endpoint send = context.getEndpoint(inChannel); producer = send.createProducer(); producers.put(eventTypeID, producer); } Exchange exchange = producer.createExchange(); exchange.getIn().setBody(content); producer.process(exchange); Doesn't that logic guarantee that I use the same connection every time, since I use the same publisher? -- View this message in context: http://camel.465427.n5.nabble.com/Performance-issue-with-Camel-JMS-publish-subscribe-tp5049909p5052131.html Sent from the Camel - Users mailing list archive at Nabble.com.
