[
https://issues.apache.org/activemq/browse/SM-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Gavlin updated SM-1760:
---------------------------
Description:
After the recent patch for SM-1681, the smx-jms provider now always attempts to
create a temporary replyTo destination if no replyTo destination is provided.
In the case of a "stateless" in-only ME for which no JBI DONE/ERROR reply is
expected, this does not seem correct.
So, should the former "stateless" boolean property which was recently removed
from the JmsProviderEndpoint be resurrected such that when stateless=false, the
endpoint knows: 1). to create a temporary replyTo queue if none has been
provided 2). to wait for a DONE/ERROR JBI reply on the replyTo queue for MEs
with an in-only MEP (see SM-1684)?
If this were the case, then if stateless=true, no replyTo destination is
specified, and a ME with a non-in-only MEP is received, would this trigger an
error condition? What would be the appropriate default for the stateless
property?
/Ron
> smx-jms provider should defer the creation of a temporary replyTo destination
> until it receives a ME w/a mep that requires one
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1760
> URL: https://issues.apache.org/activemq/browse/SM-1760
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jms
> Affects Versions: servicemix-jms-2008.01
> Reporter: Ron Gavlin
>
> After the recent patch for SM-1681, the smx-jms provider now always attempts
> to create a temporary replyTo destination if no replyTo destination is
> provided. In the case of a "stateless" in-only ME for which no JBI DONE/ERROR
> reply is expected, this does not seem correct.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
