You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Chris Custine (JIRA)" <ji...@apache.org> on 2009/05/06 18:34:38 UTC
[jira] Assigned: (SMXCOMP-507) smx-jms in-out provider
w/unspecified replyTo queue and Pooled/SingleConnectionFactory leaks one
temp replyTo queue per message
[ https://issues.apache.org/activemq/browse/SMXCOMP-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Custine reassigned SMXCOMP-507:
-------------------------------------
Assignee: Chris Custine
> smx-jms in-out provider w/unspecified replyTo queue and Pooled/SingleConnectionFactory leaks one temp replyTo queue per message
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-507
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-507
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-jms
> Affects Versions: servicemix-jms-2009.01
> Reporter: Ron Gavlin
> Assignee: Chris Custine
> Priority: Critical
> Attachments: smxcomp-507-test.patch, tempDestination-3.2.patch
>
>
> When using either an AMQ PooledConnectionFactory or a Spring SingleConnectionFactory with another broker, each message sent to a smx-jmx in-out provider with an unspecified replyTo queue creates (and does not clean-up) a single temporary replyTo queue. When using a raw ConnectionFactory, a single temporary replyTo queue is shared for all messages. See attached unit test which exposes the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.