On 5 November 2015 at 11:45, Gordon Sim <g...@redhat.com> wrote: > On 11/05/2015 10:32 AM, Michael Ivanov wrote: >> >> And it's still the question why the policy is not set for the queue >> created with: >> >> responseQueue = session.createTemporaryQueue(); >> >> when using qpid-amqp-1-0-client-jms-0.30.jar package? > > > That will most likely involve a receiving link with a dynamic source, i.e. > with no actual source name supplied but the dynamic flag set to true. >
Essentially, though it actually uses a sending link at the client for the creator. > If there was a way to configure the dynamic-node-properties requested in > this case, then the desired lifetime-policy could be selected. (I had > incorrectly assumed that the 'S' process was also using messenger). Can > anyone familiar with the 'original' 1.0 JMS client comment on whether the > dynamic-node-properties are configurable in any way? Having a peek at the source, the dynamic node properties aren't configurable and are not being set when the 'original' 1.0 JMS client creates a temporary destination. The new JMS client sets them with delete-on-close for the lifetime policy when creating temporary destinations. > > Just to wrap up, from JMS to trigger a queue created by a matching queue > policy, you would simply create a message consumer, not a temporary queue. > These are two different ways of dynamically creating queues, the policy > based on being a broker specific option. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
